Senior craftsperson A Fragment by Wilson Miner staff.design The thing that you’re talking about though, which I’ve never seen a mature company really have a sustainable space for, is the “senior craftsperson.” They’re not pivoting at some point in their career to saying “I’m going to take what I know and leverage it through other people.” They’re saying “I want to get better infinitely at the thing that I do.” I believe that that’s possible. You see it more in pure-art kind of careers. Like “I’m an illustrator” or “I’m a concept artist” or something, and there’s a need for that person being really fucking good at that one thing, and continuing to do that one thing. I think a lot of people can intuitively understand why that would be really satisfying for someone as a career path. The dual ladder craftwork
Agile as Trauma An Essay by Dorian Taylor doriantaylor.com The Agile Manifesto is an immune response on the part of programmers to bad management. Many a corner officeIntramural brownie pointsFeature factories agilemanagement
Many a corner office I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: people whose methods are inherited from military and civil engineering, and who, more than anything else, need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it. There exists many a corner office whose occupant, if forced to choose, will take an absence of surprises over a substantive outcome. surpriseplanning
Intramural brownie points Features don’t work, in the sense that they can be easily gamed. A brittle and perfunctory implementation, done quickly, is going to score more intramural brownie points over a robust and complete one. If the question is "does product A have feature X?" then the answer is yes either way. features
Feature factories We use the term feature factory as a pejorative to designate companies addicted to adding features, while accumulating incalculable so-called technical debt. This situation is driven by management for the convenience of marketing, and I am skeptical that a more faithful application of Agile principles will correct it. Indeed, I suspect Agile processes are constitutionally vulnerable to this kind of compromise. The presence of a feature can only indicate to a user if a goal is possible, behavior will determine how painful it will be to achieve it. ux