À PROPOS DE CET ÉPISODE
Here is the claim.
For an experienced programmer, reading AI-generated code is not diligence, it is a bottleneck. Complex code takes longer to read properly than to write from scratch, so the review you think you are doing is not happening.
Luca and Matteo pick that up and pull on it until something gives.
Where does it hold? Where does it fall apart? If it is true, what happens to review, to ownership, to the junior who is still learning the craft? No conclusions promised.
Just two engineers working through a question the whole industry is currently avoiding.
Anglais
États-Unis
TRANSCRIPTION 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
RECHERCHER LES ÉPISODES PASSÉS
Rechercher les épisodes précédents de The Node (and more) Banter.
AUTRES ÉPISODES DANS CE PODCAST
Nitro gives you a clean, portable server. Whether you use it on its own or with Vite, you get consistent builds, familiar routing, and a smooth development workflow. But Nitro doesn’t explain what to do when you have several instances and a cron job, or when you need a gateway, metrics, and worker …
Every Node.js developer learns the same rule on day one: never block the event loop. Async is good, sync is bad, and the libuv thread pool is your friend. Then a real customer brought Luca and Matteo a compression problem that turned all of that upside down. Turns out, the rule is only half the sto…
Eve is a well-designed open-source agent framework. It offers a clean programming model, filesystem-based instructions and tools, and durable sessions built on the Workflow SDK. However, running Eve in a real enterprise Kubernetes environment needs extra infrastructure that isn't included by defaul…
People keep saying that AI helps developers get more done. But few are asking who pays for the computing power, tokens, and time needed to keep the open-source projects behind AI running. Node.js maintainers often use their own servers, patch together free subscriptions, and struggle to get access …
You spot a critical bug in production, fix it, deploy, and feel relieved. But then you notice the workflows that need the fix most, like 30-day subscription cycles, compliance timers paused for months, or approvals waiting on a signature, are still stuck on the old version. They never get the fix. …
Avertissement: Le podcast et les illustrations intégrés sur cette page proviennent de Platformatic, qui est la propriété de son propriétaire et n'est ni affilié ni approuvé par Listen Notes, Inc.
MODIFIER
Merci de nous avoir aidé à tenir la base de données de podcasts à jour.
