I Will Always Be Angry About Software Engineering
The author, frustrated with corporate software engineering, left a high-paying job to start a consultancy, advocating for purpose and improvement in the field while contrasting it with effective healthcare experiences.
Read original articleThe author expresses deep frustration with the state of software engineering, reflecting on their experiences in the corporate world where they felt their work lacked value. After leaving a high-paying job, they started a consultancy, questioning whether their efforts to improve the industry would ultimately matter. They grapple with the contrasting perspectives of older generations, who advise acceptance of the status quo, and younger generations, who adopt a cynical view of corporate culture. The author recounts a personal experience in a hospital that highlighted the effectiveness and professionalism of the healthcare system, contrasting it with the inefficiencies often found in software development. This experience instilled a sense of optimism, as they recognized the potential for meaningful work and the importance of striving for improvement in their field. The narrative emphasizes the need for individuals in software engineering to seek purpose and challenge the prevailing cynicism, advocating for a more engaged and responsible approach to their work.
- The author left a high-paying corporate job due to dissatisfaction with the lack of value in their work.
- They reflect on the contrasting views of older and younger generations regarding work and societal change.
- A personal hospital experience highlighted the effectiveness of the healthcare system, contrasting it with software engineering inefficiencies.
- The narrative encourages software engineers to seek purpose and challenge cynicism in their work.
Related
The web I want vs. the one we have
The author reflects on a disconnect in Silicon Valley between industry leaders' understanding and software capabilities, expressing disillusionment while cherishing global connections and pursuing blogging and business ideas.
Get me out of data hell
A senior engineer reflects on the chaotic experience of working with a complex data warehouse, criticizing the toxic culture and inefficiencies, while valuing the lessons learned and camaraderie among teammates.
I've been writing software for nearly 30 years and he's preaching the gospel. It's clownfuckery all the way up. I will only add that running your own consultancy can be fun, but it's not going to dissolve his ennui.
I've been down this road. Sure being a consultant, gets you out of the day to day political shitstorm at any given company, but the clients still want software churned out at rate that is incompatible with quality. Plus you have the added bonus of not knowing if you'll have a job in 3 weeks.
Is it worth it? Yes. Do you make more money? Sometimes. Is it easier or less stressful? Not by a long shot.
I wish them the best of luck.
This sums up the post best for me.
It's really about the human condition. It leans autobiographical (as is tradition) but is quite well written, and feels widely relevant. Set it aside for later if you don't have time now-- maybe a bit on the long side, but not that long. Well worth it for me, and saved.
To begin, it motivates - "show 'em!" way. You gain the energy to prove yourself, to excel-over-others, you may feel the thrill of winning while seeing someone else loose. To aim for this gives you drive and makes you "work harder" - after all, you have some sort of goal.
Long-term though, you only discover that such "wins" (from spite) are rather hollow; the dopamine rush diminishes every time and you either need to "win bigger" or grind down others even harder in order to feel anything about it. Pursue this and eventually you'll just get angry with yourself and your powerlessness to retain this anger-fueled energy that once felt so energising. This is where it becomes self-destructive; you'll wail at the world how unfair it is to you because it's responsible for all this inadequacy, rage, powerlessness that you feel unable to retaliate for. Basically, no "win" of yours could be big enough, no loss of others great enough, for you to feel content again.
It's a lot better for the mind to work towards a goal - feel better - than be angry against something/-one. Keep anger focused. Don't burn out.
I liked very much the observations in the first half of the post, however I don't agree with the conclusions. For me the reason for the state of software engineering (and well, many other industries really) is the problem with leadership. We as society often choose wrong leaders[1] and these leaders have very detrimental effects on processes and quality. However, it doesn't mean that what we do in software engineering is intrinsically meaningless, it's just very inefficient. The majority of web and mobile applications do solve a problem people have, because people do need to eat, shop, dress, play, organise their documentation, learn, do sports, connect to other people, share things with each other, etc. More often than not these applications are developed not because of great leadership but despite of terrible one, because the people who write code still manage to do their job despite of it. And the same thing happens in hospitals, you don't think that hospitals' management is much better, do you?
So, basically, the problem with the first approach (Gratitude) is that it ignores the problem. Often ignoring the problem is contributing to it. And the problem with the second approach (Cynicism) is that it exacerbates it, because it essentially promotes the lack of integrity and the same problematic egocentric attitude that's responsible for this problem in the first place.
Being angry is a very natural reaction to this problem, and I do agree it's necessary to a degree. However I don't think it's the solution. I guess the solution is to accept the current situation for what it is, and do your part to change it. You don't need to be angry to do that, but you do need to ditch the wrong expectations about our society and how it works.
step one is acknowledging that a problem exists. this can be hard, especially when one is part of the problem.
step two is overcoming learned apathy. this is often harder.
step three is making things less shit, one day at a time, in any capacity that you can. this is awesome. everyday can be the best day of your life.
good for you. can’t wait to visit melbourne and interact with even a single, slightly less shit, piece of engineering.
viva le renaissance.
That said, so many consultancies start off with his same goal in mind (to do "real" engineering without the political bullshit) and become bankrupt or bought out. I hope they don't meet the same fate.
If your main point is that we ought to act ourselves to create a world we like, I wholeheartedly agree with you. But maybe I misunderstood.
Anyway strawmaning is bad, especially that your arguments stand buy themselves, and to me cut into the overall credibility.
Now I just fast read to try to find the point being made and I’m grateful to the author if they can say it in under four paragraphs. In this case I couldn’t find the point but it seemed like an interesting tale.
I think I preferred the 1990s.
Related
The web I want vs. the one we have
The author reflects on a disconnect in Silicon Valley between industry leaders' understanding and software capabilities, expressing disillusionment while cherishing global connections and pursuing blogging and business ideas.
Get me out of data hell
A senior engineer reflects on the chaotic experience of working with a complex data warehouse, criticizing the toxic culture and inefficiencies, while valuing the lessons learned and camaraderie among teammates.