Is it getting context from the code, reading through docs, writing tests, updating old tests, or even writing new docs?
A few things I’m curious about:
Where do you feel the most time gets wasted in your dev workflow?
What do you wish your IDE or tooling understood better?
What’s the silent productivity killer nobody talks about?
What have you tried to fix — and what’s actually worked?
Would love to hear from folks across roles and stacks. Honest, unfiltered answers are appreciated.
Thanks, Raoul
"Wasted", specifically? Probably libraries/frameworks changing APIs with zero regard for backwards compatibility instead of caring for their user's time.
> What do you wish your IDE or tooling understood better?
That I could edit any code like you edit Clojure/Lisp code, where you move/modify forms rather than text.
> What’s the silent productivity killer nobody talks about?
Not caring up the design/architecture up front, and how moving slower actually enables you to move faster.
> What have you tried to fix — and what’s actually worked?
Thinking more about design and data structures, setup automated tests for more things, being more intentional with everything, not rushing, spend time shortening the feedback cycle. All improved my overall productivity and made me move faster, not slower.
Long-running automation. Caching helps, but breaking up a monolith is long-term work.
Flaky tests. Hard to fix on memory-starved hardware. One alternative is to separate scraping from validation.
Upgrading minor versions of dependencies that are breaking changes. Just have to stay on the older one if a fix cannot be found within a timebox.