3 ms·
The better workflow, and I think the one adopted by people in the second group, is to take a step back from coding, do a bit of thinking about the domain, desig
by skydhash 5mo ago
The better workflow, and I think the one adopted by people in the second group, is to take a step back from coding, do a bit of thinking about the domain, design a better abstraction for the problem (architecture, data structure, algorithms), and then write the small amount of code you probably need.
Code should grow according to need, not for its own sake. Start small, use it in the real world, and then improve it.
- slopinthebag 5mo agoI agree with that, but there still is some code that eventually needs to be written and there is a subset of that code which can be generated. I think it depends on the domain as well - for example, UI code is trivially generatable by LLMs.
- skydhash 5mo agoRAD tools like Delphi, qt creator, glade, Android Studio, Xcode’s Interface builder,… have always make it trivial to generate UI code. And there’s libraries for other concerns. The majority of a project code are written at the beginning or when a major feature is introduced. The daily work is mostly tweaking. And you can’t tweak without a good understanding of the module.