Product Engineer/Architect navigating the AI revolution
I'm a working software engineer. Most of what I write comes from the same place: code is easy to generate now and just as easy to make unmaintainable, and the old engineering habits matter more for it, not less. prickles.org is where I collect those habits as short, specific tenets — guard clauses, screaming architecture, verifiable specs, and the rest. If something here is useful, that's where the full set lives.
Markdown supported · ⌘↵ to post
Rodrigo Juarez
I will tirelessly rename anything that becomes outdated as my understanding of the domain evolves. I mean, the agent will do it. That's why I have hundreds of tests.
I also find that renaming is a great way to expose places where the model is wrong. If something is difficult to name properly, it often points to a bad abstraction, misplaced responsibilities, poor functionality grouping, or something else that needs rethinking.