It's not that all organizations don't have disfunction, but as a younger person I was very fixated on everything I saw that was wrong and ignored either the problems I myself was introducing which were (and probably still are) numerous or the systems and programs that made the organization successful. Now that I'm older and in a position with a different perspective, I'm far less likely to find systemic fault. Perhaps I'm just lucky in my career atc? I don't have a blog to go back to, but this author seems insightful and I'd like to see what they think in 5 or 10 years.
Organization probably doesn't want to improve things
41–50 of 482 posts
Re: Organization probably doesn't want to improve things
#42Unreadable. Organize your thoughts, write concisely. You believe you have something to say; we would love to hear it. But we aren’t willing to wade through a sewage of words.
Re: Organization probably doesn't want to improve things
#43That article was a very nice surprise and apart from how crushingly accurate it is (before somebody jumps in to defend all the corporate chaos, of course) it also had me giggling several times while reading it. The answer of course is financial incentives. It is the answer 99% of the time, I know quite a few high-profile managers at this point and they are all very smart and get stuff done people and yet they allow t…
Re: Organization probably doesn't want to improve things
#44Earlier quoted context omitted.
Truth be told, I liked your article a lot but that particular example definitely should have been replaced with something more concrete and a bit more convincing. Having several copies of a GIT repo for different branches is a viable strategy as long as one does not do force-pushes.
Yeah I do this on a daily basis. Sometimes I want to have two different branches open simultaneously. Maybe there’s some fancy git hackery to have two open workspaces from the same .git local repository. But you know what? My time to figure that out is worth more than the measly megabytes of saved disk space.
Re: Organization probably doesn't want to improve things
#45These orgs are not truly functioning per market principles, yet for various reasons are stuck in a captive energy state that no one dares to disturb.
It could be a niche product sold out to big orgs or other steady clients. It could be a subsidiary or some other steady org. Either way, there is no market pressure to really push such orgs to adapt.
Thus all this theater and moldy props. These orgs are not expected to improve, they will live, but required to demonstrate an effort.
This reminds me of some shitty restaurants or deserted "boutique" storefronts which stay in business for decades with no suply-demand explanation for such longevity. I guess, these may somehow have low operating costs and some strong funding source.
Re: Organization probably doesn't want to improve things
#46Re: Organization probably doesn't want to improve things
#47All the Dereks I’ve met over the years (I know terribly anecdotal) are aware of the position they’re in. They are desperately scared of those nosy engineers that can prove with data how bad they are and try hard to put them in positions where that is not possible.
The portrayal of Michael Scott in “The Office” was sometimes too painfully real.
But knowing that, I’ve found its actually possible to use it to your own if not advantage, then at least peace of mind.
The way one does it is to get to know your Derek as a person, become his confidant - a surprisingly large amount of the “stupid jira tickets” those people generate are usually because of of very stupid requirements and policies that they have to follow.
After one understands the deep reasons for the busy work and inefficiencies - be it other bosses and hire ups or inadequate policies, one can work with their Dereks to sideline / fix them. The former being way easier than the latter of course.
Then you can approach the hire ups and understand why they put those policies in the first place, slowly getting a deeper understanding of the bigger picture. Cause there usually are reasons for all the madness, it just takes civility, patience and empathy to get to it.
“Why bother” one would ask? Well in the end you get known by all those people as “the guy to go to, to get shit done” and start being pushed into very interesting and consequential projects. People trust you, at least on a personal level - and even if you don’t manage to solve the political issues that frustrate you, you still have the peace of mind of being productive and friendly with your environment.
Re: Organization probably doesn't want to improve things
#48That article was a very nice surprise and apart from how crushingly accurate it is (before somebody jumps in to defend all the corporate chaos, of course) it also had me giggling several times while reading it. The answer of course is financial incentives. It is the answer 99% of the time, I know quite a few high-profile managers at this point and they are all very smart and get stuff done people and yet they allow t…
Which one will kill you if you get it wrong?
Which one does the manufacturer think is important?
Why are those never the same?
Re: Organization probably doesn't want to improve things
#49This is a painfully cynical take and beyond that I’m not sure what he’s trying to say. If it’s all crap, make it better. Do something, don’t just complain!
A few months later he quit.
Re: Organization probably doesn't want to improve things
#50Earlier quoted context omitted.
How? Programmers don't have executive powers. You are very often told that this is not your job and you should be doing yours and leave the "experts" to theirs. Well, they are not experts. They are not even at the level of informed amateurs. But they have the power. What would you do? Sure, there are good companies and you can switch until you find one but let's recognize that statistically speaking this absolutely d…
Hello! I am the author, and you've saved me writing this out. The whole point is that you actually can't do something (and that's okay! I don't complain anymore either!). Burnout comes from believing what people are saying in corporate contexts without looking at what they're actually doing. I have come across so many government teams that say they want to start using version control... as if someone has been stoppin…