3 ms·
Yup. I somehow became a graybeard. I really didn't fit in at my last three gigs doing "backend" work. I always play to win, so try to understand why & how I fa
by specialist 7y ago
Yup. I somehow became a graybeard. I really didn't fit in at my last three gigs doing "backend" work.
I always play to win, so try to understand why & how I failed.
My current theory:
I had good successes doing product development. Shipping software that had to be pretty close to correct.
Today's "product development" is really IT, data processing. Way more forgiving of stuff that's not quite right. Often not even close to right. (Guessing that about 1/3rd of the stuff I supported didn't actually do what the original author thought it did, and no one was the wiser, until something didn't seem quite right.)
One insightful coworker said it best: "I learned to do everything to 80% completion."
My observation is that most team mates created more bugs than they closed. Maybe incentivized by the "agile" methods notions of "velocity". And they were praised for their poor results.
Whereas my tortoise strategies nominally took longer. So I had fewer, larger commits. Way fewer "points" on the kanban board. Created much fewer lines of code.
(When fixing [rewriting] other people's code, mine was often 50% to 80% smaller. Mostly by removing dead code and deduplication.)
I was able to bang out new stuff and beat deadlines when I was working solo.
I think the difference between solo and team play is mostly due to style mismatches. It's very hard for me to collaborate with teammates who are committing smaller, more frequent, often broken, code changes.
Any way. That's my current best guess at what's happening to this graybeard.
More optimistically...
I'm very interested in the "Test Into Prod" strategies advocated by the CTO from Gilt (?). It's the first QA/Test strategy (for an "agile" world") that makes any kind of sense to me. So I think I could adapt to that work style.
(I served as SQA Manager for a while. It's hard to let go of those expectations. It's been maybe 20 years since I've seen anyone doing actual QA/Test. I feel bad for today's business analysts (BAs) who get stuck doing requirements and monkey style button pushing. Like how most orgs functioned in the 80s.)
- throwanem 7y agoI see more gray in my beard every morning. And the thing about "...to 80% completion" is that the first 80% of value is captured in the first 80% of effort, and the last 20% of value in the other 80% of effort. It's important to know when to follow that ROI graph past the knee, for sure. But it's just as important to know when not to. (I mind me of a time a few years back when I was surprised to learn that the right method of exception handling, for a specific case in some work I was doing on a distributed system, was none - just letting it crash and try again when the orchestrator stood up a fresh container. It felt wrong at first; ever before I'd have instead gone to a lot of painstaking effort to reset the relevant state by hand, and my first instinct was to do the same here. But crashing turned out to be the right thing to do, because it worked just as well and took no time at all to implement.)
- specialist 7y agoYa. Sorry, I'm still struggling on how to phrase this. I'm totally on board with 80% feature complete, MVP, biz case, etc. What I'm trying to articulate, here and elsewhere: implementations that apparently work, but not really coders who don't check their own work doing the bare minimum to get awarded the agile velocity victory points futility of arguing definitions of "done" lack of feedback loops that cliche about managing to metrics leads to undesired outcomes the personal cost, burden of craftsmanship in a "break things and move fast" world