I have a former coworker who was born in the Soviet Union at a very specific time in history. He was just old enough to see the system from the inside and grasp how it works (or, more specifically, did not work) but young enough that it did not consume him. He got out fairly quickly after the collapse and is nowadays doing computer related work in "the west", as it were. Having seen both sides of the world order he had quite an interesting view on why the Soviet Union eventually crashed and how it ties to modern companies.
Let's assume that you are working in the Soviet Union in a car factory. Your job is to be responsible for all things needed to attach the wheels to the body of the car. In practice this means taking parts from subcontractors (typically other divisions of the same factory) such as break pads and lines, the actual wheels, and all other things and put them together so that the car can roll forward. Seems reasonable enough, right?
In practice it turns out that all parts you get are actually garbage. The wheels are not properly balanced. The inner tube might have a hole in it or be completely missing. The metal in brake pads has been silently changed to a cheaper one removing 50-70% of braking power. The brake lines are too short for installation. To make them work you'd need to cut holes in the car's superstructure. Your screws are too soft to properly function, but fortunately so are your wrenches. The downside is that after tightening one wheel all your tools are shaped like a banana. And so on and so on.
Should you find yourself in such a situation, what should you do about it? In theory the parts you are given are not up to spec. So you could file a complaint about it. But you really can't, because then the problem would be you. You would need to do the extra work of getting the people providing you parts to fix their process (which you can't do). You would need to file the paper work. Your name would be on every one of them. When higher ups get reprimanded for cars not getting finished fast enough to reach the requirements of the current five year plan, they are going to come looking for a scapegoat. You made a ruckus. You stopped the pipeline. You are the problem. You get punished.
But it gets worse. Not only are the people below you not caring and producing garbage work, so are the people above you. At every part of the chain nobody gives a shit, they just take things from below, fiddle with them a bit and then shove them upwards and hope that when things eventually fail, you can deflect the blame on to someone else. If you wish to survive, that is what you must do also. This, according to my coworker, was what eventually brought down the Soviet Union. When all organizational layers of an entire nation gets filled with garbage in – garbage out shovelers, the system loses its capability to function, becomes a zombie, wanders on aimlessly and eventually dies.
He claims to have witnessed aspects of this appearing in the organizational chains of several software companies and that he has tried to warn them about the bad direction things are heading. Usually to deaf ears.
But what about today?All of that happened years ago. The question is whether any of it still matters in this, our Shining New Era of AI. It most definitely does, more than ever.
Any organization can tolerate a small fraction of employees that don't particularly care about "the job" and are just hanging around putting in the minimal amount of effort they need to to still remain employed. That is just how large organizations work. The problem is ratio, and this is where AI comes in.
One of the main non-technical changes AI has brought about seems to be the wholesale conversion of formerly competent and caring people into garbage in – garbage out shovelers. We see them all around us every day. Like the people who handle all emails sent to them by copypasting the entire email thread to a chatbot, asking "what should I reply to this" and then copypasting the entire thing (including the prompt) back as their reply. Or software developers who used to be smart, knowledgeable and competent but suddenly resemble Alzheimer's patients who reply to merge review questions such as "why did you do this thing here" with "I don't know, Claude told me to" and then merge their code without fixing any of the issues raised.
All of this is exacerbated by all the recent layoffs in the tech sector. No doubt this has been used to rid the company of those pesky troublemakers who dare point out flaws in The Perfect New System. Those who know their history might remember that this was the preferred tactic of Stalin (though, granted, his methods were more extreme). As firing people saves money immediately and only causes problems with a delay, this is seen as a good thing and managers doing it get rewarded.
And this is where we are today. Many formerly good organizations have become or are on their way to becoming lumbering hulks that can no longer properly function and will eventually collapse under the weight of their own incompetence. You can already feel this with the recent outages of Microsoft cloud and other services. Things that should have worked just breaking down randomly without anyone really knowing why was an every day occurrence in the Soviet Union. People just shrugged it off as an unavoidable fact of life. That is the direction we are heading.
The last laugh of LeninThe latter half of the 20th century was a battle between communism and capitalism. The latter won and having its world view validated went on to an even more extreme end of ultra-capitalism. The ultimate irony is that eventually it reached the exact same end state as communism: an absolute unwavering ideological religion. Which is made all the more amusing by the fact that both of these movements were meant to be fully atheistic.
In communism the country was filled with party leaders who were vocal that communism would lead to "the workers' paradise" which was "within our grasp just over the horizon", we just have to give it some time. The average person, on the other hand, did not believe a word of this nonsense, just pretended to care to get along with their life.
I communism 2.0 we instead have CEOs claiming that AI leads to "freeing humanity from the shackles of work" and that "the cure for cancer is just over the horizon", we just have to give them infinite amounts of money first. The average person does not believe a word of this nonsense, just pretend to care to get along with their life.
At least the Soviet Union had the banging Red Army Choir. All noises the techbro CEOs seem to be capable of producing seem to consist of whingy stuttering and vocal fry.
Apart from Teclas, few months ago I started another small application called Mundi, Mundi is a geography learning application for GNOME. It all started from an assignment from the teacher of my kid where they had to use the following web page: https://mapasenriquealonso.com/
The web page is actually quite nice but it pissed me off that it had publicity. So I said to myself, what if I make a clone but better for GNOME? Since then I started adding maps and different exercises and I think the application reached to a pretty good state.
When you start the application you get to select the country or a region of the world you want to learn.
The country may have different exercises.
Once you select the exercise you want you can either select the different regions to learn what they are or you can click on “Start Quiz”.
The quiz will start asking you the different regions and you have to click on the right one. It will account for the timing.
Once you are done it will give you the result and you can save your name.
I’ve been playing it with my family and colleagues and it is really funny. It is also interesting to discover how bad you are at geography when you start playing with it!
If you maintain an open-source project right now, your pull request queue probably looks very different than it did two years ago.
I maintain SwiftTerm, an open-source terminal emulator library that is now seven years old. Today, I estimate that about 80% of the pull requests I receive involve AI in some capacity. Looking back, though, this didn't happen all at once—it came in distinct waves.
Disclosure: as a Mexican national that routinely writes tedious and typo-ridden English blog posts, I had Antigravity fix my writing and repeated tedious and repetitive points (as my wife often points out).
Wave One: Vibe-Coded Band-Aids and Fork ExperimentsBefore people even started opening AI-assisted pull requests on my repository, I would browse the GitHub network graph just to see what forks were popping up and what problems users were struggling with. Early on, what I found was a lot of "vibe coding"—folks patching around issues in ways that were fundamentally wrong, slapping surface-level band-aids over deeper terminal state bugs. I would fix or implement the feature, despite the fact that the user had not submitted the fix - for the sake of helping all my users.
In one fork I stumbled across, someone had clearly unleashed an autonomous agent to try to fix all of my open issues in rapid fire. Luckily, they never actually submitted those PRs—they were likely just experimenting—and it was only my nosy self browsing the network graph that spotted it. Still, looking through those commits confirmed the early reality: the fixes weren't worth merging. They solved surface symptoms without understanding the system.
The Rise of the PromptsplainerAlongside those early waves came a new open-source archetype—one that many communities had to deal with: the Promptsplainer.
Some folks are really eager to particiapte in improving a project and LLMs have opened new doors, but they lack some basic etiquette.
A Promptsplainer is someone who asks an LLM a question, gets back a confident-sounding explanation or a sprawling patch, and suddenly believes they can override decades of hard-won domain expertise. They don't actually understand the underlying quirks, race conditions, or protocol edge cases of the codebase they are touching. When a veteran maintainer points out a flaw, the Promptsplainer doesn't go investigate the code; they just copy-paste the maintainer's review comments straight back into their chat session and paste whatever the bot spits out next.
You don't need a massive daily flood of Promptsplainers to feel the damage. Even the occasional encounter can fill a maintainer with rage - and with good reason.
Wave Two: "Send a Patch" Finally Became RealHere is what has changed dramatically over the last year. We went from AI fixes being flat-out wrong or lazy band-aids to pretty much landing in the right ballpark.
To appreciate why this matters so much to me, you have to remember what maintaining an open-source library looked like just a few years ago. Back then, I would get a steady stream of bug reports—and if I had the spare time, the patience, the kids went to sleep early, and my Netflix queue was empty, I might actually sit down and fix the bug.
For decades, open-source communities had a semi-joking, semi-exasperated stock response whenever a user asked, "Why doesn't it...?". We told them, "Patches welcome," or "Send a PR." Most of the time, we knew they wouldn't, because diving into a complex codebase from scratch was too steep a climb. The perfect storm between unpaid volunteer work, uneducated takes and exasperation.
Like many others, I have witnessed the change from getting bug reports to getting detailed pull requests. And I am personally grateful for this.
My philosophy on incoming contributions comes down to a simple reality: every PR represents a real pain point caught in the wild. It means a real user ran into a problem in their day-to-day work, reported or tracked down the issue, found a working solution, and felt the pain acutely enough that they took the time to package it up and upstream it.
As a maintainer, that is an infinitely better signal than my own laundry list of wish-list items sitting in the issue tracker. Even if the implementation needs additional work, someone just handed me proof of a real-world problem along with a concrete starting point to fix it.
Multi-Agent Code Review on My Side of the TableThe catch is that many coding models and agents still have a bad habit of just doing the fix—taking the shortest path to make a test pass without stepping back to look at the whole library. And not every contributor has learned how to tune their agents for deep engineering review, or has access to the best models for it.
The first pass of AI-generated code often needs work, and that is okay. Just as we spent years developing the discipline to master our programming languages, debuggers, and in some cases, write m4 macros, we now need to develop the muscle for using AI tools effectively—learning how to steer them, verify their assumptions, and audit their output.
For me, building that muscle meant putting AI on my side of the table to bridge the gap. Before I even bother reading a contributor's patch line-by-line, I religiously run /code-review in Claude and /review in ChatGPT [1].
These review passes routinely catch far more than narrow syntax nits—they surface genuine architectural flaws, subtle API breakage, rare side effects, and terminal conformance problems that would take me hours to trace manually [2].
Armed with that feedback, I can point contributors toward concrete architectural fixes—or, if someone disappears after opening a PR for a critical bug, I can clean up their branch and land it myself.
Some maintainers lament that reviewing these PRs feels like talking to someone who just copies and pastes feedback into a remote LLM. But we are still communicating with a human being on the other end. That gives us a real opportunity not just to coach contributors on how to use these tools responsibly, but to model and adopt better engineering practices across our industry. Given that the economics of top-tier reasoning models aren't ideal for everyone doing casual open-source work, I’m happy to foot that bill on my end for the sake of keeping my library healthy.
The Friction of One-Size-Fits-All RulesThis brings me to why I’ve been watching the broader debate around AI policies in large projects like Gnome and Godot with a lot of sympathy—and a bit of concern.
At Godot's massive scale, protecting volunteer reviewers from unvetted submissions and the occasional Promptsplainer is a completely understandable instinct. Nobody wants their Netflix time eaten up by drive-by code the author didn't bother to understand.
The challenge is that drawing hard lines around how code was written inevitably creates friction for experienced contributors who are already doing the architectural heavy lifting. Recently, I tried to upstream a small, production-tested bug fix to Godot as a trial balloon—one of roughly 60 to 80 improvements my team has built and tested in our own tree. Because I disclosed my AI workflow honestly, it ran afoul of their strict guidelines and was rejected.
When a policy polices provenance rather than quality, two unintended things happen:
The Promptsplainer is a real headache, and open-source projects are right to push back against uncomprehending, drive-by contributions.
But the antidote isn't banning the tools—it's requiring human accountability paired with better review tooling on the maintainer's side. At the end of the day, as the maintainer of a library, it is my role to make the editorial decisions about what goes in—and the people who depend on my library trust me to make those calls. Whether a patch started in an LLM prompt or was typed out by hand doesn't change that responsibility. If a contributor understands the problem, has tested the fix, and can engage thoughtfully in review as a human being, the models they used in their editor shouldn't disqualify their work.
Of course, scaling that kind of review culture when a handful of core maintainers are already stretched thin is a structural challenge all its own.
[1] With Claude I use Opus 5.5 alongside /review in GPT 6.2 with Sol-xhigh. In Claude, /code-review actually launches multiple distinct agents in parallel, each focused on different goals and common engineering mistakes. Looking forward to Antigravity to get this.
[2] In fact these reviews are so thorough, that I use /code-review on my own changes before shipping. In a seven-year-old codebase, it is impossible to keep every historical invariant in your head at once, and those agents regularly catch edge-case scenarios I had completely forgotten about.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Today we are launching the GNOME Foundation’s 2026 end-of-year fundraiser, and we need your donations to help build a stronger, healthier GNOME ecosystem.
GNOME is an independent computing platform enjoyed by millions of people worldwide. What if a small fraction of them helped financially sustain it? Together, we could give GNOME the resources to accomplish so much more.
GNOME and the GNOME FoundationGNOME is a Linux desktop environment and collection of apps intentionally designed to be elegant, intuitive, and privacy-respecting. It’s the default experience on many popular Linux distributions like Fedora, Ubuntu, Debian, and Zorin OS.
The GNOME Foundation is the organization working to sustain GNOME, but its resources are stretched thin. We are currently limited to a handful of paid team members, most of whom are part-time.
GNOME exists today thanks to a global community of volunteers sharing their time, talent, and passion to build software that benefits millions. They frequently juggle jobs, family, hobbies, and other commitments to accomplish this work. We see an opportunity to give some of these talented people the time, resources, and financial incentive to contribute more to GNOME.
The Fellowship is Making a DifferenceAnd thanks to your generosity in 2025, we were able to launch the GNOME Fellowship program in April 2026. The Fellowship allows us to directly support two talented members of this community, who in turn spend dedicated time enhancing the long-term sustainability and health of the GNOME project.
These Fellows are already making noticeable quality-of-life enhancements to your everyday desktop experience, and the underlying technologies that power GNOME.
In their first three months, Fellows Peter and Sophie have modernized the file previewer, made substantial improvements to image handling, and fixed many problematic bugs — some of which have existed for years. And that’s only a small sampling of what they’ve accomplished.
With your help, we can raise an additional $60,000 to sustain the fellowship program throughout 2027. Donate today, and let’s continue supporting the vital work our Fellows are doing!
Your Donation MattersGNOME isn’t just a desktop environment. It’s an alternative to a world where corporations decide how you should use your hardware, treat your personal data as a commodity, and disregard your privacy.
GNOME is a reflection of what we believe technology should be: open, empowering, and built to put the control back in your hands.
If you’re reading this, GNOME matters to you. And your donation matters to GNOME! Please give what you can today. Every single gift helps make a stronger, healthier GNOME possible.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.