3 ms·
Agreed, but it's also quite unfortunately few companies are willing to try anyways. > Like, lemme get this straight: you expect a six figure salary, full auton
by rektide 6y ago
Agreed, but it's also quite unfortunately few companies are willing to try anyways.
> Like, lemme get this straight: you expect a six figure salary, full autonomy to solve problems as you see fit, and _also_ bite-sized, well-scoped bug reports/features.
If someone else is setting up all the problems, it's not really autonomy at all. I can pick some other quibbles with this tweet, & the tweetstorm, but this illusion being presented that there is autonomy is just not true.
Almost all organizations will tell you they are product driven. That means that, you, the engineer, are a resource, for someone else's goals.
I fully think most engineers are bad with autonomy. But also the whole system has been set up to be combatative against engineers. To assume we are bad. To assume we don't have design mentalities. To assume our priorities are not aligned with the business.
I started my career doing development with small web shacks, doing early web application development for small & medium businesses. We've had designers on staff or that we've contracted with every place I've worked, but really the functional design was extremely liberally done, very ad-hoc, and it was wonderful. So creative, so exploratory, so collaborative. Mostly just developers running the show, a pleasant but somewhat out of site boss nominally running the things. Low ego, low titles, high collaboration, highly exploratory, highly creative. The maturation of industrial computing, has, in my view, separated out the responsibilities in a harmful way. Articles like this, to me, embody the prevailing attitude of the world towards techies: not to be trusted, incapable of aligning to & finding value, needy.
What I have yet to see is companies that actively grow & support the amazing creative anarchy of their radically technically empowered work-force. Sure, absolutely: bad match for some. There's good lessons about inflexibility, wanting too much structure provided to you, while asking for autonomy. But real autonomy is not just freedom to do a good technical job. Real autonomy encompasses a lot more, way more. And I just keep thinking- somehow, some day, someone is going to start trying to tap the endless reserves of techie ass kicking, start trying to systemitize ways to let us be the radical, out there, wildly creative, imaginative, explorative systems thinkers that we are, to bring that 101% out, into the world. Today though, there's endless euphemisms put forth for how impractical everyone thinks techies would be, how important it is that non- & semi- technicals hold the reigns. Most organizations are unprepared (& do not want) to generate real autonomy or freedom.