Software developer ... sometimes I'm like The Wolf, I solve problems (and I bake cookies) 🙂

Madrid, Spain
Joined March 2010
Rework on an old sketchnote about backpressure :-)
5
27
1
148
Yeray Darias retweeted
¿Buscas otra forma de trabajar en tecnología? 🤖 @540deg, patrocinador de la #TR26, busca talento: personas con criterio, ganas de hacer las cosas con intención y de trabajar cerca de los problemas, no solo de los tickets. Más info aquí: lnkd.in/p/eYMPSHU3
7
5
847
Yeray Darias retweeted
Agents write code "much better on average at scale" is right. The "at scale" part comes from verification. Agents make checking cheap. The stuff that made "Good Code" expensive (tests, benchmarks, specs, real e2e runs) is now a cheap thing you can ask an agent for. You can improve the checks. So our work is less "review every line" and more "build loops the agent can run itself". Give the agent a way to verify the work. That loop is where quality comes from. And make taste compound. When the agent gets something wrong, write it down (shared config, a hook, a test) so it doesn't happen twice. A human still owns what ships but now they're reviewing evidence and not just diffs.
codebases have always contained slop. we have always been okay with this because code rarely needs to be perfect, outside of mission critical "hard" (eg embedded) software. swe is a unique form of engineering because you're often building something that constantly evolves and is almost organic - user tastes change, your mental models evolve, and features come and go. admittedly, i and many others who've been coding for a long time were initially (like back in 2024) skeptical that agents would write production code. "but what about all the slop that would enter our beautiful codebase?". well, even before, we had human slop, and there was a lot of it! if we're being truthful, most people call "code i didn't write" slop. the reality is that 99% of people (i include myself in that number) don't even know what Good Code looks like, let alone be capable of writing it. i would propose that Good Code is: • correct • bug free • fast and cost efficient to run it has always been exceedingly difficult and expensive to write truly Good Code, because for the longest time (maybe @bendlang will change that), code was not something you could cheaply and formally guarantee to have all 3 of these properties. this is why writing hard software is much more difficult and expensive, because depending on the use case, you may only get one chance and so you have to be right from the start. but the vast majority of software we use does not need to be Good Code to provide value to users. in fact, it is very likely that most software we use is not formally verifiable! we accepted some bugs in exchange for velocity and progress, so we rely on tests and o11y instead and have adopted a more incremental approach. this is a good thing! agents help us move faster, and if you're open to the idea, are capable of helping us write better code. it won't be Good Code (that is still expensive), but it is likely to be much better on average at scale. the new craft of swe is to figure out how to do this. it's your job now! if your productivity with and without agents is not significantly different, you're doing something wrong. but it's not too late to embrace it and use it as an opportunity to learn a whole new skill tree
91
55
17
654
53,210
Yeray Darias retweeted
Cada vez veo más necesario tener un equipo 100% dedicado a la IA dentro de las empresas morvader.substack.com/p/por-…
2
4
1
4
742
(comic) Presentation Hell
6
98
9
978
17,614
"... porque “lo ha hecho la IA” no parece una gran explicación cuando algo se va a la mierda"
“Nuestra profesión nunca fue escribir líneas de código a mano. Era un puto medio”. La vuelta y media en la newsletter de @540deg newsletter.540deg.com/p/limi…
2
3
4
999
Yeray Darias retweeted
Some more thoughts about this. Planning a section of my course felt really fucking hard with an agent helping me. It kept distracting me with irrelevant questions. It jumped to conclusions too early. It created complex assets too fast, and drowned my thoughts with commentary. I felt out-of-control. With pen and paper, I felt totally in control. I made progress slowly but steadily. The slow pace of the medium meant I could make decisions at human speed. AI seems to be a bad fit (for me) in situations where I need oversight over the entire output at once. Where changes in one place (an early lesson) ripple through the entire output. I.e. for some things, the tortoise beats the hare
Have been trying for weeks to make AI better at course planning Tried a new method today. Notecards, pen, paper, scissors. Turns out not using AI is pretty good guys
97
40
13
879
96,488
Yeray Darias retweeted
"Don't paste the AI, please" "The world is full of people who don't want to read or think things through. Don't be one of them." dontpastetheai.com
51
153
16
1,162
78,183
The Right but Early Club (RBEC), they are people (who sees things/problems sooner) as necessary in your organization as the Right now people! cutlefish.substack.com/p/tbm…
2
1
234
Yeray Darias retweeted
Mastery still comes from doing the reps. Before agents, I got my reps as part of writing code: try different approaches out, debug what went wrong, review other’s code, read a lot. Agents can skip much of that work, so building your reps has to be deliberate. If I was new to the industry, I'd try to form a hypothesis before prompting. Ask "why" a lot, read the diffs, try to predict what might fail. Occasionally try to work through the problem myself manually. In my experience, good agent work depends on two abilities: 1. Deep expertise: you understand the problem domain well enough to define a good outcome. Understanding your user/product/business is part of this. 2. Applied judgment: use your taste to turn this into a clear, testable plan by choosing the right context, constraints, tests and verification. To build these the skills I'd practice are decision making, specifying, steering and verifying.
21
17
1
179
21,465
Yeray Darias retweeted
Han creado un motor local que convierte un repositorio en un grafo de conocimiento y lo ofrece a Codex, Cursor o Claude Code mediante MCP. Muy útil para analizar dependencias y flujos antes de pedir a un agente que modifique un repo grande. GitNexus → github.com/abhigyanpatwari/G…
25
90
1
783
41,438
Yeray Darias retweeted
Something agents have a massive problem with is failing fast They're cowards, they never want to be responsible for a crash I've lost count of how many times I've said "if the environment variable isn't present, throw"
136
22
6
1,069
81,348
Acabo de encontrar un sonotone en la playa de El Portil, Huelva. Mi madre usa y sé que perderlos es doble tragedia porque además son muy caros. Así que TUITER haz tu magia
44
5,570
22
6,889
313,679
Yeray Darias retweeted
💫¿Qué pasa cuando una función se llena de if dentro de otros if? 🤔 El "Early Return" ayuda a reducir la indentación y la carga cognitiva, haciendo que la lógica principal sea más fácil de entender. Nos lo explica @SeymourPoler en este artículo😉👇 leanmind.es/es/blog/principi…
6
6
230
Yeray Darias retweeted
We just published our internal 37signals Manager Playbook. basecamp.com/managers Inside we share what’s expected of managers, team leadership philosophies of 37signals, our "Hell Yeah" standard, how to navigate difficult conversations, and how to balance management duties with core individual contributor work. Plus a whole lot more. There are no "just managers" at 37signals, so the individual contributor bit is key. Questions? Comments? Post 'em here and I'll do my best to make sense.
49
119
19
1,620
184,793
Yeray Darias retweeted
AI;DR (AI; didn’t read)
96
2,453
89
18,156
438,314
GitOps in a nutshell (ArgoCD edition)
2
2
270