I have watched teams solve the same problem thirty times in a chat box and call it a workflow. Session one opens with a paragraph: Tailwind, no inline styles, single quotes, named exports, no comments
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
No responses yet.