> Treat code design and architecture as the thing that lets your slop canons (90% of engineers even pre-ai) move fast without breaking things
replyI'm currently of the opinion that humans should be laser focused on the data model. If you've got the right data model, the code is simpler. If you've got the relevant logical objects and events in the database with the right expressivity, you have a lot of optionality for pivoting as the architecture evolves.
It's about that solid foundation - and of course lots of tests on the other side.
> I 'm currently of the opinion that humans should be laser focused on the data model
replyyes. good programmers talk about data structures, bad programmers talk about code
How do you even converge on the right data model without refining code? Elegant code and elegant data model are the exact same thing!
replyIt's called "systems analysis". Programmers are generally pretty terrible at it because it requires holistic, big-picture thinking. But it used to take up the bulk of the design activity for a new enterprise system.
replyI agree and I like how you describe it. The phrase from Django, "perfectionists with deadlines", also resonates with me.
reply> My output is org velocity.
replyAmen, slow and steady and the feature fly wheel just keeps getting faster.
>slop cannons
replyI am stealing that phrase haha