@esoria_dev
🇪🇸Account based in
About this account
- Account based in
- Spain
- Connected via
- Spain Android App
Account-level information from X, not a live location or the device used for a specific post.
Durant l'horari laboral faig de tech lead de backend en @KaveHome. En el meu temps lliure faig cosetes a @festivaleswiki 🐍 #python #django #beer
València
Joined April 2022
- Tweets958
- Following404
- Followers91
- Likes4.1K
Y ahora estamos generando esta cantidad de código terrible a una velocidad 4-5x.
Enrique Soria retweeted
There's a meta question here:
Why did all these get published yesterday? Is it reasonable to suggest that some people thought it was a "good day to bury bad news" - be one item in a list of shit, not the main news story.
xitter.cf/fiveoutofnine/status/2…
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
Enrique Soria retweeted
As I manually type more code (Yes I am a dinosaur) and review my code using AI tools, I am finding how bad AI suggestions are from an architectural perspective. It behaves like a teenager, who when asked to clean the room simply pushes all the garbage under the bed.
When I confront AI with those bad decisions it says "Oh yeah you are right....".
I really don't understand how people are 100% trusting AI and committing all the code without reviewing.
Enrique Soria retweeted
The AI agent fatigue is real. Unfortunately, software development has historically been measured by lines of code. And now that coding agents can generate 100x more code than humans, software engineers are expected to do 100x more in the same amount of time.
But managing AI agents is much more exhausting than writing code or even managing human developers.
The context switching drains your mental energy. You’re constantly working on System 2 thinking, which much more exhausting than the flow of implementing a well thought feature with your headphones on. You have to keep tabs on all your agents and get them unstuck when they fall in stupid deadlocks.
And why can’t we slow down? Because the company next door is shipping 10x with Claude Code or Codex.
In the end, you reach a state of fatigue and psychosis that pushes you toward just accepting whatever the AI agent says and throw more compute and LLM tokens at the problem when they get stuck.
Fantastic for the business model of companies that sell AI tokens. Bad for your mental health and your product’s reliability.
AI was supposed to make us work less
I've never been this tired in my life
most days I have up to 10 agents running at the same time. one fixing a bug, one writing pages, one refactoring something I already forgot I asked for, 3 other I have no idea what they are doing but i suppose i ask it?
and I jump from conversation to conversation all day
compared to 5 years ago, I probably context switch 100x more
by the end of the day my brain is fried. completely toasted. nothing left, not even for the people I love
I call it the fried brain effect
thought it was just me but almost every founder I talk to lately says the exact same thing
we got superpowers, and somehow the pressure only went up. if you can ship 10x more, you feel like you have to ship 10x more. every single day
I don't have a solution
honestly I have no idea where this goes from here
anyone else feeling this?
Enrique Soria retweeted
Python 3.15 adds frozendict as a built-in type! 🐍
It works like a dict, but it's immutable. Once you create it, you can't change it. That also makes it hashable, so you can use it as a dict key or put it in a set.
Great for config data you don't want changed by accident.
Will you use it?
Here's a quick example:
Enrique Soria retweeted
Mucho avance esta tendiendo a darle peor calidad al Software, la calidad no solo es el código, la calidad viene en cada proceso, y se está tendiendo a la no revisión, se está forzando el crear Software lo más rápido posible, dejando de lado el tener un sentido para hacerlo.
Enrique Soria retweeted
“the danger isn’t that ai writes bad code- it’s that it makes writing unnecessary code 100% free” — @HarivanshRathi
Enrique Soria retweeted
With AI, it’s tempting to create big tickets because AI can handle big tasks, and it generates code so quickly.
But the benefits of small, focused tickets remain relevant in the AI era.
- Get feedback quicker.
- Avoids context bloat / compacting.
- Less chance of spending a bunch of time going in the wrong direction.
- Leads to small PRs, which are easier to review.
- I’m more likely to understand a small ticket, and to notice gaps, inconsistencies, and logical issues in the requirements.
- Small tickets lead to smaller releases, which reduces risk.
Enrique Soria retweeted
Getting people to care about what you built remains arguably the hardest part of building software
Enrique Soria retweeted
"Some programmers have aesthetic preferences about code and they need to get over it because aesthetics don't matter."
Yes, sometimes they don't matter. But aesthetic judgements are also fast. If they're calibrated to match useful properties of code, that's useful.
Enrique Soria retweeted
stop making ai agents memorize your entire codebase.
people thought that throwing more markdowns file into the codebase and calling it SDD whatsoever will help. or installing some shitty memory plugins will.
trust me, I've been there...
every markdown you add is another potential source of stale truth.
want an agent-friendly codebase?
- shallow, feature-based modules
descriptive filenames
- comments explaining why, not what
- tests as executable specifications
- explicit, enforceable boundaries
- code search before vector search
your agent doesn’t need a better memory.
it needs a codebase that’s easier to understand, navigate, and verify.
sometimes the best context engineering is just good software engineering.
what a plot twist 😁
something that keeps bothering me is how some people see slop as something that is happening to them, like they're some kind of helpless bystander powerless to do anything about it
excuse me but you are a software engineer, you literally learned how to make sand think and make computers do your bidding?! and now you can't do anything about it? please
the 2 things you should know to cut through all the noise:
1. you need to give your agent a way to verify its own work (i just posted about this so won't rehash)
2. your codebase is memory
the 2nd is not new either, we have always had lint rules, compilers with good diagnostics and strong type systems, LSPs, etc to help us write better code. there is no difference when agents write the code instead, you just need more of them, and stronger ones.
forget rules and skills. you can add those later.
yes, your codebase is a form of memory to agents! agents love extending what already exists. so every nit and every annoyance you've ever seen, every mistake and bad pattern you observe from agents, needs to turn into a constraint, or the agents will just keep repeating those same mistakes like a virus in your code. then you keep observing and repeating this process until your codebase is locked down enough that even agents with little context can one shot a high quality PR.
an even better direction is to refactor/rewrite your code such that agent anti-patterns become categorically impossible. use type systems to your advantage, use libraries/frameworks that reduce the architectural search space, or heck, create your own framework like we did for grok bot and design high quality primitives and well thought out APIs
Enrique Soria retweeted
Esto no es algo nuevo, al negocio siempre le ha interesado tener nuevas funcionalidades, no si la arquitectura escala o si es clean code.
Lo único que logró la AI fue darnos la capacidad de subir código espagueti y acumular deuda técnica a velocidad x100
