Developer Advocate at @Howdy. FullStack #JavaScript developer. Pragmatic software engineering #research is my thing.
Montevideo
Joined January 2010
- Tweets1.7K
- Following362
- Followers227
- Likes523
Darío Macchi retweeted
“Maintenance is not a discrete activity, but a routine part of the entire development process.” — The Pragmatic Programmer
Darío Macchi retweeted
Practical? No.
Extravagant? Utterly!
Beautiful? Absolutely!
Will I buy one? No chance.
Did I cheer? Enthusiastically!
Darío Macchi retweeted
AI makes your work harder, not easier. I think of it as work density—the percent of time spent expending brain cells. The denser the work, the more exhausting it is. If you have 10 agents running at once, you have 10x the context swaps, each of which requires recovery time. The more density, the higher the recovery time. When you don't take time to recover, you burn out. Working with multiple agents is worse than normal multitasking because you're juggling more tasks.
There's nothing new about this. I can't think of a single "time-saving" workplace technology that saved anybody any time. Instead, it forces us to work harder. It increases density. The problem is compounded by moronic management that fires people because of the tech. In practice, firing 50% of your staff means that the remaining 50% have to do twice the work in the same time. It's exhausting. The utopian notion that AI will create leisure time is complete BS. It will just force us to cram more work into the time we have.
We need to just stop frantically pushing, pushing, pushing for more and more output and relax. It takes a conscious effort to counter that effect, so make the effort. You will not be "more productive" once you burn out.
ALT Post from Twitter: https://t.ly/ozBrG
Darío Macchi retweeted
This is Pele, my new rendering library for diagrams and charts, compatible with the latest Mermaid syntax.
- 100-500× faster than mermaid.js
- 6× smaller bundle
- No dependencies
- Easy to theme
- Responsive to device width
In pursuit of making Obsidian insanely fast and cohesively designed, I always found the Mermaid library to be too big, too slow, and too hard to theme. Pele will be the new renderer in the next version of Obsidian, but you can start using it now.
Pele [ˈpɛlɛ] is named after the goddess of volcanoes and fire. It's open source under the MIT license. Try the playground!
Darío Macchi retweeted
In my career, compilers have always generated better code that I ever could have. I find this to be increasingly so with contemporary AIs.
But you know what neither can do better than me?
Knowing what software to write, what shape it should take, and what I want it to do.
The entire history of software engineering has been one of rising levels of abstraction.
This is how it was, how it is now, and how it shall be in the fullness of time.
Darío Macchi retweeted
I usually have 5-10 coding agents running at once, and I kept losing track of what each one was doing, where it was in the repo, and how the work connected.
So I made an infinite map for Claude Code, Codex, and Cursor.
The canvas is endless. Add as many agents as you want, watch them work in parallel, and see the relationships and data flowing between them.
Completely open source. Repo in the replies.
Darío Macchi retweeted
I actually think (and am anecdotally seeing) that AI is making work a lot harder.
AI coding agents removed a lot of the friction of writing software. But now everyone is expected to do more.
So if you’re not spinning up 10 coding agents to do 10x more work for you, you will be left behind.
And compared to classic software engineering, managing AI coding agents is much more exhausting. You are constantly working in System 2 mode, trying to figure out and formulate the high level goals and verify and validate the progress of the agents.
To say nothing of the constant worry in the back of your mind that you don’t know what the agent is exactly doing and things might go wrong at any moment.
That is in stark contrast to the relaxing and semiautomatic process of implementing a well thought out solution with your own hands. Our brains had time to relax back then.
before ai it was cognitively expensive to be a programmer cuz you had to really use brain cycles for everything, from architecting, to even using the right variable names etc. it was genuinely draining.
& if you programmed for a whole day, you were fucking tired. even code reviews required you to think deeply & you had to be aware of the entire code base to some extent too. so not only did you have to have context loaded, you had to do manual inference if you will.
ai completely eliminated all of this strain.
Darío Macchi retweeted
Elixir v1.20 released! Now officially a gradually typed language: Elixir type checks every single line of code, finding bugs and dead code, without developer overhead (no typing signatures) and extremely low false positives rate. Plus a faster compiler! Links and reports below.
Caso interesante de #phishing... me llegó este email (ya sospechoso por el mail de origen). Luego de destriparlo, llegué a un server en Estambul y aprendí un hermoso uso para webhooks de Discord!
Darío Macchi retweeted
I’ve come to the conclusion that those who are pushing agentic systems have at least three glaring holes in their approaches:
Most are entirely ignorant of the existing literature in this space, both from early AI to biological studies of swarms to complex systems theory. This is not a new landscape.
Orchestration among agents is either treated as an afterthought or via extremely naive centralized architectures. This BTW is why I am a fan of blackboard architectures as pioneered in Hearsay years ago and in @BernardJBaars global workspace theory.
There exist many flavors of agents and yet most today are a little more than trivial input/output mappings.
This is fertile ground, but most are planting seeds opportunistically in fallow ground, without consideration for where they may fall or how they may be nourished.
Darío Macchi retweeted
Así se vivió nuestro meetup de tecnología Q1 2026 🔥
Gracias a todos los que reservaron el tiempo para estar, aprender, compartir y hacer esto posible 🙌
Vamos por más, nos vemos en el siguiente 🚀
#BoyacáDev
.
Indeed...
Nobody in history has gotten better at software development by having more meetings. Calling those meetings "events" doesn't change that. Time spent in meetings is time spent not working. Looking at Scrum, I can't see anything done in a single one of those meetings that couldn't be done better without the meeting.
Let's look at a few:
Daily Scrum: Unnecessary if you're working collaboratively in an ensemble or even talking to each other throughout the day. This is a meeting for the benefit of people who work in isolation so they can coordinate once a day. Stop working in isolation.
Retros: Teams working in an ensemble don't need them. It assumes scatter/gather. That doesn't mean an occasional chapter/guild meeting isn't a bad way to coordinate with other teams, but the by-rote bi-weekling thing most Scrum Teams do is not that. When something goes wrong, pull the Andon Cord.
Sprint Reviews. Dog and pony shoes are worthless. Release often--daily if you can. People who are interested in the state of the software can just look at it.
Sprint planning--Have regular chats with customers all the time. If you haven't gleaned enough info to start from those chats, maybe you should work on that. Get active feedback as you work and collect additional info as you do that. Dump the damn tickets and the story points. They're actively destructive.
Luego de un almuerzo de discusión intentando interpretar los puntajes de los clavados sincronizados, encontré como se calcula con ejemplos.
De nada. usadiving.org/about-us/divin…
Darío Macchi retweeted
Todo preparado para celebrar el #DiaInternacionalDeLaCerveza gracias a @cervezasya 😎💅🏻🍺
Maybe you all already know this site... but if there is someone out there who doesn't know it (like me) and wants to do some kind of job retraining or just improve their skills, I recommend it.
Here is an example of how to become an AI & Data Scientist.
buff.ly/49SxVkZ