No se si entiendo el concepto de que un lenguaje se vea feo o lindo. Maa bien esconde lo que hace por detras o lo muestra. O bien entendes lo que ves o no lo entendes, según lo que sabes del lenguaje.
Python supuestamente es fácil de leer y se puede hacer código bastante feo
Getting enough of it was always the biggest problem.
Initially that drove companies to try and hire more people. The problem is, adding more people required a reduction in skill level. This lead to the infamous “StackOverflow copy/pasters” who would regularly get stuck and required more senior people to pull their fat out of the fire.
The industry continued to try and expand on the “more people” theory. Frameworks were reoriented around “developer experience” which is often a fancy way of saying, “we made this a lot less effective and more expensive to build, but the low skilled guy is more likely to get something done.” Teams got less effective because the remaining skilled people got thinner on the ground.
Software quality took a nosedive and costs skyrocketed. When the free money (borrowing) ran out, that became a problem and everyone had to reduce costs.
AI comes along and says it will replace programmers.
Ok, so it doesn’t actually do that. But it will keep your copy/pasters from getting stuck!
It does do that. By ramming through whatever bad decisions your bad developers are making. Bugs skyrocket. Security issues go through the roof. And while there’s more code being generated (not actually a good thing) the productivity at the business level… doesn’t budge.
So now companies are paying twice for developers. (1 human + 1 AI) And they’re having more problems.
The major outages of the past few days are exactly what’s been expected out of all this AI code generation. Whether caused directly or indirectly, it’s not going to take many more before companies have to walk back the idea of generating all their code with AI.
@premun_@ClassicGamerTWR I think we can see modules as being part of a larger abstraction within a context. And libraries being reusable autocontained components with appliances in multiple contexts. Modules can be seen as libraries maybe, if reusable within a single context, but still modules imo.
@zashekov@Scott_Bailey_@echolocade I'm certain clean code and clean architecture greatly impact UX. A bad API route with a bad asynchronous pattern can translate to low responsiveness which in turn means the user waits more for stuff to happen. That's bad UX from bad code.
@Scott_Bailey_@echolocade That's usually what happens when poor design decisions are made. It's my whole point. LLMs repeat patterns and don't care much about module architecture, they just get the job done. That bothers me at least, because it goes against maintainability.
@Scott_Bailey_@echolocade Why do you think people bother to write clean code if not to guarantee proper UX? Proper maintainability? Don't you think good quality design equals a good quality product?
@klieber@oldstackjournal You did not. However I find interesting that you and many others seem to be reacting somewhat childishly to a rightful movement, and calling that a childish thing to do at the same time.
Asahi Linux is moving all its repositories from MIT to GPLv2 or later. They say that in some cases, in-development code was lifted from their personal forks and published without credit, or rewritten with an LLM to hide where it came from.
Their AI contribution ban gets called silly, but the stated reason is legal. Clean-room reverse engineering depends on knowing how the knowledge was obtained, and with an agent you often can't say.
@GergelyOrosz The problem with waterfall in software is not only time it takes to implement but also how implementation raises the questions that were not asked during planning that need answering. This AI does not solve. It usually creates bloats of code with the wrong business rules.
This is absolutely true.
AI is incredible—like breathtakingly, jaw-droppingly incredible—at building apps.
But it's total ass at writing. And hasn't moved an inch here in the last 2 years.
the most import skill in 2026 is still being able to tell your agents "wtf is this crap, no, not like this"
if you stop doing that, you're basically fucked, despite what some devfluencers would like you to think.