LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
Select Accept to consent or Reject to decline non-essential cookies for this use. You can update your choices at any time in your settings.
Loved watching Andrej Karpathy talk at AI Startup School. Must watch for everyone in Product and Engg to understand software in the AI era
1. Software is undergoing a fundamental shift, moving beyond traditional code.
2. LLMs share characteristics with utilities, fabs, and especially operating systems.
3. LLMs possess "human-like psychology" with both superpowers and cognitive deficits.
4. The future of software is in "partial autonomy apps" and human-AI cooperation.
5. This is the decade of AI Agents. Time to build :)
https://lnkd.in/gHQ7Ad9a
🚀 Software Is Changing Again
🎙️ By Andrej Karpathy, AI Visionary and Former Director of AI at Tesla
Andrej Karpathy, one of the most respected voices in artificial intelligence, shares a powerful message about how software development is entering a new era.
He describes three major phases that define the evolution of software:
1️⃣ Software 1.0: Humans wrote precise rules and logic by hand.
2️⃣ Software 2.0: Machines began learning these rules from large amounts of data.
3️⃣ Software 3.0: Developers now express their intent in natural language, and large language models transform those ideas into functioning systems.
This transformation, which Karpathy calls vibe coding, represents a complete shift in how we build technology. Instead of focusing on syntax, structure, and repetition, engineers can focus on creativity, problem solving, and system design.
Software creation becomes more of a conversation between human imagination and machine intelligence.
Karpathy believes that in the future, software will not only serve people but also communicate directly with other intelligent systems. This means engineers will need to master new skills such as prompt design, orchestration, and validation.
They will need to manage how intelligent components interact and collaborate in complex environments.
He also introduces the idea of jagged intelligence, which means AI can be brilliant in some areas but unreliable in others. The most successful engineers will be those who know how to design systems that take advantage of AI’s strengths while carefully managing its weaknesses.
🌍 Why it matters
Software is becoming adaptive, intelligent, and self-improving. For decades, engineers wrote programs that followed strict rules. Now we are entering an age where software learns, reasons, and evolves.
This moment marks a change from the age of programming to the age of teaching machines how to think.
The next generation of engineers will not simply code. They will design intelligence itself.
The challenge is no longer to compete with AI but to understand it, guide it, and work with it to build something truly transformative.
✨ My reflection
Andrej Karpathy’s vision is both inspiring and deeply practical.
He reminds us that our role as engineers and innovators is evolving.
We are moving from commanding computers to collaborating with intelligence.
Our true value will come from imagination, critical thinking, and the ability to translate ideas into intelligent systems that can learn, adapt, and improve.
We are not just building software anymore.
We are shaping the future of intelligence.
🔥 Absolutely HOT topic by Andrej Karpathy and it hits right where most tech execs still look away.
Most companies are layering AI over legacy spaghetti, not modernizing just masking entropy with a shiny prompt interface.
After nearly 70 years of evolution, traditional software engineering is becoming as rare and as essential as real AI literacy.
Because if you don’t understand how your systems were built, you won’t survive 😁re-architecting them.
😏 AI doesn’t replace systems, it exposes them.
The future isn’t plug-and-play. It’s migrate-and-pray (if you skipped your foundations 😋).
🎯 For every CTO, CIO, and “AI strategist”: watch this on your lunch walk it might just save your next roadmap.
#AI#LLM#Software3point0#DigitalTransformation#TechLeadership#EnterpriseArchitecture#AndrejKarpathy#CIO#CTO
Recently came across this fantastic video “Software in the Era of AI” by Andrej Karpathy the former Senior Director of AI at Tesla and also the guy who coined the term ‘vibe coding’!
It’s a very insightful explanation about how software itself is evolving, from Software 1.0 > 2.0 > 3.0, and how natural language is quickly becoming the new programming interface.
Andrej does a great job in breaking down some complex ideas and covers areas like:
🟢 LLMs as utilities and operating systems
🟢 Psychology of LLMs: People spirits and cognitive quirks
🟢 Designing LLM apps with partial autonomy
🟢 Lessons from Tesla Autopilot & autonomy sliders
🟢 The Iron Man analogy: Augmentation vs. agents
🟢 Vibe Coding: Everyone is now a programmer
And more…
As Andrej puts it we are in the 1960s of LLMs and the early days of a new computing paradigm.
https://lnkd.in/dTPBY-Qm
The biggest mistake developers are making right now?
They think AI is just another tool.
It’s not. It’s a new substrate for building software.
History shows the pattern:
• 1990s → Code lived on desktops
• 2000s → Code lived on the web
• 2010s → Code lived on mobile
• 2020s → Code lives inside AI
And that changes the rules of the game.
We’re moving from:
• Writing instructions → to teaching intelligence
• Debugging functions → to shaping behaviors
• Shipping commits → to orchestrating agents
As Andrej Karpathy said:
“Programs are no longer written. They’re grown.”
What does this mean in practice?
⚡ Systems that learn instead of being patched
⚡ Products that understand goals, not just clicks
⚡ Developers who multiply output by orders of magnitude
The uncomfortable truth?
Your coding skills have a half-life.
The faster you adapt, the longer you stay relevant.
The future belongs to those who stop fighting AI; and start collaborating with it.
The 2025 DORA report is out! The report - The State of AI-assisted Software Development shows AI’s primary role and how this affects organizations.
Check it out here.
The 2025 DORA report is out! The report - The State of AI-assisted Software Development shows AI’s primary role and how this affects organizations.
Check it out here.
The 2025 DORA report is out! The report - The State of AI-assisted Software Development shows AI’s primary role and how this affects organizations.
Check it out here.
Demand for manual software development steadily drops both in current region and in the world in whole. AI-supported tools grow up their consistence step by step. It will eventually lead to best ever automatically generated software code delivered faster and priced much less for better quality, reliability, and performance.
Scientifically supported solutions will take more importance along this trend. Shown below is multi-component software solution for processing customized pipelines of streaming data. Its core element drives any sort of computing model. It can run in server mode or can be examined at runtime. Character of interactions reminds MCP protocol, very popular today in AI agents world.
“Every engineer remembers their first time.”
Not shipping code—but watching it break in production at 3 a.m. And diving into a Slack war room with 50 others, trying to find a root cause in a sea of telemetry noise.
That’s the world Traversal is rebuilding—from the ground up.
At this year’s RAISE Summit at the Louvre, Anish Agarwal, Traversal’s CEO (MIT PhD in causal ML), took the stage to challenge one of software’s ugliest truths: the more AI writes our code, the less context engineers have—and the harder debugging gets.
But Traversal’s thesis is clear:
→ Writing code is easy.
→ Keeping software reliable is the next trillion‑dollar problem.
→ And AI agents + causal inference are the missing layer.
Instead of dashboards and “alert storms,” Traversal uses swarms of LLM agents performing parallel, semantic investigations, grounded in causal ML, to pinpoint the real root cause—fast.
The company launched with $48 million in funding, led by Sequoia and Kleiner Perkins, with participation from NFDG and Hanabi. DigitalOcean has already rolled it out org‑wide, with AmEx and Eventbrite next in line.
Considering enterprise downtime can cost up to $1.9M per hour, this isn’t just a better observability tool—it’s the AI SRE every engineering team will need.
If GitHub Copilot is AI for creation, Traversal is AI for continuity—and it might just be the most important devtool startup of this generation.
https://lnkd.in/e2eDTDC9
Thanks for sharing, Vijay