| Episode Type | Expert Insight Interview |
| Guest | Menil Vukovic, CEO, Pear Shadow |
| Guest Website | pearshadow.com |
| Listen | View on Sales POP! Podcast Page |
AI has reopened settled questions in software engineering — what quality means, how fast teams should ship, and where humans belong in the build process.
Menil Vukovic, CEO of Pear Shadow, brings two decades of engineering leadership to this shift. He explains how his team moved from chaotic experimentation to structured AI orchestration, and why experienced engineers now hold an unexpected advantage.
Key Insights
1. Here is what you need to know about orchestrating AI instead of writing every line yourself.
Each engineer now manages AI agents the way a lead manages a team. Menil compares the shift to giving every developer a Ferrari — fast, but dangerous in untrained hands. Orchestration demands new skills: context-rich prompting, output review, and real-time course correction. AI still repeats the same mistakes even with guardrails in place. Engineers who embrace the supervisory role operate at a scale they could never reach on their own.
2. Here is what you need to know about why experienced engineers gain an advantage.
Experience translates into better AI output. Menil points to Google Translate, invented 22 years ago, which still has not replaced human translators. AI amplifies existing knowledge rather than replacing it. Engineers with deep context write sharper prompts, spot weak code faster, and catch errors others miss. Many senior leaders who stopped writing code have returned to the keyboard, shipping ideas in evenings that used to take quarters.
3. Here is what you need to know about the three stages of AI adoption.
Menil’s team moved through three stages. The YOLO stage gave engineers free rein — one AI produced brilliant code, another produced garbage, with no pattern to either. The team then borrowed from Agile and Waterfall to wrap a process around the use of AI. The third stage reframes every engineer as a lead engineer managing their own AI workforce. Teams that skip these steps produce more code, but the quality drops fast.
4. Here is what you need to know about why documentation matters more than ever.
Writing code now accounts for roughly 20% of an engineer’s job. The rest lives in documentation, review, and team coordination. Menil calls this the most important year for README files in the history of the industry. Accurate documentation grounds the AI, prevents drift between sessions, and lets the next person — human or agent — pick up the work. Teams that neglected documentation in the past pay the bill now.
5. Here is what you need to know about balancing vibe coding with proven fundamentals.
Vibe coding has its place — fast experiments, non-engineers solving their own problems, weekend MVPs that prove or kill ideas. But the middle ground wins in the long term. Git practices remain essential: commit a working version, push to the remote, and revert cleanly when the AI breaks something. Some industries — embedded systems, avionics, military — will resist AI adoption far longer than mainstream development. The fundamentals still apply everywhere.
Pull Quotes
“I have not written so much code in my career as much as I had in the last two years, because my ideas can now go from ideas to execution much faster than they ever could.” — Menil Vukovic
“Everyone’s driving a Ferrari these days when it comes to coding. But that’s very dangerous. Not everyone should be driving that fast.” — Menil Vukovic
“Each individual engineer is now orchestrating their AIs. They’re not engineers in the same sense, but much more like lead engineers, engineering managers of their own AIs.” — Menil Vukovic
“Having a README that is correct based on the code base has never been more important.” — Menil Vukovic
Software Engineering in the AI Era: Key Statistics from Pear Shadow
| Statistic | Detail |
| 22 years | Time since Google Translate launched — yet human translators are still in demand. |
| 2021 / GPT-2 | AI began handling Chinese-to-Japanese translation, one of the hardest language pairs. |
| ~20% | Share of a modern software engineer’s job spent actually writing code. |
| 2 years | Time in which Menil has written more code than in the rest of his career combined. |
| 5 years | Menil’s tenure as CEO of Pear Shadow, building products for startups and enterprises. |
| 50 years | Of software engineering fundamentals that still apply in the AI era. |
Related Resources
- Book a free consultation with Pear Shadow: https://www.pearshadow.com/
- Sales POP! Podcast: Sales POP! Podcast
Our Host
John is the Amazon bestselling author of Winning the Battle for Sales: Lessons on Closing Every Deal from the World’s Greatest Military Victories and Social Upheaval: How to Win at Social Selling. A globally acknowledged Sales & Marketing thought leader, speaker, and strategist, he has conducted over 1500 video interviews of thought leaders for Sales POP! online sales magazine & YouTube Channel and for audio podcast channels where Sales POP! is rated in the top 2% of most popular shows out of 3,320,580 podcasts globally, ranked by Listen Score. He is CSMO at Coevera. In his spare time, John is an avid Martial Artist.




Comments