Baldur Bjarnason's Notes on the Web
Everything from www.baldurbjarnason.com
-
Autumn fields and horses
Here are a few late autumn photos that I took about a month ago.
-
‘AI’ might be the end of our careers
I never planned on becoming a software developer, and these days it feels like my exit from the industry might be similarly unplanned.
The video version is on YouTube.
‘AI’ might be the end of our careers Shifts in power #
My education and training is entirely in art, literature, and media. Like many of my generation I got into web development because it was, quite simply, one of the more interesting things happening in the late nineties that a young person could get into without a big investment.
Web and software development turned out to be a decent job with decent pay. Even with my tendency to work for charities, publishers, and cash-strapped media outfits, dev work has always been a steady gig that paid okay.
But I’m increasingly concerned that the future might be quite dire for software development as a profession in the long term, even beyond the current era of bubble mania. The prospects of software development as a field and as a career are inversely proportional to the success of Large Language Models in coding.
A new kind of unskilled labour #
Here’s a hypothetical example – loosely based on several real-world examples I’ve witnessed.
You have a software company, or organisation doing the kind of work that requires a small software team of mixed specialities. There are server-side developers who write in Ruby, or something similar, and front-end developers who understand the
noderuntime well enough fit under the otherwise vague and meaningless label of “full stack”.After a recent wave of layoffs, the front-end team is short-staffed, so the Ruby team steps in to work on some of the front-end tasks as needed.
Sometimes it’s the other way around, but in this example it’s Ruby devs doing JavaScript.
They don’t know the first thing about web development, DOM APIs, the CSS cascade, or any of the fundamentals that make web development unique. But they aren’t worried. They’re using “agentic development” and the agent generates code in whatever language you want. As far as the business is concerned, these developers don’t need to understand any of the fundamentals, they just need to work from the requirements and understand the general structure.
The output of the agents is neither great nor catastrophic, at least to begin with. It has issues, mostly down to performance and reliability but neither of those concerns have been dealbreakers in software for over a decade. The industry is perfectly fine with products that are constantly partially broken.
The company talks up the productivity gains of generating code, without actually checking to see if those gains are realised in concrete ways, and hype up the flexibility of being able to shift developer staff as needed.
Nobody seems to have actually noticed what happened, which is that skilled specialised labour has been replaced by less skilled, less specialised labour.
This isn’t a value judgement. I love Ruby. It’s a lot of fun. But server-side Ruby and client-side JavaScript are already very different specialities even without taking accessibility, HTML, CSS, and other client-side concerns into account.
What happened is that “AI” let the company replace a specialist with a non-specialist.
Or, phrased a bit differently: automation let unskilled labour take the job of skilled labour.
We’re seeing this happen in other ways as well. Managers, support staff, and designers are all “prompting” code and committing changes to projects and products.
These are literal examples of people who are unskilled in a specific specialised job but are doing the work of a specialist with the help of automation.
We’ve seen this happen before in history – it has been happening since the dawn of industrialisation – but I don’t think we’ve seen many examples as extreme as what’s happening in software. What’s especially unusual is how eager software developers have been to promote the tools that are effectively ending our own careers.
That might be because it’s not always obvious why it’s bad or how specifically it’s going to end our careers. The reasons why this is very bad for software developers and our field can be a bit counter-intuitive.
Most people’s expectation of the technology is that as long as “AI” falls short of the full automation that requires general purpose reasoning, it won’t be able to fully replace developers, and as long as it doesn’t replace us directly, it won’t harm our job prospects.
That the code genuinely – at least from the perspective of third party observers – seems to be of a lower average quality than code written by hand, and gets less and less accessible as the layers of generated code pile on, further supports the idea that even though this might be a change in our practices, companies are still going to need us.
This might be true, but what it misses is that, in the long term, they won’t have to pay us as much as they used to.
The biggest threat “AI” poses to software developers isn’t that it might replace us, it’s that it will let our employers redefine our job as more generic, lower paid, and unskilled.
Or, less skilled at least.
Supply and demand #
If, like me, you spent your teens and college years working to pay for your education, you’re going to be familiar with how limited your job options are when you’re young, unskilled, and inexperienced.
Most of the jobs you have a shot at – unless you’re some sort of nepo-baby – are unskilled labour. That means the employer believes the job doesn’t require any expertise, experience, or skill to perform.
What that really means it that the employer thinks you’re perfectly replaceable. They believe there is, in economic terms, an infinite supply of potential replacements to take your place each as good as the other.
It doesn’t matter if the job actually is unskilled or not. I very occasionally stepped in as a substitute bartender at a hotel during college[1] and there is obviously a huge difference between a skilled bartender and an unskilled one, but both of us got paid the same.
Because the job is classed as “unskilled” and the supply of possible replacement is near infinite, you don’t have any leverage or bargaining power. That means the employer gets away with paying you whatever the legal minimum is for that job in your country.
The formula is simple: the less skill the job requires or is seen to require, and the greater the supply there is of replacement workers, the less the job will pay in the long run.
“Unskilled” office work, such as that done by agency temps, gets paid much less than PR, sales, or marketing.
Skill levels and supply of labour are two of the main reasons why I’m worried about the prospects of software development as a career.
Deskilling began a long time ago #
The drive to turn software development into less skilled labour isn’t new. Not to be confused with attempts to make the craft more accessible and approachable, deskilling generally focuses on making the developer conform and aims to limit what they need to know to do their jobs.
Before “AI” the biggest push in this direction was the adoption of web development frameworks such as React – a framework for building web and native apps, if you aren’t familiar. React wasn’t popular because it made for better software but because it simplified recruitment by deskilling the job. You need fewer skills for framework-oriented web development than for a job that requires understanding the front-end stack in its entirety.
- You didn’t have to understand the platforms you were building on.
- You didn’t have to understand the languages except how they operated in the limited context of the framework.
- You didn’t have to understand the context of the work you did. Components were designed for the purpose of making labour interchangeable between teams and departments, not to separate concerns or optimally structure the software.
Companies loved React not because it cut costs or increased productivity. They loved it because it promised to simplify recruitment and let them hire developers with less training. It promised them a world where bootcamp trainees would, after only a few weeks, be able to perform as well as a computer science graduate or somebody who had worked with the web since before frameworks existed.
The bootcamp graduates would be paid less, obviously, but at the time the concern of most employers was primarily to offset the massive imbalance that existed in the software developer job market at the time: the demand for developers far outstripped the supply.
The bootcamp promise never really panned out, which is why many of those outfits devolved into fraud and scams, but it shows us that employers have been interested in the idea of deskilling the job since well before coding agents became a thing.
Two things have changed:
- Demand for software developers turned out to have been artificially inflated by tax loopholes, low interest rates, and a very irrational belief in the long term sustainability of the software industry’s massive growth rate.
- The supply of software development labour has now increased dramatically. LLM tools have placed an ever-increasing number of people who are unskilled in software development in direct competition with us, the skilled developers. The layoffs have also increased the supply of unemployed developers with experience who are competing for every available job.
Demand deflation #
Whatever the reason, employers today almost universally believe they need fewer developers.
Pretty much every company, small and large, that employs software developers has been scaling back on the number of coders they employ. They all believe they’ve massively over-hired.
That means there is less demand.
There’s also the increasingly common sentiment that regular software is basically done. That operating systems and productivity software are basically already as good as they get, already at market saturation, and the only true growth opportunity is pushing “AI” onto as many people as possible.
This further depresses demand for software developers, especially those who are specialised in user-facing software.
Regulatory efforts to tackle oligopolies, monopolies, and abusive business models have also stalled. Oligopolies and monopolies generally don’t need to do anything to make money, so they don’t really need to be hiring as many people as a company in a more competitive market would.
That’s even less demand.
All of this is happening regardless of “AI” and it’s likely that when the financial bubble surrounding “AI” pops, demand for developers will be pushed down even further.
Junior hiring is over #
That lack of demand has hit new Computer Science graduates hard. The current software developer job market is bad for everybody, but for new graduates it means they won’t have the opportunity to start a career in their chosen profession.
Most of them will end up pursuing other careers. Some of them will discover, through happy accidents, that they have a different calling in life. Many won’t care that much because what matters is putting food on the table.
But those who are enthusiastic for the field will feel betrayed – lied to – and are unlikely to forgive the industry if the situation changes in the future.
This too has happened before, and normally it results in a long term cycle of dysfunction.
It usually begins as the job market for a speciality deteriorates, graduates in that field go unemployed, course attendance declines, the number of graduates collapse, and that industry is saddled with an ageing workforce. Managers think this is fine as they just see the cost savings of not having to train new employees that they won’t need.
Several years later, the industry experiences a growth spurt again, but that growth is stalled from the outset because there is no supply of labour to fuel it. There is no one to hire to fill the increased demand. Short-sightedness killed off economic growth.
The problem we’re facing as a profession is that “AI” breaks this cycle for software developers, to the company’s benefit and our detriment.
When the time comes for the software industry to experience its first post-bubble growth, companies won’t be limited to hiring what ever new graduates are available at the time.
Employers will be able to hire as many unskilled, untrained, low-wage office workers they want, saddle them with whatever shoddy agentic coding tools are available at the time, and set them to work.
We’ve created our own competition and destroyed our bargaining power in the job market.
Unskilled software development #
People with no skill or expertise in programming have entered into direct competition with those of us with expertise.
We’re all seeing unskilled software development eat into our business, one way or another. Managers and designers are vibe-coding software. Clients send us half-baked vibed up code they want us to finish. Developers are vibe-coding in languages and on platforms they’re completely unfamiliar with. A bigoted ruby programmer who is vibe-coding in rust is effectively an unskilled worker replacing a skilled one through the use of automation.
Some of this is also happening in the software marketplace itself. One example I’ve been keeping track of is a writing app, because it’s quite illustrative is Neo.
Hugh Howey, who is an author and not a programmer, has been vibe-coding his own writing app. It’s basically a remix of preexisting open source writing tools with no attribution, because that’s how LLMs work, all wrapped up in Howey’s preferred user interface themes and style.
The number of apps and games released onto the various online marketplaces has exploded. Sales have not followed suit. Very few of these kludges are bought by anybody and quite a few, like Neo, are offered for free.
The last time something like this happened was during the mobile app store bubble.
A glut inevitably changes consumer value perception, the price you can demand for software craters, and the clutter makes it harder for well-made apps to succeed.
Together, increased supply and less demand has a very simple and straightforward consequence: lower prices everywhere.
This is going to be the case no matter how the “AI” bubble pans out. A collapse might make it financially infeasible to train new models from scratch, but the financial rewards for companies if they manage to depress software developer wages are substantial enough to offset higher running costs.
And if we aren’t creating any new handwritten code to speak of anyway, because the industry has switched entirely to vibe-coding, the rewards for training new models from scratch would be minimal at best. There isn’t really any new code.
Software developers are generally paid much more than illustrators or photographers. Modern companies employ more of them, even after several years of regular layoffs. Even if “AI” code turns out to be mostly garbage, the software industry has a long history of being genuinely tolerant of garbage code and garbage designs.
There is no path forward for “AI”-generated code that’s a net benefit to us, software developers, as a profession.
- If these tools increase productivity, that just adds to the problem because that will just depress demand for developers even further.
- If it decreases productivity – once you account for how works flows through the entire system – then existing software developer pay is high enough to still make that productivity sacrifice extremely lucrative.
- If it generates code that’s as good as that of a mid-career developer, then that just makes it easier to quickly “gear up” relatively unskilled people to step into specialised software development jobs for less pay.
- If it constantly generates unsafe code, then it’s still worthwhile because the financial cost of even major software defects are relatively minor in the markets while the benefit of paying developers less is substantial.
No matter how this plays out, as long as “AI”-generated code continues to be accepted, we as software developers lose.
The more supply of labour and less demand there is, the lower the pay, and less employment there is.
The supply-demand equation #
If there’s less demand for software developers, our pay is likely to decline over time.
If there’s more supply of people able to do software development work, then that pushes pay down even further.
If software development, or specific subtypes such as web dev, gets redefined in the marketplace as “unskilled”[2], then we lose our bargaining power in the job market and pay gets pushed down even more.
Jobs where labour has less bargaining power get a smaller cut of overall revenue, which means that if things turn around after the bubble pops, the jobs that have been deskilled and redefined as “unskilled” won’t benefit from that turnaround.
The best we can hope for, as software developers, is that agentic coding turns out to be completely unviable after the financial bubble pops and that most of these tools just outright disappear.
Because if it remains even partially viable in the long term, the push to redefine larger sectors of software development as unskilled or semiskilled will continue. This will cause our ability to demand fair payment for our work to crater.
Some parts of software development will probably be sheltered from this, but it’s hard to tell in advance which will and which won’t.
What can we do? #
Software developers as an expertise or field of practice does not stand to gain from “AI” in any meaningful way. The success of “AI” would mean that most of our careers have reached an end station and the field will enter a steady decline.
This is fine if you’ve already got yours, if you’ve already cashed in on stock options, or have already saved enough for an early retirement.
This sucks if you actually like the job.
More than any other profession, due to widespread adoption, pervasive belief in its effectiveness, and broad support from employers, software developers are the ones who stand to lose the most from the success of “AI”. But we can pick up some of the tactics used by some of the other fields affected by “AI”-driven job losses.
It’s common now among illustrators and writers, for example, to basically make the use of “AI” socially unacceptable. Individuals with bargaining power, such as John Scalzi require that the work done on their books by their publishers be done by humans without the use of generative models. Antipathy towards “AI” is increasingly popular among both those who work in the creative industries and those who are fans of that work.
The more “AI”-free corners of the field software development we can protect, the stronger our bargaining position becomes as software development workers. Pushing “AI” out of our field where we can is one of the strongest, most effective tools we have for protecting our field from being devalued.
People who use their public profile, influence, and platform to promote the use of “AI” for coding should feel defensive. They are actively undermining our careers. We have a right to be concerned about their actions.
That isn’t to say that people should be aggressive, abusive, or violent. Quite a few people are just doing what they can under difficult circumstances to put food on their table or keep themselves employed. We don’t know what’s going on in people’s lives, and we don’t know what might motivate people to use these tools.
But criticism, even harsh criticism, is legitimate when somebody with a large public platform, or strong influence within the industry, has picked a side against our profession’s best interests.
A solo developer working in relative obscurity on their open source project is not in the same position as Linus Torvalds and should not be made to be a target. But Linus has picked a side, and it’s not our side.
The more “AI” becomes a sales and marketing liability across multiple industries, the stronger our position will be.
The more of a political liability “AI” support becomes, the more likely we are to get regulation and enforcement that limits the harm done by the tech.
The broad basket of technologies that the industry has marketed as “AI” is shaping up to be the least popular in the history of computing.
It still has fans, but nothing in computing comes close to being as disliked by as many as generative models are today.
If we build on that, there’s a chance that software development will continue to be a viable career into the future.
-
Looking back at snow
A few black and white photos from a snowy 2024. Thankfully it’s not this snowy these days.
-
Automation, algorithms, and self-censorship
I’m probably not going to turn this essay into a video and maybe not even a podcast. Not because of the theme or any of the concerns raised, but simply because I don’t know if I’ll have the time to do so this week.
A couple of my videos on YouTube got picked up by their recommendation algorithm.
Even by the most conservative “percentage of the audience who watched to the end” estimate, those videos had an audience that was at least one hundred times larger than my channel’s baseline. They’re still racking up views.
This raised a question I’ve been wrestling with since.
Not “how do I replicate this and make it happen again?”
Though that’d be an understandable thought.
Instead, I’ve been tackling the question of choice and self-censorship.
“Should I be trying to replicate this?”
Should I let the temptation of an algorithmically-driven mass audience on YouTube define and constrain what I do as a writer?
That’s obviously a loaded question with an equally obvious and loaded answer, but the journey between the two is what matters.
The creative process is made of the choices you make #
Self-censorship is a vital part of the creative process.
The emphasis on “process” is intentional. In spite of what the name implies, acts of self-expression don’t occur in singular bursts. People keep using unfortunate terms like “seminal” to describe creative acts for a reason. They imagine that art comes in singular voluminous emissions followed by calm and well-being.
In conservative and religious cultures, that is then normally followed by shame and guilt, so perhaps it’s fitting that the rather obscene metaphor has become the standard, unthinking description everybody reaches for when they’re trying to describe a genuinely original creative or intellectual act.
To me that word has a smell. Whenever I see it in a text, that smell sits on the writing like a lukewarm blob. It’s a word that carries with it the act that precedes: there’s an implied dick pic in every paragraph that contains it.
As unfortunate as this popular metaphor is – and I can see why it’s popular – it’s also inaccurate.
I’m fine with obscenities in art and writing. It’s the fact that it’s so wrong that annoys me, and the coyness, obviously. There’s plenty of opportunity to write about genitalia when it comes to art and creativity. Resorting to a “teeheehee, oh my god, how rude!” Benny Hill metaphor is nothing short of cowardice.
It stands both as a shorthand dismissal of the weeding and winnowing, expression and self-censorship, that is the creative process and as an example of cowardly self-censorship that has stagnated into a petrified metaphor: the idae that creativity is the work of a singular moment.
This may well be an accepted truth, but it is not a fact. Creative works are the results of ongoing processes, not singular moments, and the processes are life-long – they are your life, interwoven with your life and reflecting it to the outside world. The singular inspiration coming out of the blue is a lie. A “eureka!” moment is usually the resolution or climax of an ongoing process that has stalled or reached an impasse, not the process in its entirety. It’s a climax preceded by lengthy work and succeeded by a no small amount of cleaning up.
Hang on. Sorry.
Maybe the metaphor isn’t that inaccurate after all.
It’s still an act of cowardice, though, an unthinking shortcut that lets you avoid thinking about what you say or what you intend to describe. Using the word is a choice, and choosing clichés like it without thinking means you’re letting an indistinct crowd of ghosts – the accumulated whispers of faded memories of texts read and forgotten – make your choices for you.
Tech is keen to automate those choices for you.
Navigating the automation and algorithms that have been pushed into every corner of our culture has become a core part of every modern creative process.
Even opting out of it – writing your thoughts out by hand is a choice made in the context of the laptop, keyboard, and software filled with various automations.
The choice to walk means something different in a world where the car is universal and ever-present.
Making poor choices is how you grow as a writer or artist #
I’ve been struggling a bit with the choices I have to make in my writing.
Nothing too serious. My lack of familiarity with the algorithmically-compiled audiences of YouTube and TikTok mean I don’t really know how to address them. They feel like a mirage – a vision that’s ephemeral and changing.
From the perspective of a writer the algorithms abstract away the audience behind a veil of automation. The audience of a regular, non-algorithmic medium has a much more stable body that can be investigated with – essentially – a form of call and response.
For example, I do have a sense of my regular audience. Not in the analytical sense – I don’t actually know who you are – but I do have a sense of how my existing audience is likely to respond to my writing. I can’t predict what will play outside that immediate bubble or what will inspire a new reader to immediately subscribe or even email me, but I do have a vague sense for how the small community I’m in will respond when I try something in my newsletter.
I can speak to you, because you’re here.
My sense isn’t completely accurate, but I usually get the overall direction right.
I just quite often ignore that sense because I’m also writing this for myself – to help my put order to own thoughts. I know I can mostly get away with this because I’ve done it before. I know that the community I’m a part of has some tolerance for self-expression even when it doesn’t speak to them personally.
What I say to you is shaped by omissions. It’s not just a matter of choosing what to say, but since every decision involves picking one of alternatives, the omissions are always going to outnumber the choices. They are the outside that defines the frame of a painting.
Self-censorship is in this way a constant shadow of the entire creative process. Technology that affects or even governs that shadow changes the body casting the shadow – the work itself. It always has, because technology and culture are interwoven and integrated. A medium is always a technology of one kind or another.
But that technology used to be consistent, for the most part. It expanded opportunities, but it bounded that more open space with new sets of constraints. The printing press transformed text, but it also defined it through its limitations. This created a stable environment you, as an artist, could navigate and learn.
Algorithms have changed that.
Every call a writer makes to an algorithmic medium can have a different audience. Exploring the interests of your audience by changing your tone, style, or topic to see how they respond no longer works because the change algorithmically assembles a new crowd, some of which may be carried over from prior audiences, some of which may be new and strange and only interested in this hyper-specific new topic. Further exploration will lose them.
A particular kind of video will get you its corresponding algorithmically assembled audience. Make a different kind of video, and you risk getting thrown into a completely different kind of audience.
The self-censorship you do as a writer stops being about exploration and becomes a source of stagnation.
These algorithms favour repetition and routine. This is my fixed self, let the robots find it a place and auditorium. Nobody has chosen to be here.
The “algorithms” become audience automations. They transform art into a body severed in half.
Adding media is one thing, adding algorithms is another #
I worried quite a bit about what to write for YouTube and TikTok. Much of this comes from my inexperience. What should I write about next? Do I dare try out different formats and structures? What approaches and angles can I take that might trigger a similar audience automation as before and let me preserve the creative body undivided?
All that worry did was leave me with a greater appreciation for newsletters, feed-driven websites, and podcasts in general.
I realised that the “algorithm” was also indirectly automating my self-censorship. Deliberate omission drives clarity. Fearful omission muddies.
Navigating the constraints imposed by a new medium is fun. Challenging and hard, but it is fun. If you enjoy writing, navigating new formal constraints to that writing means engaging with exactly the tasks and puzzle-solving that make the process fun.
Writing for voice means you need to reassess your sentence structure, pacing, and pauses. A pause in the right (or wrong) place is all it would take to turn the opening section of this essay on the word “seminal” into an exercise in camp.
Writing for something that will appear on the screen, even just a talking head, means you now have to be aware of the connotations the visuals might add to the text.
Facial expression while narrating the same line can be the difference between:
- “I’m making fun of myself.”
- “I’m making fun of you.”
- “I’m making fun of these people both you and I dislike.”
- And “I’m actually being quite serious now and not making fun of anybody.”
Thinking about the different ways a sentence can be interpreted is one of the tasks that makes writing enjoyable.
Following each of those thoughts is a choice and any choice you make is an omission – implied self-censorship – of the choices you don’t make.
Creativity is shaped through deliberate omission and seeing how the audience reacts, but in an algorithmic medium each choice risks creating a completely different audience.
This leaves you and me, as writers, with one of two, well, choices:
- You can ignore the algorithm and hope that the less algorithmic audience features, such as following, leaves you with a stable baseline that won’t be threatened by future alterations to the User Interface or notifications.
- You can stifle the urge to explore the form, stick with a set structure, format, and approach, and tailor your work to the audience automatically generated by the algorithm. Live by the algorithm; die by the algorithm.
Both are equally valid choices. Especially since not everybody has that urge to explore the form. Consistency can also be a virtue. Not everybody enjoys making choices, especially creative choices.
The audience, especially, should have the freedom to choose how much of a burden it takes on by viewing or reading.
Creative choices can be a burden #
Having to consciously assess everything and constantly have to choose during every waking moment would be exhausting.
This is essentially why those of us with the neurotypes commonly labelled autistic more often than not find social interactions exhausting. The interactions, assessments, and responses that are automatic and unconscious to the neurotypical are conscious and take effort for many who are neurodivergent.
Unconscious processes can be a blessing – a relief.
It’s more than understandable that people, as audience, often don’t want to make choices.
Choosing media that is easy to unpack and reassemble in your mind, media that takes little conscious effort on your part, is a valid choice. I personally think that familiarity – choosing media you already know – is a better path towards a genuinely restful cultural experience than letting predigested slop ooze over you, but I understand why people opt for it.
It’s also a question of balance. Knowing that Josh Johnson has a consistent style and approach and that his YouTube channel has a predictable schedule is part of what makes his stand-up comedy a kind of cultural “comfort food”. You can usually guess in advance what the topic and structure of the video will be, but even though you know what he’s likely to joke about, you don’t know what the joke itself will be, and the framing stories that give his performances their heart is different every time.
Audiences respond to and appreciate a range of different opportunities for choice when experiencing media. Sometimes they like “difficult” media that needs active focus and engagement. Sometimes they want to lie like a slug under their weighted blanked and recharge while going “haha! He made fun of Elon Musk. So funny.”
The choices made by the creator are trickier to avoid.
Creativity made without decision or choice is slop #
I wrestle with these questions and thoughts because writing without making choices – writing that’s assembled out of shortcuts, unconscious clichés, and predictable structures – is slop. The text and images generated by machine learning models may be the purest form of this kind of slop, but the genre has been with us since the first writer who recoiled from the intolerable burden of conscious choice retreated to the restful safety of an unconscious formula, uncritically adopted.
Making a choice can be painful. Poor choices stand out just as much as the good ones do. Many people don’t want to be noticed for being different. They have the impossible and paradoxical desire to be noticed for being the same as everybody else. They want recognition for their outstanding compliance.
They don’t want to be inventive on LinkedIn; they want to be noticed for playing by the rules of the platform extraordinarily well; they want to be uniquely not unique and be rewarded for exemplary blandness.
Slop is this automation of unconscious shortcuts, blended into a beige ooze, and poured into whatever shape is demanded by the algorithm or platform on that day.
It lets you be recognised for association with creativity while avoiding the risks of creativity.
Large Language Models are just one mechanism of many for accomplishing this. It’s a convenient automation, offered for a convenient price, but because slop is a larger phenomenon – not a unique consequence of a single technology – it’s a trap that we all need to avoid.
It’s easy to fall into repetition, to always play by the same structure and rules, to never vary your choices and always opt for ease and the sort of indistinct message that rewards lack of effort.
The creative act in modern media is a stormy, hard-to-navigate strait. On one side we have algorithmic media – the audience automations that abstract away the call-and-response exploration of your creative community – and on the other side we have algorithmic tools – the temptation to rid yourself of the pain of creative choice with the click of a button. Both jagged edges are shattering.
Thankfully, there’s more to this ocean than just those two cliffs.
The foundation of Josh Johnson’s work I mentioned earlier is his audience. Not his YouTube audience, though they are a big part of his platform today.
No, the foundation of his creative work are the audiences he has had to work with outside of YouTube. His stand-up is shaped by the people in the room where he’s performing. The Daily Show has a following built up over many years, and they define the work done on the show.
When he steps into those spaces and engages with those audiences, that exploration helps define and drive the work. YouTube’s algorithm adds to it and expands upon it, and I’m sure his team sees regular variations in the algorithmic response to the videos, but his work is not dependent on YouTube’s algorithmic traffic. Losing it would be a setback, but he would still be left with a foundation to build on.
This should make it obvious that search was yet another algorithm with the same risks and pitfalls as the platforms driven by recommendation.
Search was literally just a recommendation algorithm that responsed to key phrases. A review or blog post didn’t pop up in anybody’s recommendations, but through search its audience was nonetheless algorithmically tailored to that particular type of writing. Along with the dependence on algorithmic social media, most online writing was even more driven by and dependent on audience automation than your average YouTube channel.
Much of our media became dependent on the search and social media algorithms consistently delivering them a particular audience for a particular consistent and unchanging form of writing.
That went away because Large Language Models made it simpler to automate the slop than it was to automate the construction of an audience for manually created slop. Less lucrative, as it happens, but certainly simpler. Even without generative chatbots, none of this made for a stable foundation for our cultural and media industries.
Community is culture #
These questions have an answer. The loose, informal communities that form around newsletters, blogs, and podcasts – the non-algorithmic media that remain – are the only audiences that have any chance of lasting. They’re the ones we, as writers, need to understand, and that understanding can drive our creative choices.
The algorithmically-assembled audience that comes from search and recommendations is an army of ghosts. If you’re lucky, they’ll come to you when you make something that resonates with them or with the moment. Otherwise, you’ll still have your actual audience – your actual community.
I’m not going to let YouTube, or the desire to succeed on YouTube, drive my choices. Newsletter comes first, then the podcast, then the YouTube channel.
That’s the priority of constituents.
That means that even though I’m planning to continue to deliver essays in text, audio, and video when I can, I won’t let the concerns of video limit what I write for the newsletter.
I’m not going to let the ephemeral algorithmic audience dictate what videos I make, and I’m sure the videos will find their own core audience in time.
This way I won’t drive myself into anxiety chasing the mirage of getting into people’s YouTube recs.
-
Writing is Magic; Machine Writing is Ash
A couple of years ago I found some of the old journals I’d kept when I was a teenager. Some of the thoughts in it were innocuous and silly. Some of them were heavier – had a weight I still carry with me today – especially the passages I wrote when I was hospitalised for a summer.
None of it’s great writing. But all of it helped at the time. Taking thoughts and putting them down into writing helped clear them, structure them, and turned them into a foundation I could build on. It helped me deal with crises and changes.
The magic of writing is this ability to witness the thought process, where somebody has used the piecemeal of words and sentences to turn incoherence into structure.
Where once there was little more than anxiety and an idea, there was now understanding.
Even when it’s your own writing, the thoughts that prompted the writing are long gone – “the past is a foreign country” as another writer put it – and even with your vague recollections your position is that of the reader and no longer the same writer.
Writing is magic even when it’s bad. The process is thinking. It forces structure in place of the anxious jumble of your mind.
It helps others order their own minds by witnessing your thoughts captured in lines.
Machine writing does none of this. It’s ash – the burnt embers of dead thoughts. It captures nothing, structures nothing, orders nothing.
Human writing is as close to mind-reading as we can get. It’s weird, lossy, and simultaneously substantial and insubstantial.
It magic even when it’s bad because it helps you think.
It’s magic even when there’s nobody to read it; the life it gives to thoughts always helps the writer, even when they sit alone with it.
So, I’d just like to echo and extend what Andy Bell wrote on the Piccalilli blog:
This article is mainly addressed to fellow educators, but also to people that write on their personal blogs. You must keep going because people still need us. If we don’t, we lose.
Writing is magic. It’s always been magic. The vikings thought bound language bound reality and reshaped it. It gives our thoughts shape.
Writing is always a gift. Bad or good writing. Sloppy or structured. Planned or improvised. It’s all magic.
Don’t let the mirage of generated, extruded, letterforms, hollow bubbles inflated by machines, take it away from you.
It’s a gift of magic you can give yourself.
Premium NewsletterWeekly suggested reading on the software and ‘AI’ crises with commentary and analysis
A year's membership in the Out of the 'AI' Crisis – Premium Newsletter.
Paid monthly the full price would be €84 EUR
You should be automatically enrolled into the newsletter after purchase.
-
Out of the ‘AI’ Crisis – Premium Newsletter launch and Halloween Sale
Overview #
- I’m launching a Premium Newsletter that runs in addition to the regular one. The launch price is €25 EUR for a year’s membership, which is a 50% discount off the annual price and a 70% discount off the monthly price. This Halloween launch sale lasts up to (and including) 1 November 2026.
- I’m also offering a bundle Halloween sale that includes all the ebooks and a year’s membership in the Premium Newsletter at €50 EUR, a 60% Halloween launch discount until 1 November 2026… Or, more than a 70% discount including the value of the annual Premium Newsletter membership.
- If paying annually isn’t your thing monthly subscriptions are available through Patreon, where paid members will be able to access the premium newsletter as posts. Those do not have a launch discount, but there is a trial period.
- I’ve also opened a Liberapay profile for donations. For those of you who want to support the newsletter, podcast, and YouTube channel, but don’t want to buy anything. You’re buying the happy feeling of doing good.
All the pull quotes I’ve highlighted are genuine comments I’ve found online during my research, usually lightly paraphrased to protect the identities of people complaining about their jobs and their careers.I’ve suddenly become “overqualified” for everything. Employers seem to want cheaper employees who use “AI” for everything. I don’t even mind using “AI” but they still don’t want me.
Out of the ‘AI’ Crisis #
Nobody talks to each other any more. We’re just shuffling bullshit back and forth.
Many of us aren’t doing well, even as our bosses tell us things are great.
The “AI” bubble is hitting a lot of industries, and it’s disproportionally affecting those of us who work in these industries over our managers.
Professional educators, people like me who used to help train developers, have seen their businesses evaporate. Teachers, illustrators, voice actors, writers, and translators have all had their careers threatened or even destroyed by “AI” tools offered with predatory subsidies, built using their own work, used without permission by tech companies.
My employer doesn’t want to hire a team, so I’m doing five jobs at once. Bugs keep piling up.
But it isn’t just the creative industries and education that are being hit. Software developers are among the worst affected groups.
Nobody likes this. Everybody is doing the same thing and nobody is thinking any more.
Arguing whether the job losses we’re facing in software are down to “AI” replacement, poor free cash flow, or dysfunctional stock market dynamics is splitting hairs.
No matter which take you favour, it’s all down to the “AI” financial bubble one way or another.
I don’t recognise my job any more. I’m a bot manager now, not a designer. The work isn’t mine any more.
You don’t have to look far online to see that many of us are in the middle of an identity crisis.
- Some of us feel complicit in the destruction being wrought by “AI”. Even if we haven’t directly participated, much of it is built on our shared work and sometimes years of contributions.
- Software development was unique. It has similarities with many jobs, but there really isn’t a job exactly like it.
- Tech jobs were supposed to be safe and, well, lucrative.
- Much like the creative and media industries, software development was a bit of a safe haven for those of us who don’t fit in a normal office job.
- Many of us genuinely thought we were helping build a better world.
I’ve been laid off, but I’m too tired of this industry to even want another job in it.
Even as the noose seems to tighten around software development as an expertise and field of practice, the widespread destruction cause by Large Language Models and image generation models, means we aren’t getting much sympathy, if any.
I like doing it myself. I like the work, but I don’t get to do the work any more. The job is to ask “AI” to do it.
Arguably the worst hit are those of us who worked on the fringes of tech – straddling the border between software and media or education. Both aspects of our job, both of our identities are in crises, and we have colleagues on either side of us that are frustrated and angry.
Very little of what we’re told by the industry itself makes sense.
Much of what the executive class are saying sounds outright bonkers.
My boss is a true believer in “AI” so the deadlines keep getting tighter and tighter, I use “AI” more and more, and it’s all very soul-crushing.
Ebook and Newsletter Bundle Halloween Sale for €50 EUR
Make this make sense. #
One worldview shared by many designers and software developers is if I understand it, I can fix it.
If I figure out what makes it tick, what people want from it, how it hangs together as a structure, I’ll see the thing – that one thing – that I can pull out, repair, replace, and everything will be fine again.
Please, let it be just one thing.
There’s no sense of victory in solving a problem now. I didn’t solve it. It isn’t mine.
It’s never just one thing. “AI” isn’t even just one thing, and it didn’t appear out of nowhere. The system that is tech, politics, and the economy together are what led us here.
But, because the whole is large, it contains multiple systems, each containing its own diversities. There are corners of the software or media industries that are less affected and might even offer ideas for how to go forward.
“AI” is not all encompassing. There are places to go.
But we do need to go out and look for our place in the big picture.
The industry’s culture is dying. And it wasn’t that great to begin with. I don’t believe in the future any more.
Premium Newsletter for €25 EUR/year
Finding a future to believe in #
I can’t fix this. We can’t fix this. The world is too large to be “fixed” by individuals or even communities. Otherwise, the globe would be filled with harmoniously competing utopias.
We might not be able to fix everything, but we can make some things better, and those improvements can accumulate.
Damaged doesn’t mean worthless or doomed.
It’s just… not as good as it used to be, which is a feeling we can all relate to.
Our skills may feel useless where we are now, but that doesn’t mean they are useless.
We can act and mitigate, but we need to do it with understanding.
The skills I’ve been building my entire life are being taken away from me.
Academic understanding is useful, but we need people understanding – we need our problems seen and understood from our perspective.
And we need honesty.
None of this will work if we just pretend everything is fine, that nothing’s wrong. Avoidance works for temporary problems, but honesty is the only blade sharp enough for persistent wrongs.
We’re not expected to write any code ourselves, and it makes me feel so replaceable.
Out of the ‘AI’ Crisis – Premium Newsletter #
I’m trying to figure out where I stand in the world, how my career and job has been affected. So, I began to research what others in my position are experiencing.
We are not doing okay, and many of us are feeling lost.
As I wrote above, I can’t fix things, but I can play a small part in helping us feel a little less lost, because that’s what I’ve been doing for myself – with my writing and my research – my entire life.
Even though there is never just that one thing to fix, figuring out how things work and how they connect does help us navigate them.
Sometimes it even lets us make things a little less awful.
That’s why I write the essays I write. That’s why I make the podcast and YouTube videos. That’s why I read and research. Understanding might not fix things completely, but it can partially mend them – make damaged things a little bit less damaged.
The entire team feels depressed. We aren’t shipping faster. Management is on our backs. We’re using “AI” for everything but nothing’s improved.
This work has always had to be subsidised by other paid work, whether through the sale of my ebooks or my freelance work.
But times are hard for us all at the moment. These days, the more I look for freelance work to pay the bills, the less time I have to for the newsletter or podcast.
“AI” is ripping my identity as a software developer away from me.
What the newsletter offers #
This is why I’m launching Out of the ‘AI’ Crisis – Premium Newsletter. It’s a paid weekly (at least) exclusive newsletter that collects commentary and suggested reading that adds depth and detail to the regular newsletter and video commentary I do.
- It collects suggested reading culled from the links I’ve posted on social media that week.
- I’ll provide additional commentary and analysis on that reading.
- Semiregular extra essays or columns.
The money it earns directly funds my writing and videos.
I also want to offer a fair deal, which is why I’m launching this as a Halloween sale with substantial discounts. This discounted launch offer lasts until 1 November 2026.
The flow of coding was almost spiritual. I miss that feeling so much.
There are three ways you can join:
- Premium Newsletter
A year’s prepaid membership in the Premium Newsletter. The regular price will €50 EUR for a year of updates, but I’m offering a 50% discount at launch until 1 November 2026, so €25 EUR single payment (non-recurring) for twelve months membership.
Premium Newsletter for €25 EUR/year - Halloween bundle
You can also get that same year’s membership as a part of a Halloween bundle sale that also includes all the ebooks at €50 EUR single payment (non-recurring), which is almost an 70% discount until 1 November 2026, if you include the value of the Premium Newsletter membership.
Halloween Ebook and Newsletter Bundle for €50 EUR - Monthly Patreon
But if you want automatic monthly payments instead then monthly subscriptions are available through Patreon for €7 EUR a month, and members of the paid Patreon tiers will be able to access the premium newsletter as posts.
Patreon Supporter Tier €7 EUR/month
The amount of work I can put into my writing is directly proportional to how well the premium newsletter sells. So, the better it does, the more I can add to the newsletter, podcast, and YouTube.
I really do need your support, so I would appreciate it a lot if you spread the word, and let people who might be interested know.
-
Autumn comfort cat photos
Given the state of, well, everything, I figure the best thing to do at the moment is to post a few old cat photos. These are two-year-old photos of a couple of my neighbour cats. They’re still around these days, just two years older, so a bit quieter.
-
The 'AI' Software Crisis: Software Developers have been promoted into incompetence
Software Developers have been promoted into incompetence Developers have been promoted into incompetence #
With the age of “AI” and agents, software developers have been promoted into incompetence.
And it all comes down to comedy and satire.
Sort of.
That probably requires some explanation.
If you’re actually working in an industry – any industry – reading about management theory is often indistinguishable from reading comedy.
Not just because the reality of how you experience “management” is frequently absurd or grotesque, which the theories often fail to address, but also because the alternative to laughing at the mess, is to cry and despair.
When we – as people working in a deeply flawed industry – read about management theory and practice, most of us won’t recognise any of the “good” practices, but we will be intimately familiar with all the “bad” practices. We could even probably list a few more “bad” examples so awful that they have hitherto been unknown to science or sanity.
We’ve all had bad managers. Sometimes we’ve even been the bad manager.
Occasionally you do get a management book that leans into the inherent comedy of the farce that is the reality of the modern corporation.
Like the book Management of the Absurd by Richard Farson. It doesn’t take itself seriously, has a few useful pointers, and is appropriately mocking at times.
But comedy has also made genuine contributions to both the theory and practice of management.
One of those being The Peter Principle, which has its origin in a satirical book of the same name.
The principle it describes is that people tend to rise through organisations through promotions until they reach a level of respective incompetence.
What it means it that you or I might work, say at coding, at an organisation, and we get good at our entry-level job. Our skills get noticed so we get a promotion that involves more important coding. Same skills, just better and more important. It builds on our skills, which is recognised, so we continue to rise through promotion.
Until, that is, we get promoted to a manager position that doesn’t involve coding. This position instead involves a bunch of skills we haven’t practiced at all.
At this point, it’s entirely possible that we might be worse at the managerial job than we were in the entry-level job where we started.
And because we are now incompetent, we no longer get promotions. We’re stuck. Our career has reached a dead-end because we’ve been promoted into incompetence. We’ve become bad at our jobs through no fault of our own.
Why software industry career ladders have been different #
This has especially been a problem for software companies. The job of a software developer has traditionally been very different from that of a manager.
- Coding lends itself to a singular focus during each task. Management requires juggling tasks.
- That singular focus means coding is very light on the kind of monitoring work that can be a big part of management.
- Coding lends itself to unambiguous communication that deliberately strips nuance and ambiguity away. You mean just what you say and nothing else. Management communication is almost entirely nuance and ambiguity.
- Management is all about coordinating unruly “processes” to make sure the work they do is delivering value to the organisation. Busywork of no value is worse than idleness because idleness actually reduces delays and shortens task queues. You can’t react quickly to an unexpected need, if you’re occupied with busywork. But you can react immediately if you’re idle.
Management is all about maintaining a constant vigilance towards the bigger picture: the queues, the delays, where value is being created and destroyed, avoiding both over- and under-optimisation, and coordinating things that are unruly and chaotic.
And, normally, somebody who manages coders rarely codes themselves.
The two jobs are very different. Promoting a coder into a manager frequently means the company is losing a good coder and gaining a bad manager.
The consequences of gaining a bad manager are also quite different from what many imagine. The result of bad management isn’t that work won’t get done, it’s that the wrong work gets done – that everybody is running around, overworked and busy, but none of what gets done has any meaningful value to the company.
Busywork.
This is why many software companies have historically had a separate career ladder that doesn’t involve management. That way the company can give a talented software engineer a respectable career trajectory without losing access to their valuable skills.
“AI” and the changes it has brought to software, have together thrown all of that out the window.
The “agentic” decline #
With “AI”, the software development job involves:
- Constant monitoring of unruly and chaotic “agents”.
- That are coordinated using ambiguous and nuanced language that never seems to be completely “understood” by any of the participants.
- Constant juggling of a variety of tasks.
- And it no longer involves focused work but instead requires outlining, commanding, and specifying.
And, despite managing a lot of code, developers now rarely seem to code themselves.
Software developers is a field so universally recognised as being poor managers that many of the stiffest and most conservative organisations on the planet gave up and just gave them their own career ladder. And we, as a field, have all at once been promoted into management without any preparation or training.
Because the processes a developer is managing are nondeterministic and chaotic – more so than any human – this new management job is in many ways harder than that of a regular manager.
We’ve taken an entire industry that was so-so at its job – at best – and pushed it into outright incompetence.
The result is very similar to what happens when you have a bad manager.
- Busywork increases.
- Nobody has any visibility into where value is being created or destroyed.
- Pressure and stress increase because of the added uncertainty.
- More busywork means less slack in the organisation.
- This actually increases delays, lengthens task queues, and magnifies costs.
- Communication becomes harder.
- Concrete and actionable information becomes scarce.
And nobody has any time left to spare, to figure out what it is they’re doing wrong. Nothing improves.
Because – remember – the consequences of bad management isn’t that nothing gets done but that there’s too much of the wrong work getting done.
That’s not the worst part.
The worst part is that even though this new job many of us have landed in is similar to management, it still isn’t actual management. It’s a new thing made up of some of the worst parts of the managerial job.
The worst part is that it’s automation, and that comes with a bunch of fairly insidious downsides.
Deskilling from automation #
People have been studying the effects of automation for decades. One of the core ideas from that research is the paradox of automation.
Paradoxically, the human contribution tends to become more important the more reliable the automated part gets.
This means that better automation can lead to worse outcomes, because it shifts the work of the human from tasks they’re good at, to tasks they aren’t.
The 1983 paper that originally coined the paradox, Ironies of Automation by Lisanne Bainbridge covered a number of different “ironies” that each independently undermine the value of automation, but the irony that’s the most relevant to the software industry today has to do with the cognitive effects.
One of the concerns she raised all the way back in 1983 had to do with deskilling.
Quite a few of the skills we have are perishable. What that means is that once we stop practicing a skill, some of it begins to fade away. That’s why we talk about “being rusty” at something if we haven’t practiced in a while.
One of Lisanne Bainbridge’s observations was that cognitive skills that rely heavily on both memory and a coherent mental model of the job are more vulnerable to this decay than the skills that don’t.
Human memory relies on repetition and regularity and mental models need to be built and then maintained.
Once automation kicks in, that regularity, repetition, and maintenance disappears.
Memory and mental models are a major part of the programming skill set of a software developer.
It seems likely, to me at least, that the kind of automation presented by agents – where our existing triggers for reinforcing memory and building mental models now instead trigger external automated processes – will lead to the steady deskilling of the developers who rely on them.
This matters because many of the other parts of the new job that developers have – the monitoring and the reviewing, specifically – rely on us continuing to have those skills.
In addition to destroying value through busywork, poor coordination, delays, and longer queues, this new automation is also lowering quality in the long term by removing the skills we need to monitor that quality.
All this, while being charged by the token.
This should matter to us – the developers who are facing a changed industry – because this process is genuinely quite unpleasant to live through.
It takes away the enjoyment we had in the job. It adds stress. It increases the odds of burnout. All at a time when layoffs are still in fashion among the executive class and jobs are precarious.
There are a few things we can do about this. Not many and not all of them great. But we do have a couple of options.
What can you do? #
The most sensible “AI for software development” strategy over the past four years has always been the same: wait and see.
This has been the most sensible strategy, in general, for software firms over the decades.
This industry has a tendency to adopt innovations too quickly and recklessly, before their flaws come to light. Much of it flames out in crappy products.
Then the same people who caused the problem make money again by fixing it.
It doesn’t matter whether it was NoSQL databases, GraphQL, or SOAP network protocols, it’s always been sensible to wait and see what the long term downside to a technology was before adopting. First mover advantage is non-existent when it comes to adopting new techniques or tools for making software.
So, the most sensible strategy is to wait and see. And the second most sensible one is to stop. Just pull back, regroup using regular software development approaches, and then wait and see.
If deskilling is really a thing, you’ll end up with an advantage over your competitors.
If agent-using developers really have been promoted into incompetence, you end up with an advantage.
If somebody discovers fixes to all of these downsides, you can adopt the fixed workflow without ever having experienced the downside yourself, and you end up with an advantage.
That obviously isn’t possible in an organisation that measures volume of work instead of the value of work. And it doesn’t help if your clients are organisations intent on shipping features instead of making good products or services.
In those cases, you need to find ways to maintain your skills and develop those new management-adjacent skills, if they are at all possible. And you need to do it at the same time as you’re working what is probably more than a full-time job.
This is obviously much harder than just doing the job as you’re told and letting both quality and your own skills degrade. And if your self-improvement is seen as taking time from your job of churning out slop, all you’ve accomplished is put your own job on the chopping block.
Good managers and executives with a focus on long-term growth wouldn’t put you in this spot.
So if this is happening to your workplace you already know that the people you’re working for are either themselves incompetent, or are letting their short-term greed harm the company they’re running.
A competent executive would not have created a system that promoted a big chunk of their workforce into incompetence.
This means that, if nothing else, you can take from all of this one hard fact:
Whatever happens next – to your employer, to the software, to the market – is not your fault.
That may not seem like a comforting thought today.
But there’s a good chance that thought might bring you some satisfaction – even joy – over the next two or three years, as events unfold in the industry.
Patreon #
If you want to support my work and want me to make more of these videos, essays, and podcast episodes, the best thing to do is to become a member of my Patreon.
But I’m also trying to provide a service with my Patreon. With the state of social media and search as it is, keeping up can get quite difficult. There’s so much noise and so little signal.
One of my strengths, because of my background and training, is that I’m quite good at researching and reading, so one of the things I’m offering to Patreon members are regular updates where I recommend things to read, with context and commentary.
I post these reading updates every other day or so, and I’ve got plans for more member-exclusive features, some of which I think might even be a bit exciting, but I’m obviously quite biased.
I’m also open to suggestions, so send your suggestions my way, either on Bluesky or Mastodon, but I’ll try and monitor the comments on YouTube as well.
-
It’s not our job to fix our employers
Contents #
I have a Patreon! #
I’ve been writing since the 1900s (technically the late 90s, but still) on the web, about the web, and, over the past twenty years or so, about software development and publishing.
I’ve been here a while and am not going away.
But I’d like to write more, make more videos and podcasts, and specifically look at the problems we have who are now outsiders in our own industries, whether that’s in software development or in publishing.
For that, I’d like your help.
Hence, a Patreon.
It’s going to offer exclusive material, support tiers, and hopefully a few novel goodies that I’m working on at the moment.
Currently, it has two membership tiers:
- Supporters, who get access to all the stuff. €7 / month.
- Patrons, who get access but also mentions in the newsletter, podcast, and are listed at the end of the video. €25 / month.
Any support you can give is very much appreciated.
Video #
Audio #
It's not our job to fix our employers This broken industry is too big of a problem for software developers to solve alone #
As I wrote in my last newsletter, software developers don’t seem to be doing well.
I can relate. I’ve been unlucky enough to work for dysfunctional software companies and startups in the past, and those dysfunctions have increasingly become the norm across the industry over the past few years.
The response was greater than I expected, both on the newsletter and elsewhere, so I wanted to pause and try to put those responses into context.
I had already written and recorded the next couple of videos and newsletters even before I uploaded the last one, but I’m postponing those, because I think it’s important to sometimes stop and listen instead of constantly lecturing at people.
Even though most of the responses were positive – at least, positive in the sense that they could relate to or recognised what many software developers seemed to be going through – some were less supportive.
This is the internet. Obviously some people are going to be annoying. Most of it you can ignore, but a few of them highlighted the big shift in attitudes towards tech that has been taking place over the past decade.
People aren’t on “our” side any more. Quite a few have gone from having largely positive feelings towards tech – considering it to be a force for progress – to thinking it’s an industry that’s ruining the world.
Tech is the new tobacco.
So, if we’re miserable, the attitude some have is that it’s our own fault for making the world we live in worse.
Or, that we deserve what’s happening to our field because we didn’t do enough to prevent bad things from happening.
Or, our work in the tech industry, no matter what it was we actually did, means we have it coming.
This is what falls out from the now relatively common public sentiment that tech is the new tobacco industry. How that framing has played out in media coverage and discourse, has quite correctly emphasised the abuses, the legal shenanigans, how tech is spending money to manipulate the public, and other strategies that the tech industry seems to have copied from big tobacco.
But the other consequence of that shift in public sentiment is: if your industry gets the reputation of being like the tobacco industry, people stop having any sympathy for those of us working in that industry.
Nobody cares if a sales person in a tobacco company burns out from stress or pressure. If your job is selling opioids to college athletes – “but it’s legal! I’m only helping doctors decide on the correct treatment” – hearing that you’re suffering will only make people smile. Now, finally, a sign that the world is just place.
This is a little bit unfair to many of us for two reasons:
First, the industry wasn’t this bad when most senior people in the industry started. You don’t have to have gone into coding thirty years ago, like me, to have had reason to believe it was an industry with promise. The sentiment shift has been happening for a while, but it was a gradual one for a long time.
Second, quite a few of us have spent our careers avoiding the kind of work we felt was harmful to society. We’ve tried to do good and our careers and finances suffered for it.
Related to this is another idea that came up. Some people seemed convince that we who work in the industry could have prevented all of this, if we’d done this or that. Most of them mentioned unions. If we’d unionised years ago, none of this would have happened.
The problem is that this is almost certainly false.
Unions are largely absent from the software industry in the United States.
But software development is largely unionised in quite a few European countries. Those unions, many of them large and relatively influential, haven’t stopped the job from changing for the worse here in Europe in many of the same ways it’s been declining in the States.
Union participation in Iceland is well over 90% and is almost certainly higher than that in software. We’re still seeing lay-offs in software development, fewer opportunities for junior developers, a push towards using Large Language Models to make up for all those fired colleagues, and a collapse in college enrolments in computer science.
It’s hard to see how software developers and other employees could have prevented this change when it’s fundamentally driven by much greater forces in policy, economics, and deregulation. These are problems that can only be fixed through politics, not unionisation.
But even if we could have prevented it by forming unions in the States, that still doesn’t make it our responsibility to fix a toxic employer.
Think about it this way:
Imagine that a friend of yours is working retail. The manager is awful. The company has abusive policies. The retailer’s overall strategy is to treat employees as disposable and cheat the customers as much as they can get away with.
You’ve shopped there. You know what I’m talking about.
A labour union will absolutely help prevent the worst abuses your friend is facing. It’ll keep them safer while they’re working for the abusive retailer, and it might give them some leverage when dealing with their employer.
But the union won’t fix the retailer. It won’t make the manager less toxic and won’t stop them from micromanaging. It won’t prevent the retailer’s abusive tactics against their suppliers, which will come back and impact your friend. It won’t make the retailer less abusive towards the customers. It won’t prevent lies, monopolistic tactics, mismanagement, financial fraud, or the pervasive outright incompetence of much of the management. It won’t prevent middle-managers from resorting to superstitions or coercive manipulation.
It certainly won’t prevent them from hire a sociopath CEO.
A union can make a workplace safer, fairer, and more equitable. A large union can function as a political force that will help change society for the better. The big reason why Iceland is a largely progressive society despite having had very right-wing governments for most of the past four decades is at least partly thanks to our strong labour unions that advocate for their members.
But once you’re in the situation where deregulation, financial incentives, mismanagement, sociopathic managers, or owner politics have turned a particular workplace toxic, a union won’t suck out the toxins, and it won’t fix that broken employer.
It’s all well and good to talk about the industry as a whole and how it needs to be fixed, but individuals need to think about their own health and their own survival first before they can worry about saving the world.
Fundamentally, it isn’t the job of an employee to fix their employer. If your workplace is a broken mess and that’s causing you to suffer, the sensible thing is to try and look for an exit while you still have your health.
Because you can’t buy back your health once you’ve lost it.
-
Ravens and churches
A couple of years ago I noticed that one of the local ravens was perching on the town’s church steeple and serenading the surrounding area with the song of their people. The photos have ended up being one of my favourite sequences of images.