Ronny López

Biggest mistake in AI coding era: to believe that specifications should be either natural language OR something else. The best combo is a natural language high level specification (the intend), plus code (as it gets written) documenting the finer behaviors.

Something that I think goes under-emphasized is how much AI coding demands a 'lead dev' mentality. If you spent your pre-AI career trying to level up your teammates (through API design, feedback loops, architecture) Then working with AI will feel natural. If you only focused on your own output, it will feel super bad.

@ThePrimeagen creating a thing isn’t hard. maintaining is.

I don’t think AI is lowering the barrier to entry as much as it is giving the very smartest people an even more enormous advantage.

It’s going to be a wild year, don’t completely forget about the humans in your life

@adamdotdev This “adult in the room” framing is pretty rude to the Claude Code team that built a product hitting $1B run-rate revenue faster than probably anything in history. Bun made like $2.50 total (stickers). Engineering is relative to time & tradeoffs & they made fantastic tradeoffs

We’ve got the lamp… now we just need to not mess up the three wishes.

@simonw So… who won in the end: tabs or spaces?

Adding Deno and Node.js creator Ryan Dahl to the growing chorus Software developers add WAY more value than memorizing the syntax trivia of the languages they use It's time to lean into that everything-else and cede putting semicolons in the right places to the robots

@gimenete Move fast, break prod, blame the model 😎

Don’t worry too much if your coding agent generates technical debt today. The next version of the model will fix it 😀

@davidalvarezdlt @JosuGoi1 Montar un SaaS como el tuyo "totalmente solo", a día de hoy es imposible, al menos yo no lo he visto. En un año no sé, pero hoy me temo que no.

@JosuGoi1 Estoy de acuerdo, pero el juego va a cambiar por completo… ni idea como, pero que se puedan montar hoy SaaS como el mío totalmente solo o con pocas personas hace que las dinámicas cambien totalmente.

Cómo diferenciar al founder que usa la IA del que no: - El que no la usa: opina que el mundo de software va a cambiar (porque lo ha leído en las noticias) pero añade la coletilla “pero no tanto”. - El que sí lo usa: pregunta por rentabilidades de negocios físicos.

When I wrote that Go was the only mainstream language that got concurrency right, many people reminded me of Erlang. But no one said anything about Clojure (maybe because it's not mainstream). Meanwhile, Clojure's core.async is an excellent implementation of the Communicating Sequential Processes (CSP) approach as a library, not in the language runtime. (Don't be confused by the unfortunate "async" naming, it's NOT about async/await) It's quite similar to Go (no surprise, Go also implements the CSP approach). But it's even more powerful! (Only in terms of the API, though; the scheduler implementation in Go is much more sophisticated, and it uses a preemptive approach, unlike cooperative core.async) If you are programming in a language with async/await concurrency - I encourage you to read the core.async documentation. I'm not a fan of Clojure, but this library is a real gem.

I've been working alone for the last months so several people told me I'm an "Indie Hacker". But I do not identify with that movement. I do think there is a need for people solving problems in the long tail, but it does not need to be a hustling game.

@masylum Love it

@garrytan We are building this at anything.so Email, calendar and phone in autopilot for busy professionals. And you don’t need to fire your assistant. We put him/her on the loop. DM to join beta.

@smoyac Call someone ...

@ronnylt Sorprendeme 😂

Three weeks working at @TimescaleDB and wow! Already having so much fun; gearing up amazing stuff since day one. The engagement level is out of orbit.

A few months ago, we changed the way we address bugs @linear. We prioritized bugs over everything else. If you have bugs assigned when you wake up in the morning, you don't do anything else before they are addressed. This approach felt scary and quite radical, but our theory was this: Every software product has defects and the amount of defects being found is somewhat constant. We want to build a product that is of the highest quality, so eventually all bugs will be addressed. This means that the amount of work required to tackle bugs is the same regardless of whether you address the immediately or whether you prioritize feature work and tackle bugs in bulk between feature work. And this made it obvious that the better alternative is to prioritize bugs over everything else. The cost for doing this was that we had to spend a month or so to bring down the backlog of bugs, but once the backlog was eradicated, there was no additional cost to this approach. Now, if we or a customer finds a bugs, it usually gets fixed the very next day. You certainly should consider doing this at your software company.

@elwatto Podía haberte dicho: "si eres de Sacramento, te pentesteo hasta adentro..."

best pickup line I’ve seen in a while

@smoyac I know there's a word for that, but I can't remember it right now.

What do you call it when you don't recall what you already know?

@david_bonilla En Equilateral hacemos un poco de todo: equilateral.cloud

Quiero hacer una lista de «boutiques de desarrollo». Compañías de servicios informáticos que ataquen proyectos pequeños, de menos de 50.000€. ES PARA UN AMIGO...