{"id":24901,"date":"2026-06-18T08:00:51","date_gmt":"2026-06-18T01:00:51","guid":{"rendered":"https:\/\/fpt-is.com\/en\/?post_type=goc_nhin_so&p=24901"},"modified":"2026-06-18T17:38:23","modified_gmt":"2026-06-18T10:38:23","slug":"the-final-machine-is-the-mind-as-software-gets-cheaper-responsibility-gets-pricey","status":"publish","type":"goc_nhin_so","link":"https:\/\/fpt-is.com\/en\/insights\/the-final-machine-is-the-mind-as-software-gets-cheaper-responsibility-gets-pricey\/","title":{"rendered":"The final machine is the mind: as software gets cheaper, responsibility gets pricey"},"content":{"rendered":"

A person who can\u2019t code sits with AI for an afternoon and builds a working app. Today, that no longer shocks us like it did a year ago. But if you pause for a moment, it\u2019s still deeply strange.<\/span><\/p>\n

For two centuries, nearly every major technological leap replaced humans in their limbs. This time, machines are starting to intrude into the realm of thought. Not the entire mind\u2014but enough to shake an old assumption: that cognitive labor is humanity\u2019s final refuge. And when even that last layer is touched, the rules change\u2014for both engineers and the people who pay them.<\/span><\/p>\n

\"The<\/a><\/span><\/p>\n

The 200-year ladder<\/b><\/span><\/h2>\n

Looking back at history reveals a rather consistent pattern: every technological revolution tells the same story\u2014machines replace humans in one type of work, differing only in <\/span>which part<\/span><\/i> they replace.<\/span><\/span><\/p>\n

The steam engine replaced muscle; one worker with a power loom produced as much as many workers before. Electricity and assembly lines replaced repetitive labor at scale\u2014Henry Ford didn\u2019t invent the car; he changed how it was built. Computers replaced rule-based office work: calculation, storage, ledger reconciliation. Look far enough, and the shift becomes clear: machines always move from the rough to the refined aspects of labor. Human strength first, then repetitive operations, then processes describable by rules.<\/span><\/p>\n

Each time a layer gets automated, humans move up to a higher layer\u2014one requiring more judgment, more understanding, more responsibility. In 1800, most American workers were in agriculture; by the late 20th century, that figure was just a few percent. Farming didn\u2019t disappear, but direct labor demand plummeted, and people shifted to factories, offices, research, and services. For 200 years, that was almost always the escape route: machines get better at the lower layers, humans climb higher.<\/span><\/p>\n

The problem is, the ladder has a top. And the layer machines are touching now is one we previously assumed only knowledge workers could handle. Not all thinking, but enough to force us to rethink how we create value.<\/span><\/p>\n

When machines start drafting thoughts<\/b><\/span><\/h2>\n

AI doesn\u2019t carry loads, turn wheels, or stand on assembly lines. It reads, writes, reasons, synthesizes, generates code, proposes solutions\u2014and in many cases, drafts the very first version of a decision.<\/span><\/p>\n

Steve Jobs once called the computer \u201ca bicycle for the mind\u201d: it helps humans go farther and faster, but the person still pedals. AI is different\u2014it\u2019s not just a bicycle; it starts suggesting the route itself. That\u2019s what makes many people uncomfortable. When muscle gets replaced, humans retreat to the mind. So when part of the mind gets replaced, where do we retreat to?<\/span><\/p>\n

Software isn\u2019t dying\u2014The way we create it is<\/b><\/span><\/h2>\n

That\u2019s why I wrote a few months ago that \u201c<\/span>Software Development is dead<\/span><\/a>.\u201d Many read that as a prediction about the software industry. In reality, it\u2019s just one manifestation of a much larger movement.<\/span><\/span><\/p>\n

Software isn\u2019t the only field affected. It\u2019s simply where we see most clearly what\u2019s happening: the cost of turning ideas into intellectual products is dropping at unprecedented speed.<\/span><\/p>\n

That question leads straight to the real meaning behind what sounds like a sensational claim. Software isn\u2019t becoming unimportant\u2014on the contrary, it\u2019s more critical than ever. What\u2019s changing is the cost of creating it.<\/span><\/p>\n

The part that once made an engineer\u2019s value scarce\u2014the ability to translate requirements into code\u2014is plunging in price rapidly. In a controlled Microsoft Research experiment, teams using GitHub Copilot completed a specific programming task (building an HTTP server in JavaScript) <\/span>55.8% faster<\/b> than teams without it.<\/span><\/span><\/p>\n

That number doesn\u2019t prove AI can replace engineers; it shows the \u201ccode generation\u201d layer is being accelerated dramatically.<\/span><\/p>\n

This commoditization isn\u2019t happening uniformly. Software with repetitive structures and clear requirements gets hit first. Systems requiring extreme reliability, complex business constraints, or intricate operations change more slowly. But even there, the cost of producing lines of code is falling.<\/span><\/p>\n

Just as when the power loom appeared, fabric didn\u2019t lose value\u2014the skill of hand weaving did.<\/span><\/p>\n

Translate this into financial language for business leaders: what you once paid a premium to own is becoming a commodity. And whatever becomes common sooner or later ceases to be a competitive advantage. Advantage shifts elsewhere.<\/span><\/p>\n

The 1-Man Module: one person owning a slice of value<\/b><\/span><\/h2>\n

Previously, a sufficiently large scope usually required many people: requirements analyst, designer, backend developer, frontend developer, tester, reviewer, operator. AI isn\u2019t making those roles disappear, but it collapses many of the operations within them into the hands of one sufficiently skilled person.<\/span><\/p>\n

One person, if they understand the problem correctly and know how to use AI, can quickly build a prototype, write most of the code, generate test cases, read logs, find bugs, write documentation, even create a demo for stakeholders. Tasks that once required a small team now orbit around one person.<\/span><\/p>\n

But here\u2019s where misunderstanding easily happens. A 1-Man Module doesn\u2019t mean one person doing everything haphazardly. It means one person fully owning a slice of value\u2014from understanding the problem, creating the solution, validating it, to operating it.<\/span><\/p>\n

AI helps that person move faster. But what keeps that speed from becoming chaos is the harness.<\/span><\/p>\n

\"The<\/a><\/span><\/p>\n

The old team dissolves into one person. That person doesn\u2019t do less\u2014they decide more.<\/span><\/p>\n

Harness: Turning Speed into Reliability<\/b><\/span><\/h2>\n

I\u2019ll temporarily call that part the harness\u2014the entire mechanism that turns AI\u2019s speed into reliable outcomes.<\/span><\/p>\n

Imagine a car for clarity. The engine is the most powerful part, but placing an bare engine block on a road gets you nowhere. You need a steering wheel to drive, brakes to stop, seatbelts to protect, a chassis to bear load\u2014only then does the engine\u2019s power become a car that drives on real roads.<\/span><\/p>\n

AI is the engine. The harness is everything else in the car. Specifically, it\u2019s the control framework around AI and around the module: testing, guardrails, code conventions, review rules, deployment pipelines, monitoring, rollback mechanisms when failures occur, security checks, acceptance criteria.<\/span><\/p>\n

Without a harness, AI just increases the speed of generating garbage. With a harness, AI becomes an amplifier.<\/span><\/p>\n

\"The<\/a><\/span><\/p>\n

Everyone can buy the same engine. The difference lies in the rest of the car.<\/span><\/p>\n

This is also why the debate over \u201cwhich model is stronger\u201d often misses the point. With the same AI and the same problem: someone without a harness produces an interface, an API, a few green tests\u2014looks like it works. Someone with a harness limits scope, separates guesswork from what must be absolutely accurate, plugs in clean data, verifies, then deploys via a traceable process. Two products look identical in a demo, but only one survives the first month of operation.<\/span><\/p>\n

AI is getting better at producing solutions. But it still depends on the quality of context provided. In many organizations, the bottleneck is no longer whether a solution can be written, but whether the problem to solve is understood correctly, operational constraints are understood correctly, and the consequences of each choice are understood correctly.<\/span><\/p>\n

That\u2019s why domain expertise, system intuition, and real-world operational experience remain irreplaceable assets.<\/span><\/p>\n

In other words, the engineer\u2019s future isn\u2019t sitting and writing lines of code faster than AI. It\u2019s designing systems so AI creates software within a safe boundary, with validation, with accountability. AI generates the draft; the harness turns the draft into something trustworthy; humans take responsibility for the entire loop.<\/span><\/p>\n

There\u2019s a curious linguistic detail that fits this story oddly well. Many people think the word <\/span>engineer<\/span><\/i> comes from <\/span>engine<\/span><\/i>\u2014the machine. But both trace back to a deeper Latin root: <\/span>ingenium<\/span><\/i>, meaning intelligence, cleverness, creative capacity. The engineering profession at its root has never been just about writing code or operating machines; it\u2019s about using intelligence to solve problems. AI is taking away part of the \u201cmachine,\u201d and pushing humans back to exactly the \u201cmind\u201d part.<\/span><\/span><\/p>\n

Humans plus machines, not humans versus machines<\/b><\/span><\/h2>\n

Chess is the clearest example. When Deep Blue defeated Garry Kasparov in 1997, many believed human chess was over. It didn\u2019t happen. Kasparov reached a different conclusion: the strongest future isn\u2019t humans versus machines, but humans plus machines\u2014he essentially said machines don\u2019t make humans obsolete; human complacency does.<\/span><\/p>\n

That\u2019s not comfort; it\u2019s a warning. Clinging tightly to old skills means losing; knowing how to use machines to elevate judgment means still having a chance.<\/span><\/p>\n

But to know where to add machines, you must avoid the two extremes everyone easily falls into: one side thinks AI replaces everything immediately, the other thinks it\u2019s just hype that will pass. Both can be wrong.<\/span><\/p>\n

Roy Amara has a memorable quote: we tend to overestimate technology\u2019s impact in the short term and underestimate it in the long term.<\/span><\/p>\n

In the short term, many demos create illusions\u2014look intelligent but break when facing real data, real users, real constraints. Long term, when AI embeds into processes, tools, hiring practices, productivity measurement, and decision-making, its impact is far deeper than a few demonstrations.<\/span><\/p>\n

So the right question isn\u2019t \u201cWill AI replace engineers?\u201d but rather: which parts of an engineer\u2019s work will get commoditized first, and which will become scarcer?<\/span><\/p>\n

The answer is becoming clear. Writing code gets cheaper; understanding the problem correctly gets more expensive. Generating solutions gets cheaper; choosing the right solution gets more expensive. Building demos gets cheaper; real operations get more expensive. Knowing how to use AI will be a baseline skill everyone has; knowing how to take responsibility for AI\u2019s output is the differentiating capability.<\/span><\/p>\n

The Compressed Shift<\/b><\/span><\/h2>\n

History shows professions rarely disappear completely, but there are always generations stuck between two eras\u2014people holding skills that just lost value before they\u2019ve built new ones. AI\u2019s biggest difference isn\u2019t in nature but in speed. The steam engine took decades to spread widely; electricity took multiple decades to restructure production; the internet needed nearly twenty years. AI reached massive user scale in a very short time, then continued improving on cycles measured in months.<\/span><\/p>\n

McKinsey Global Institute estimates that by 2030, approximately 30% of current work hours could be automated\u2014a trend significantly accelerated by GenAI. Notably, this figure remains quite consistent across the organization\u2019s 2023 and 2024 reports, even as the analysis scope expanded from the US to Europe and many other major economies.<\/span><\/p>\n

But the more thought-worthy point isn\u2019t the automation rate. McKinsey also estimates the number of people needing occupational transitions by 2030 could be about 25% higher than forecasts made before GenAI emerged. That doesn\u2019t necessarily mean jobs disappearing. It means the speed of skill shifts is accelerating.<\/span><\/p>\n

This is no longer a story for the next generation. It\u2019s the story of this cycle.<\/span><\/p>\n

 <\/p>\n

Organizations must redesign around responsibility<\/b><\/span><\/h2>\n

Individuals can teach themselves new skills. Organizations must redesign how they create value. A few things worth starting immediately:<\/span><\/p>\n

Change how you measure value. Stop measuring engineers by lines of code, stop rewarding activity, start measuring by outcomes: does the feature create business impact, is the system more stable, are risks controlled well? When code-writing costs plummet, counting lines becomes a dangerous metric\u2014it makes organizations think they\u2019re creating value when they\u2019re actually just creating more maintenance surface area.<\/span><\/p>\n

Invest in AI operational capability, not just buying AI. Good models will quickly become commodities anyone can buy. What\u2019s hard to copy is how an organization controls and leverages them: verification processes, risk governance, access control, monitoring, resilience when AI returns wrong results. Two companies using the same model can produce vastly different outcomes\u2014the difference lies in the operating system around the model, not the model itself. That\u2019s the real competitive moat.<\/span><\/p>\n

Organize around outcome ownership. When one person can do work that once required an entire team, the need for intermediate coordination drops. Organizations will become flatter, with fewer transitional layers, more people taking direct responsibility.<\/span><\/p>\n

That doesn\u2019t mean the middle management layer disappears. It means the value of management changes. When AI reduces the cost of information synthesis, reporting, and coordination, a manager\u2019s value no longer lies in transmitting information but in making decisions under uncertainty.<\/span><\/p>\n

A strong manager isn\u2019t someone who controls more activities, but someone who helps the organization make better decisions with less friction.<\/span><\/p>\n

Don\u2019t abandon the middle generation. This group is the riskiest, but also the most valuable. They have operational intuition, domain knowledge, troubleshooting experience, and organizational knowledge that AI doesn\u2019t yet possess. Abandoned, they become obstacles; properly retrained, they become the most effective AI amplifiers. Organizations that only hire new people who know AI while forgetting to upgrade existing staff are erasing their own operational memory.<\/span><\/p>\n

Race against the clock. AI doesn\u2019t wait for anyone to finish adapting before moving forward. Organizations treating this as a future issue will learn from a position of disadvantage. Advantage belongs to those who start changing while there\u2019s still time to try, fail, and fix.<\/span><\/p>\n

Conclusion<\/b><\/span><\/h2>\n

Every time technology steps to a new rung, it takes away part of the value that once belonged to humans, then forces us to redefine ourselves by what remains. Muscle was lost long ago. Now it\u2019s a part of the mind. But the ability to determine what\u2019s worth doing, make judgments in uncertain contexts, and take responsibility for final outcomes\u2014those still can\u2019t be automated.<\/span><\/p>\n

Two hundred years ago, machines took away the advantage of muscle. Today, AI is starting to take away the advantage of part of the thinking process. Each time this happens, value shifts to a higher layer.<\/span><\/p>\n

If AI is the most powerful engine ever to appear for cognitive labor, then the remaining question isn\u2019t how powerful the engine is, but who\u2019s holding the steering wheel.<\/span><\/p>\n

 <\/p>\n\n\n\n
Exclusive article by FPT expert Vo Ta Nhat Anh – Solution Architect, Manufacturing Division, FPT\u00a0 IS, FPT Corporation.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

References<\/b><\/span><\/h2>\n
    \n
  1. McKinsey Global Institute<\/b> (July 2023). <\/span>Generative AI and the future of work in America<\/span><\/i>.<\/span>
    \n<\/span>Link<\/span><\/a><\/span><\/li>\n
  2. McKinsey Global Institute<\/b> (May 21, 2024). <\/span>A new future of work: The race to deploy AI and raise skills in Europe and beyond<\/span><\/i>. Eric Hazan, Anu Madgavkar, Michael Chui, Sven Smit, et al.<\/span>
    \n<\/span>    Link<\/span><\/a><\/span><\/li>\n<\/ol>\n","protected":false},"author":21,"featured_media":24905,"parent":0,"template":"","nang_luc":[],"danh_muc_goc_nhin_so":[882],"dich_vu":[],"linh_vuc":[],"platform":[],"san_pham":[],"the_goc_nhin_so":[],"class_list":["post-24901","goc_nhin_so","type-goc_nhin_so","status-publish","has-post-thumbnail","hentry","danh_muc_goc_nhin_so-data-ai-insights"],"acf":[],"_links":{"self":[{"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/goc_nhin_so\/24901","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/goc_nhin_so"}],"about":[{"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/types\/goc_nhin_so"}],"author":[{"embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/users\/21"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/media\/24905"}],"wp:attachment":[{"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/media?parent=24901"}],"wp:term":[{"taxonomy":"nang_luc","embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/nang_luc?post=24901"},{"taxonomy":"danh_muc_goc_nhin_so","embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/danh_muc_goc_nhin_so?post=24901"},{"taxonomy":"dich_vu","embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/dich_vu?post=24901"},{"taxonomy":"linh_vuc","embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/linh_vuc?post=24901"},{"taxonomy":"platform","embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/platform?post=24901"},{"taxonomy":"san_pham","embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/san_pham?post=24901"},{"taxonomy":"the_goc_nhin_so","embeddable":true,"href":"https:\/\/fpt-is.com\/en\/wp-json\/wp\/v2\/the_goc_nhin_so?post=24901"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}