Coding Is Just Typing, Then What? From Explicit Programming to Implicit Programming

Post Title Image (A dish that breaks the rules of the game can show up even during a casual meal. Turns out Greek cuisine has its own version of sashimi, paired with a light touch of avocado mousse that balances out the richness of the tuna, making it the star among the bite-sized appetizers. At Taverna in Palo Alto, a dancing silhouette tucked in the corner of the menu reminds us: “Every day is a gift.” We will live well, and challenge the rules together. Image source: Ernest.)

✳️ Typing has become a commodity

Jensen Huang, holding a glass of white wine at the late-night session of Cisco AI Summit 2026, said: “Coding as it turns out is just typing. And typing as it turns out is a commodity.”

This isn’t putting down engineers. For 60 years, we’ve been telling computers exactly what to do, line by line in Fortran, C, C++. That’s called explicit programming. Now we’re entering the era of implicit programming, where we tell computers our intent and they figure out how to solve it. Just like that, the scarcity of “being able to write code” has vanished.

Since last Lunar New Year, I’ve gone from Cline to Cursor to Claude Code, and my deepest takeaway is: Coding is Easy, Context is Hard. When AI can write the code we want in seconds, the bottleneck has long shifted from typing speed to whether we can articulate the context of the problem, the boundary conditions, and the edge cases clearly. That’s why I moved from Vibe Coding toward Spec-Driven Development combined with organizational workflow frameworks: define “what to do” and “why” in human language first, then let AI handle “how to do it.”

✳️ Apply infinity to it

He offered a thinking framework: “Apply infinity to it. Apply zero to it. Apply the speed of light to it.”

Moore's Law is 10x every 5 years. Jensen says AI is 1,000,000x in 10 years. If something that used to take a year now completes instantly, what would we do differently? If something that used to be heavy now has zero weight, how would we redesign it? He said if we’re not thinking about problems this way, “you’re doing it wrong.”

He gave an example: processing large-scale graph analytics used to require breaking it into small batches. Now? “How big is it? I don’t care. Just give me the whole graph.” Then he added: “Just imagine a company who is about to get founded is thinking that way. It changes everything.” A startup that hasn’t even been founded yet is already designing with an abundance mindset from day one. How do we compete with that? When I help clients decompose legacy ERP systems, I use exactly this line of thinking: if a query no longer needs an overnight batch run and returns results in real time, the move isn’t to speed up the old system, it’s to reimagine the entire workflow.

✳️ Domain knowledge is the real programming language

“When you graduate, you can write amazing code but have absolutely no idea what the customer wants or what problem to solve. But you do.”

Jensen said this to a room full of enterprise people. What used to feel like a weakness, not knowing how to code, is now an advantage. AI lets everyone communicate with computers in their own language. Our domain expertise is our programming language.

Before the pandemic, I participated in the Bluetooth SIG to help define the FTMS Bluetooth communication spec. I learned that the time spent defining requirements and boundary conditions was easily ten times more than the time spent writing code. But precisely because the spec was clear, manufacturers around the world could develop interoperable products. What Jensen describes as implicit programming is the same thing: we clearly express our intent, and let the execution layer handle the implementation. The ability to transform vague requirements into clear intent is the most valuable skill.

✳️ For the first time, we can communicate with computers in our own language

Jensen tied it all together at the end: “All of you could escape from this limitation which is we don’t have enough software engineers, because typing is a commodity.”

He wasn’t just saying there are more engineers now. He was saying the definition of “who can write code” has been fundamentally rewritten. No need to know Python or JavaScript. We can communicate with computers in Chinese, English, Japanese, any language. In 60 years of computing history, this is the first time the barrier to software development has been brought to near zero. When I spoke about “Reinventing Programming” at AWS Summit Hong Kong, the core message was the same: it’s not that the tools got better, it’s that the rules of the game changed. When typing becomes a commodity, the real value returns to the things hardest to automate: understanding context, defining direction, making trade-offs. And these happen to be exactly what we do every day at PAFERS and Kyklosify.

Post Title Image (A dancing silhouette tucked in the corner of the Taverna restaurant menu in Palo Alto reminds us: “Every day is a gift.” We will live well, and challenge the rules together. Image source: Ernest.)


✳️ Further Reading