> Writing acceptance criteria is harder than writing a prompt, because it forces you to think through edge cases before you've seen them. Engineers resist it for the same reason they resisted TDD, because it feels slower at the start.
This resonates with my experience, and it is also a refreshing honest take: pushing back on heavy upfront process isn't laziness, it's just the natural engineers drive to build things and feel productive.
You are the project, and getting through your idea to something, is about building a better you. Which points back to the beginning:
--
Publish that novella, build an OS, converse in Mandarin, release an indie game, publish that other novella, dominate a continent --
--
Seem to be a lot of complaints about this post, I'm enjoying it. Interesting flow of thoughts and share similar frustration with all my ideas and trying to channel them, and get to something. If I get to something close to my thoughts that's a huge win for me.
This reminds me of what my PhD supervisor told me as he was trashing my first draft of my first paper: “up until this point in your life you’ve been trained to convince someone who knows more than you that you know something by writing impressive equations and complex concepts. Now you are the expert and if you do that nobody will read your papers. And if someone stops after a few sentences you’ll lose citations too.”
reply