3 ms·
I've been there. I had a job where after 3 months... There was a crapton of technical debt, we had a new PM that was useless, no one seemed to know anything,
by PopeDotNinja 7y ago
I've been there. I had a job where after 3 months... There was a crapton of technical debt, we had a new PM that was useless, no one seemed to know anything, every user story was written for everyone except me, yada yada. I wanted to bash my head in daily. Then one day it got better. The hung on long enough to find a few people who had been around long enough to know a bit about what they were talking about, and then I started learning how they stay sane. A lot of it involved mastering how to tell people they needed to up their game in communication before I was gonna do work they asked me to do.
No magic answer, but in general I find I'd rather work on a fucked up environment where I can make incremental improvement than a good-enough-for-people-who-aren't me environment where everyone is to comfortable to tolerate any changes.
- darioush 7y ago> A lot of it involved mastering how to tell people they needed to up their game in communication before I was gonna do work they asked me to do. Any pointers?
- PopeDotNinja 7y agoIf you thinking stuff as input and output, think about what input to your work makes things so hard. For me, I hadn't worked with a PM that simply didn't get how to talk to an engineer. So I learned how to quantify what I needed before I could start working and then started saying "hey, I need A, B, and C, and they aren't in here."