Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Why does "vibe coding" not lead to anything productive, for the most part? A great person to answer is Addy Osmani: he has been working on Chrome for 10+ years, and has just published his new book: Beyond Vibe Coding. Watch or listen: • YouTube: • Spotify: • Apple:...

51,839 Aufrufe • vor 9 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

. Kent Beck 🌻 is a legend in software engineering: and after coding for 52 years, he's never had more fun than now, he told me. Why? Because AI agents brought back the joy of creating software without the stuff that he's started to hate about coding for so long. Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: • Sonar — Code quality and code security for ALL code •⁠ Statsig ⁠ — ⁠ The unified platform for flags, analytics, experiments, and more • Augment Code — AI coding assistant that pro engineering teams love Two of my takeaways from this chat with Kent: 𝟭. 𝗞𝗲𝗻𝘁 𝗶𝘀 𝗿𝗲-𝗲𝗻𝗲𝗿𝗴𝗶𝘇𝗲𝗱 𝘁𝗵𝗮𝗻𝗸𝘀 𝘁𝗼 𝘂𝘀𝗶𝗻𝗴 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝘀𝘁𝘂𝗳𝗳. Kent has been coding for 52 years, and the last decade, he’s gotten a lot more tired of all of it: learning yet another new language or framework, or debugging the issues when using the latest framework. What he loves about these AI agents (and AI coding tools) is how he doesn’t need to know exactly all the details: he can now be a lot more ambitious in his projects. Currently, Kent is building a server in Smalltalk (that he’s been wanting to do for many years) and a Language Server Protocol (LSP) for Smalltalk 𝟮. 𝗙𝗮𝗰𝗲𝗯𝗼𝗼𝗸 𝘄𝗿𝗼𝘁𝗲 𝗻𝗼 𝘂𝗻𝗶𝘁 𝘁𝗲𝘀𝘁𝘀 𝗶𝗻 𝟮𝟬𝟭𝟭, 𝗮𝗻𝗱 𝘁𝗵𝗶𝘀 𝘀𝘁𝘂𝗻𝗻𝗲𝗱 𝗞𝗲𝗻𝘁, 𝗯𝗮𝗰𝗸 𝗶𝗻 𝘁𝗵𝗲 𝗱𝗮𝘆. Kent joined Facebook in 2011, and was taken aback by the lack of testing and how everyone pushed code to production without automated testing. What he came to realize – and appreciate! – was how Facebook had several things balancing this out: • Devs took responsibility for their code very seriously • Nothing at Facebook was “someone else’s problem:” devs would fix bugs when they saw them, regardless of whose commit caused it • Feature flags were heavily used for risky code • Facebook did staged rollouts to smaller markets like New Zealand To this date, Facebook ships code to production in a unique way. We covered more in the deepdive Shipping to Production at

Gergely Orosz

42,529 Aufrufe • vor 1 Jahr