logoalt Hacker News

tikotus • today at 2:44 PM • 2 replies • view on HN

This takes me back to the era of object oriented programming and UML diagrams. More time was spent framing the solution than implementing it. Is there maybe one more design pattern that could be applied? And when the time to implement came, all those diagrams were mostly in the way. But doing it was fun, since it allowed you to focus on the fun, big picture and skip the nitty gritty details that were actually hard to solve.

I feel like people are going down that slippery slope with harnesses and skills and what not. With the right prompt, and with the right model, and with a sprinkle of magic, the solution will emerge. Oh, it didn't? Let's see if there's a new model available, or if someone has come up with a new clever skill or something. Maybe then... Because actually solving annoying problems is not fun, even less so now that the code is a black box only the LLM can understand.


Replies

dutchbart • today at 5:43 PM

Diagrams and really, just designing the software you are trying to build is mostly about finding out painpoints before you start the programming (at least at point the time-consuming part). The diagramming allowed you to, without programming, show interactions between modules and check on a high level if you are missing edgecases that can’t be solved because of the design. If you were just using it just to apply design patterns then you were doing it for the wrong purposes.

➕ show 1 reply
rafaelRiv • today at 6:30 PM

I still do diagrams. Not UML specifically, but using mermaid.js. It is a great way to think about the requirements before coding