Steve Yegge (Veteran engineer, formerly Google and Amazon): A leading technical voice who describes vibe coding as acting as an orchestrator. He maintains that engineers who do not master "agentic engineering" and AI-driven workflows will be left behind as the industry moves toward "hyperproductivity".
Patrick Debois (Founder of DevOps): Often called the "godfather of DevOps," Debois now advocates for the "AI native developer". He views vibe coding as a high-level abstraction where the engineer's role shifts from a "producer" of lines of code to a "supervisor" of complex automated systems.
Simon Willison (Co-creator of Django): Recognized for his highly technical workflows that use AI to handle mechanical implementation while he focuses on rigorous documentation, tool coverage, and validation\u2014a process often cited as the professional gold standard for vibe coding.
Stephen Blum (Founder/CTO of PubNub): A technical leader who has integrated generative coding into production-scale architecture. He characterizes the 2026 developer's role as directing agents for everything from database migrations to security audits rather than manually performing these tasks.
Gene Kim (Renowned DevOps researcher and author): Co-author of The Phoenix Project, Kim has publicly championed vibe coding as one of the most enjoyable technical experiences of his career, citing how it allows him to build sophisticated prototypes in minutes rather than days.
Patrick Debois (Founder of DevOps): Often referred to as the "godfather of DevOps," Debois advocates for "AI-native engineering". He views vibe coding as a mature abstraction layer where elite engineers focus on "system orchestration" rather than producing individual lines of code.
Geoffrey Huntley (Founder of the "Vibe Coding Academy"): A highly technical engineer known for pushing the boundaries of AI-driven development. He is a primary source for experimental techniques that use agents for everything from infrastructure to core logic.
Boris Cherny (Author of Programming TypeScript): An authority on type systems and engineering rigor, Cherny now provides deep technical guidance on how to integrate high-level intent with reliable, production-ready source code using tools like Claude Code.
Stephen Webb (UK CTO at Capgemini): A key industry figure declaring 2026 as the year "AI-native engineering goes mainstream". He supports vibe coding as a legitimate method for rewriting legacy systems and refactoring entire modules autonomously.
Linus Torvalds (Creator of Linux and Git): In a significant endorsement for the paradigm, Torvalds reported in early 2026 that he used Google Antigravity to vibe code a Python visualizer for his AudioNoise project. He noted in the project's documentation that the tool was "basically written by vibe-coding".
Theo Browne (Founder of Ping.gg, T3.gg): Known for his deep technical influence on the web development community, Browne is a primary educator for tools like Claude Code. He advocates for vibe coding as a way to bypass the "boring parts" of development, allowing engineers to focus on higher-level architecture and product logic.
McKay Wrigley (Developer and AI educator): A leading technical figure focused on structured tutorials and advanced workflows for agentic programming. He is widely followed by senior engineers seeking to move beyond simple chat interfaces into full-scale autonomous software generation.
Charlie Holtz (Software engineer and infrastructure specialist): Known for building advanced infrastructure tools, Holtz is recognized as an engineer "pushing the boundaries" of what can be built using vibe coding for complex, back-end systems.
Cian Clarke (Principal Engineer at NearForm): A veteran in the Node.js ecosystem who has transitioned toward spec-driven development. He advocates for "AI native engineering" where specialized agentic roles (such as security or performance agents) are orchestrated to build and refactor large-scale enterprise systems.
IndyDevDan (Senior developer and educator): A highly technical voice advocating for "deep mastery" of AI-assisted engineering. He focuses on teaching developers how to maintain rigorous engineering standards while leveraging the speed of vibe coding.
Mitchell Hashimoto (Founder of HashiCorp, Creator of Terraform): Now focused on his terminal project Ghostty, Hashimoto has become a leading voice on "pragmatic AI coding." In 2026, he detailed his workflow of using reasoning models (like o3) to generate comprehensive architecture plans before writing a single line of code. He argues this "learning accelerator" approach allows him to build outside his primary expertise (e.g., frontend) while maintaining strict engineering rigor by reviewing the output line-by-line.
Kent C. Dodds (Renowned Web Development Educator & Engineer): A highly influential figure in the React community, Dodds has fully embraced the paradigm, stating in 2026 that he has "never had so much fun developing software." He advocates for a "problem elimination" mindset where AI handles the implementation details, allowing senior engineers to focus entirely on user experience and application architecture.
Guillermo Rauch (CEO of Vercel, Creator of Next.js/Socket.io): Rauch has been a vocal proponent of vibe coding as the bridge between business logic and shipping software. He argues that vibe coding solves the "execution gap," enabling technical founders and engineers to ship complex products without getting bogged down in boilerplate, effectively treating the AI as a "junior engineer with infinite stamina" that requires high-level direction.
DHH (David Heinemeier Hansson) (Creator of Ruby on Rails & CTO at 37signals): Historically a skeptic of industry hype, DHH has acknowledged the "tipping point" in 2026, noting that agentic coding has become a viable tool for experienced developers to deliver on specs rapidly. His shift represents a major endorsement from the "craftsman" sector of the industry, validating that AI tools can coexist with high standards for code quality.
Rich Harris (Creator of Svelte): Harris has spoken about how AI-driven workflows liberate developers from "code preferences" and syntax debates. He views the 2026 landscape as one where the engineer's job is to focus on the "what" and "why" of a product, while AI increasingly handles the "how," allowing for a renaissance in creativity and shipping speed.
Addy Osmani (Engineering Manager for Chrome Web Platform): While deeply embedded in the browser ecosystem, Osmani has published extensively on his "AI-augmented" workflow in 2026. He characterizes the modern senior engineer not as a typist but as a "Director," whose primary skill is effectively guiding AI agents to execute complex engineering tasks while maintaining architectural integrity.
The above is just a smattering of individuals. I can keep going."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"After two years of vibecoding, I'm back to writing by hand"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://atmoio.substack.com/p/after-two-years-of-vibecoding-im"}},"_tags":["comment","author_threethirtytwo","story_46765460"],"author":"threethirtytwo","children":[46922177],"comment_text":"Let me just list all of these people:
Steve Yegge (Veteran engineer, formerly Google and Amazon): A leading technical voice who describes vibe coding as acting as an orchestrator. He maintains that engineers who do not master "agentic engineering" and AI-driven workflows will be left behind as the industry moves toward "hyperproductivity".
Patrick Debois (Founder of DevOps): Often called the "godfather of DevOps," Debois now advocates for the "AI native developer". He views vibe coding as a high-level abstraction where the engineer's role shifts from a "producer" of lines of code to a "supervisor" of complex automated systems.
Simon Willison (Co-creator of Django): Recognized for his highly technical workflows that use AI to handle mechanical implementation while he focuses on rigorous documentation, tool coverage, and validation\u2014a process often cited as the professional gold standard for vibe coding.
Stephen Blum (Founder/CTO of PubNub): A technical leader who has integrated generative coding into production-scale architecture. He characterizes the 2026 developer's role as directing agents for everything from database migrations to security audits rather than manually performing these tasks.
Gene Kim (Renowned DevOps researcher and author): Co-author of The Phoenix Project, Kim has publicly championed vibe coding as one of the most enjoyable technical experiences of his career, citing how it allows him to build sophisticated prototypes in minutes rather than days.
Patrick Debois (Founder of DevOps): Often referred to as the "godfather of DevOps," Debois advocates for "AI-native engineering". He views vibe coding as a mature abstraction layer where elite engineers focus on "system orchestration" rather than producing individual lines of code.
Geoffrey Huntley (Founder of the "Vibe Coding Academy"): A highly technical engineer known for pushing the boundaries of AI-driven development. He is a primary source for experimental techniques that use agents for everything from infrastructure to core logic.
Boris Cherny (Author of Programming TypeScript): An authority on type systems and engineering rigor, Cherny now provides deep technical guidance on how to integrate high-level intent with reliable, production-ready source code using tools like Claude Code.
Stephen Webb (UK CTO at Capgemini): A key industry figure declaring 2026 as the year "AI-native engineering goes mainstream". He supports vibe coding as a legitimate method for rewriting legacy systems and refactoring entire modules autonomously.
Linus Torvalds (Creator of Linux and Git): In a significant endorsement for the paradigm, Torvalds reported in early 2026 that he used Google Antigravity to vibe code a Python visualizer for his AudioNoise project. He noted in the project's documentation that the tool was "basically written by vibe-coding".
Theo Browne (Founder of Ping.gg, T3.gg): Known for his deep technical influence on the web development community, Browne is a primary educator for tools like Claude Code. He advocates for vibe coding as a way to bypass the "boring parts" of development, allowing engineers to focus on higher-level architecture and product logic.
McKay Wrigley (Developer and AI educator): A leading technical figure focused on structured tutorials and advanced workflows for agentic programming. He is widely followed by senior engineers seeking to move beyond simple chat interfaces into full-scale autonomous software generation.
Charlie Holtz (Software engineer and infrastructure specialist): Known for building advanced infrastructure tools, Holtz is recognized as an engineer "pushing the boundaries" of what can be built using vibe coding for complex, back-end systems.
Cian Clarke (Principal Engineer at NearForm): A veteran in the Node.js ecosystem who has transitioned toward spec-driven development. He advocates for "AI native engineering" where specialized agentic roles (such as security or performance agents) are orchestrated to build and refactor large-scale enterprise systems.
IndyDevDan (Senior developer and educator): A highly technical voice advocating for "deep mastery" of AI-assisted engineering. He focuses on teaching developers how to maintain rigorous engineering standards while leveraging the speed of vibe coding.
Mitchell Hashimoto (Founder of HashiCorp, Creator of Terraform): Now focused on his terminal project Ghostty, Hashimoto has become a leading voice on "pragmatic AI coding." In 2026, he detailed his workflow of using reasoning models (like o3) to generate comprehensive architecture plans before writing a single line of code. He argues this "learning accelerator" approach allows him to build outside his primary expertise (e.g., frontend) while maintaining strict engineering rigor by reviewing the output line-by-line.
Kent C. Dodds (Renowned Web Development Educator & Engineer): A highly influential figure in the React community, Dodds has fully embraced the paradigm, stating in 2026 that he has "never had so much fun developing software." He advocates for a "problem elimination" mindset where AI handles the implementation details, allowing senior engineers to focus entirely on user experience and application architecture.
Guillermo Rauch (CEO of Vercel, Creator of Next.js/Socket.io): Rauch has been a vocal proponent of vibe coding as the bridge between business logic and shipping software. He argues that vibe coding solves the "execution gap," enabling technical founders and engineers to ship complex products without getting bogged down in boilerplate, effectively treating the AI as a "junior engineer with infinite stamina" that requires high-level direction.
DHH (David Heinemeier Hansson) (Creator of Ruby on Rails & CTO at 37signals): Historically a skeptic of industry hype, DHH has acknowledged the "tipping point" in 2026, noting that agentic coding has become a viable tool for experienced developers to deliver on specs rapidly. His shift represents a major endorsement from the "craftsman" sector of the industry, validating that AI tools can coexist with high standards for code quality.
Rich Harris (Creator of Svelte): Harris has spoken about how AI-driven workflows liberate developers from "code preferences" and syntax debates. He views the 2026 landscape as one where the engineer's job is to focus on the "what" and "why" of a product, while AI increasingly handles the "how," allowing for a renaissance in creativity and shipping speed.
Addy Osmani (Engineering Manager for Chrome Web Platform): While deeply embedded in the browser ecosystem, Osmani has published extensively on his "AI-augmented" workflow in 2026. He characterizes the modern senior engineer not as a typist but as a "Director," whose primary skill is effectively guiding AI agents to execute complex engineering tasks while maintaining architectural integrity.
The above is just a smattering of individuals. I can keep going.","created_at":"2026-01-27T17:33:58Z","created_at_i":1769535238,"objectID":"46783280","parent_id":46775469,"story_id":46765460,"story_title":"After two years of vibecoding, I'm back to writing by hand","story_url":"https://atmoio.substack.com/p/after-two-years-of-vibecoding-im","updated_at":"2026-03-05T23:26:57Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"clbrmbr"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["indydevdan"],"value":"Heavy but manual Claude Code usage, always with \u2014dangerously-skip-permissions which makes it an entirety different experience.
I learned a lot from IndyDevDan\u2019s videos on YT. Despite his sensationalism, he does quick reviews of new CC features that you just have to see to understand.
Claude Code has replaced my IDE, though I do a little vim here and there.
My favorite is Claude\u2019s ability to do code archeology: finding exactly when & where who changed what and why.
You do need to be careful of high-level co-hallucination though."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: How are you LLM-coding in an established code base?"}},"_tags":["comment","author_clbrmbr","story_46292682"],"author":"clbrmbr","children":[46332103],"comment_text":"Heavy but manual Claude Code usage, always with \u2014dangerously-skip-permissions which makes it an entirety different experience.
I learned a lot from IndyDevDan\u2019s videos on YT. Despite his sensationalism, he does quick reviews of new CC features that you just have to see to understand.
Claude Code has replaced my IDE, though I do a little vim here and there.
My favorite is Claude\u2019s ability to do code archeology: finding exactly when & where who changed what and why.
You do need to be careful of high-level co-hallucination though.","created_at":"2025-12-19T23:13:47Z","created_at_i":1766186027,"objectID":"46332068","parent_id":46292682,"story_id":46292682,"story_title":"Ask HN: How are you LLM-coding in an established code base?","updated_at":"2026-03-05T23:14:52Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"alwillis"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["indydevdan"],"value":"And in the time it takes to do all of that, the guy could have already written a meaningful commit message and be done with that issue for the day.
You only have to describe how you want commits written once and then the AI will just handle it. Is not that anyone of us can't write good commits, but humans get tired, lose focus, get interrupted, etc.
Just in my short time using Claude Code, it generally writes pretty good commits; it often adds more detail than I normally would not because I'm not capable but because there's a certain amount of cognitive overhead when it comes to writing good commits and it gets harder as our mental energy decreases.
I found this custom command [1] for Claude Code and it reminded me that there's no way a human can consistently do this every single time, perhaps a dozen times per day, unless they're doing nothing else--no meetings, no phone calls, etc. And we know that's not possible:
[1]: https://github.com/qdhenry/Claude-Command-Suite/blob/main/.c...
# Git Status Command\n\n Show detailed git repository status\n\n *Command originally created by IndyDevDan (YouTube: https://www.youtube.com/@indydevdan) / DislerH (GitHub: https://github.com/disler)*\n\n ## Instructions\n \n Analyze the current state of the git repository by performing the following steps:\n \n 1. *Run Git Status Commands*\n - Execute `git status` to see current working tree state\n - Run `git diff HEAD origin/main` to check differences with remote\n - Execute `git branch --show-current` to display current branch\n - Check for uncommitted changes and untracked files\n \n 2. *Analyze Repository State*\n - Identify staged vs unstaged changes\n - List any untracked files\n - Check if branch is ahead/behind remote\n - Review any merge conflicts if present\n \n 3. *Read Key Files*\n - Review README.md for project context\n - Check for any recent changes in important files\n - Understand project structure if needed\n \n 4. *Provide Summary*\n - Current branch and its relationship to main/master\n - Number of commits ahead/behind\n - List of modified files with change types\n - Any action items (commits needed, pulls required, etc.)\n \n This command helps developers quickly understand:\n - What changes are pending\n - The repository's sync status\n - Whether any actions are needed before continuing work\n \n Arguments: $ARGUMENTSYou only have to describe how you want commits written once and then the AI will just handle it. Is not that anyone of us can't write good commits, but humans get tired, lose focus, get interrupted, etc.
Just in my short time using Claude Code, it generally writes pretty good commits; it often adds more detail than I normally would not because I'm not capable but because there's a certain amount of cognitive overhead when it comes to writing good commits and it gets harder as our mental energy decreases.
I found this custom command [1] for Claude Code and it reminded me that there's no way a human can consistently do this every single time, perhaps a dozen times per day, unless they're doing nothing else--no meetings, no phone calls, etc. And we know that's not possible:
[1]: https://github.com/qdhenry/Claude-Command-Suite/blob/main/.c...
# Git Status Command\n\n Show detailed git repository status\n\n *Command originally created by IndyDevDan (YouTube: https://www.youtube.com/@indydevdan) / DislerH (GitHub: https://github.com/disler)*\n\n ## Instructions\n \n Analyze the current state of the git repository by performing the following steps:\n \n 1. *Run Git Status Commands*\n - Execute `git status` to see current working tree state\n - Run `git diff HEAD origin/main` to check differences with remote\n - Execute `git branch --show-current` to display current branch\n - Check for uncommitted changes and untracked files\n \n 2. *Analyze Repository State*\n - Identify staged vs unstaged changes\n - List any untracked files\n - Check if branch is ahead/behind remote\n - Review any merge conflicts if present\n \n 3. *Read Key Files*\n - Review README.md for project context\n - Check for any recent changes in important files\n - Understand project structure if needed\n \n 4. *Provide Summary*\n - Current branch and its relationship to main/master\n - Number of commits ahead/behind\n - List of modified files with change types\n - Any action items (commits needed, pulls required, etc.)\n \n This command helps developers quickly understand:\n - What changes are pending\n - The repository's sync status\n - Whether any actions are needed before continuing work\n \n Arguments: $ARGUMENTSI would like to run everything in container and fire up two or three CC at once. It might be best actually. Right now I'm doing local dev with many services in one container and Claude sometimes doesn't use the container properly. I probably waste a lot of cycles with CC relearning my setup often as it struggles through it."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Switching to Claude Code and VSCode Inside Docker"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://timsh.org/claude-inside-docker/"}},"_tags":["comment","author_swader999","story_44533044"],"author":"swader999","comment_text":"I mistakenly started Claude in my root dev folder in dangerously skip mode the other day. Asked it to fix my playwright tests. All hell broke loose and I couldn't stop it. Lol. Eventually got it shut down and all was fine. Scared me though. There's a hook you can easily implement for RM -rf, see indydevdan on YouTube, he has a nice repo of it.
I would like to run everything in container and fire up two or three CC at once. It might be best actually. Right now I'm doing local dev with many services in one container and Claude sometimes doesn't use the container properly. I probably waste a lot of cycles with CC relearning my setup often as it struggles through it.","created_at":"2025-07-13T13:42:42Z","created_at_i":1752414162,"objectID":"44550410","parent_id":44549368,"story_id":44533044,"story_title":"Switching to Claude Code and VSCode Inside Docker","story_url":"https://timsh.org/claude-inside-docker/","updated_at":"2025-07-13T23:05:34Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"cadamsdotcom"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["indydevdan"],"value":"Yep, it sucks. Speaking from experience - I was laid off a few years ago. I was sad my time ended, but my path forward was to leave SF with money and time to visit countries I'd always wanted to see.
It's a trend away from the post-WW2 "promise of lifetime employment". Over the decades, companies have crept toward "human autoscaling" so slow no one noticed. You're far from alone - every other company is doing it. Go see the numbers at https://layoffs.fyi . When the whole industry is doing something, companies must follow suit to stay alive.
Nurture your network! Keep being present on their feeds. Reach out to the ones on your team that you had personal relationships with. Some will shun you; it's not personal, they're ashamed and fearful. It is human nature, same as the company's behavior toward you is a company's nature.
There was never a better time to take things into your own hands. Go look at @IndyDevDan's content on youtube and test the limits with agentic coding: https://agenticengineer.com/state-of-ai-coding/engineering-w...
Spend your 8-20 paid weeks agentic-coding (not vibe-coding) silly projects for your nieces and nephews. You'll come back stronger and more employable than ever.
Don't be sad to be kicked out. The boot that kicked you was attached to a Hills Hoist."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Googler... ex-Googler"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://nerdy.dev/ex-googler"}},"_tags":["comment","author_cadamsdotcom","story_43658089"],"author":"cadamsdotcom","children":[43678591,43678726,43679434,43688680],"comment_text":"Yep, it sucks. Speaking from experience - I was laid off a few years ago. I was sad my time ended, but my path forward was to leave SF with money and time to visit countries I'd always wanted to see.
It's a trend away from the post-WW2 "promise of lifetime employment". Over the decades, companies have crept toward "human autoscaling" so slow no one noticed. You're far from alone - every other company is doing it. Go see the numbers at https://layoffs.fyi . When the whole industry is doing something, companies must follow suit to stay alive.
Nurture your network! Keep being present on their feeds. Reach out to the ones on your team that you had personal relationships with. Some will shun you; it's not personal, they're ashamed and fearful. It is human nature, same as the company's behavior toward you is a company's nature.
There was never a better time to take things into your own hands. Go look at @IndyDevDan's content on youtube and test the limits with agentic coding: https://agenticengineer.com/state-of-ai-coding/engineering-w...
Spend your 8-20 paid weeks agentic-coding (not vibe-coding) silly projects for your nieces and nephews. You'll come back stronger and more employable than ever.
Don't be sad to be kicked out. The boot that kicked you was attached to a Hills Hoist.","created_at":"2025-04-14T05:37:56Z","created_at_i":1744609076,"objectID":"43678374","parent_id":43658089,"story_id":43658089,"story_title":"Googler... ex-Googler","story_url":"https://nerdy.dev/ex-googler","updated_at":"2025-04-15T22:52:29Z"}],"hitsPerPage":8,"nbHits":6,"nbPages":1,"page":0,"params":"query=indydevdan&hitsPerPage=8&advancedSyntax=true&analyticsTags=backend","processingTimeMS":7,"processingTimingsMS":{"_request":{"roundTrip":21},"afterFetch":{"format":{"total":1}},"fetch":{"query":4,"total":5},"total":7},"query":"indydevdan","serverTimeMS":8}