Pragmatic Developer Experience
banner
pragmaticdx.com
Pragmatic Developer Experience
@pragmaticdx.com
39 followers 270 following 570 posts
Writing about developer experience beyond the tooling debates—because your best engineers aren't leaving over build times, they're leaving over death by a thousand interruptions.
Posts Media Videos Starter Packs
Pinned
If you find the developer experience content helpful, supporting via Ko-Fi helps sustain the research, experimentation, and writing.

ko-fi.com/pragmaticdx

Thanks for being part of this. 🙏
Support Pragmatic Developer Experience
Support Pragmatic Developer Experience
ko-fi.com
What's the ratio of time you spend writing code vs waiting for builds, deploys, and CI pipelines? Are we developers or professional waiters?
When someone says 'this should be a quick fix' how much do you multiply that estimate by in your head? 3x? 5x? 10x?
When you see a job posting asking for 10 years of experience in a technology that's 5 years old, do you laugh or cry?
What's your honest take on microservices? Revolutionary architecture or distributed monolith with extra steps and network latency?
When you see 'temporarily hardcoded' in a comment from 3 years ago, do you fix it or accept that temporary is actually permanent?
How many times have you written 'TODO: optimize this later' knowing that later will never come?
What's the worst legacy code comment you've found? 'Do not touch' with no explanation? 'This works, don't ask why'?
What's your most embarrassing git mistake? Force push to main? Delete the wrong branch? Commit credentials?
How do you handle the pressure to be a 'full-stack developer' when you really just want to be great at one thing?
When AI suggests code that works but you don't fully understand, do you use it anyway or insist on comprehending every line?
What's your policy on commenting code? Document everything, only document the weird stuff, or assume future developers can figure it out?
What's the feature you built that you were super proud of that users completely ignored? How long did it take you to accept they just don't care?
What's the percentage of your 'engineering time' that's actually engineering vs attending meetings about engineering?
How many times can you run 'git pull' before you realize you forgot to commit your changes? Asking for a friend who definitely isn't me.
What's your threshold for 'good enough' vs 'perfect'? Does it change at 5 PM on Friday?
When your architecture diagram needs its own zoom levels to be readable, is that thorough documentation or a sign you've overengineered everything?
What's the programming concept you explained to someone that made you realize you didn't understand it as well as you thought?
How do you decide when to stop optimizing code? When it's fast enough, when you run out of time, or when you've exhausted Stack Overflow?
How do you stay motivated working on a legacy system where every change feels like defusing a bomb?
How many times have you written the same explanation in Slack before realizing it should probably be a doc? What's your threshold for 'this should be documented' vs 'I'll just answer it again next week'?
I agree, leveraging AI to enhance decision-making and efficiency can really transform cloud operations without replacing the valuable expertise engineers bring.
That's a good point—starting with the latest updates can minimize technical debt and ensure smoother, more secure operations. Regularly reviewing and updating can indeed prevent larger issues down the line.
Absolutely, clear API guides can make a big difference in how quickly developers feel comfortable working with a platform. They really are essential for fostering a vibrant ecosystem.