Ask HN: Tracking Coding Friction Points?
I work with a stack that’s pretty brittle, and in a constant state of flux. As such, I spend _most_ of my time fixing broken compiles, chasing down problems that are red herrings (e.g., my branch suddenly has a test failing, but it turns out that’s totally unrelated to my changes), etc. I spend only a small fraction of my time on the actual “business logic” (aka “useful work”).

I would love to be able to track this stuff, so at the end-of-the-week standup I have a better idea wh … ⌘ Read more