The AI Boom Can Bust. AI Adoption Won't Stop.
Translated from the original Korean post. 한국어 원문 보기 →
What using AI every day actually feels like
I was cleaning up my work setup recently and noticed something. AI had crept into nearly everything — writing code, drafting docs, replying to email, summarizing meeting notes. It started as "let me try this thing." Now a screen without an AI assistant feels off. Like reaching for a keyboard shortcut that isn't there.
Meanwhile the news says the opposite. The AI bubble is about to pop. GPU spending has overheated. Valuations have run way ahead of earnings. On my desk AI keeps digging in deeper; in the market people are calling it a bubble. That gap got my attention.
The two stories don't actually contradict each other. They're two different things wearing the same word. One is the AI investment boom. The other is AI spreading through society. Split them apart and a lot of confusion clears up.
So let me take an engineer's pass at separating them. Conclusion first: the AI boom can go bust. AI adoption is much harder to stop.

Two AIs: the investment boom and the spread
Right now the AI market has two completely different currents running through it.
The first is the investment boom. Slap "AI" on something and the valuation goes up. GPU makers, data centers, model companies — all carrying expectations far beyond what's been proven. This part can absolutely correct: earnings don't materialize, payback takes too long, capacity overshoots, rates move. A lot of that price came from sentiment.
The second is AI spreading through society. Search, writing, coding, customer support, education, manufacturing, finance, security, ops, personal assistants — AI quietly getting embedded in all of it. This runs almost independently of a stock drawdown. Share prices falling doesn't make my code completion disappear.
Which means the question that matters isn't "how long does the boom last." It's "which parts of this actually dissolve into the systems people run on." The first is a sentiment question. The second is a structural one. Measure them with the same ruler and you'll get the answer wrong.
From novelty to annoyance — expectations shift
If you want to see how AI hardens from a trend into infrastructure, watch what users start demanding.
Early on people treated it like a fun toy. AI writes text. AI makes pictures. AI writes code. AI replaces search. The emotion is amazement.
Then usage piles up and the questions change. Why doesn't it remember what I told it before? Why can't it reason about my company's situation? Why do I have to re-explain the same thing every time? Push further and it becomes: why can't it connect my docs, my email, my calendar, my work history? Why can't it actually finish the task?
Those complaints are the important signal. They mean AI is moving from being a feature to being a layer your work runs on. The moment amazement turns into annoyance, a technology has stopped being a trend and become part of daily life.
Back when I was running internet banking systems, the point where user complaints shifted from "neat" to "why doesn't this work" was the point the feature had become table stakes. Annoyance is demand, expressed rudely.
So the long-term value of AI lives less in the model itself and more in this stack:
AI 모델
↓
AI 내장 서비스
↓
개인/조직 메모리
↓
업무 맥락 이해
↓
소프트웨어 로봇
↓
업무 자동화와 실행
It starts at the model, but the money and the value accumulate further down. Past "good answer" and into "understands the context and actually does the thing."
Boom vs. adoption, line by line
Under the same "AI" umbrella, different items have very different fates. Here's my split between what can correct and what spreads structurally.
| 구분 | 성격 | 전망 |
|---|---|---|
| AI 테마주 과열 | 투자 심리 | 조정 가능 |
| 단순 챗봇 서비스 | 기능 경쟁 | 경쟁 심화 가능 |
| 모델 기업 밸류에이션 | 기대 기반 | 수익성 검증 필요 |
| GPU·데이터센터 과잉투자 | 설비 투자 | 일부 과잉 가능 |
| 기업 업무 자동화 | 비용 절감 | 장기 확산 가능 |
| 개인화 AI 비서 | 사용성 개선 | 장기 확산 가능 |
| 메모리 AI | 맥락 이해 | 구조적 수요 증가 |
| AI 에이전트 | 실행 자동화 | 차세대 응용 |
| 전력·저장·통신 인프라 | 물리 기반 | 장기 수요 지속 |
The top of the table is mostly sentiment and expectation. The bottom is real demand and physical constraints. One sentence covers it: the investment froth can burn off, but the user experience doesn't roll back.
The dot-com bubble popped and the internet stayed. Same shape here. AI themes can correct while AI keeps sinking into everything. Prices swing. Habits don't.
History has walked this road before
None of this pattern is new. Tech revolutions tend to trace the same arc.
The internet. The late-90s dot-com bubble was spectacularly overheated and killed a lot of companies. The internet itself didn't go anywhere. E-commerce, search, advertising, cloud, mobile platforms — all of it grew on top afterward. The froth was froth; the foundation was real.
Mobile. Early smartphone and app store days had their own mania. "Just build an app" was a business plan. Most of the lightweight apps got cleared out, but mobile became life infrastructure. I watched internet banking turn into mobile banking up close, and what survived wasn't the clever apps — it was the functions that wedged themselves into daily work. Nobody today thinks "I am using mobile." We just live inside it.
Now AI. Same likely path. It opens with "AI changes everything" overheating. Then the weak services and the overvalued companies get cleaned out. What survives seeps into search, office software, development, CRM, manufacturing, security, finance, education, ops systems. At that point it stops being a trend and becomes a default. Just like mobile, I expect we'll be working inside AI without thinking about "using AI."
Three reasons the spread is hard to stop
So why is adoption hard to reverse? Three forces, the way I see it.
-
Productivity pressure. Companies always need to cut cost and produce more. AI can automate document work, customer support, development, ops, analysis, reporting, audit response. The pressure is strongest in industries with high labor costs and lots of documents, communication, and repetitive judgment calls. Once an organization has seen the benefit, pulling it back out is hard. From where I sit as an ops PM, I've almost never seen a team decide to un-automate a process and go back to doing it by hand.
-
Experience is irreversible. This is the strongest one. Once someone has worked with an AI assist, going back is painful. Autocomplete, summarization, translation, code help, drafting email, cleaning up calendars, searching documents — the baseline expectation itself moves. The real engine of adoption isn't amazement, it's annoyance. "AI is amazing" is an early-market feeling. "Working without AI is annoying" is a structural-adoption feeling. AI is already crossing into the second one.
-
Data and memory compound. The longer you use it, the more context you demand. Not just Q&A — you want answers that account for past conversations, work history, customer records, project history, decision criteria. Meeting that requires memory, storage, search indexes, knowledge graphs, permission management. So adoption naturally pulls the next set of industries along with it.
AI 사용 증가
↓
맥락 이해 요구 증가
↓
메모리·저장 수요 증가
↓
업무 자동화 요구 증가
↓
소프트웨어 로봇 확산

The next growth axis sits outside the model
The next leg of AI growth probably happens around and beneath the model, not in it.
Memory AI. The layer that holds long-term context for a person and an organization. Personal preferences, work history, customer relationships, project context, document history, decision criteria, recurring task patterns — that has to accumulate before AI becomes a real assistant or a real staff officer. Memory AI isn't a storage bucket, it's a context operating system. Two teams on the same model get different results depending on who has the richer context.
AI infrastructure. AI looks like software, but it runs on enormous physical plant. The more it spreads, the more demand for HBM, DRAM, NAND, SSDs, GPUs, grid capacity, transformers, UPS, ESS, cooling, optical networking, data centers. What you see on screen is a chat box. Behind it are electricity, heat, and disks. Run a single Kubernetes cluster and you feel this — there's always physical resource one abstraction layer down, and it bills you honestly.
Software robots. I think the endgame for AI applications isn't a chatbot, it's a software robot: something that remembers, understands, judges, executes, records, and feeds the result into the next task. For a company, the value isn't in "a good answer," it's in "the work got done." Hearing an answer and having the job finished are different categories.
Where the openings are
Here are the places I'd expect domain-specific software robots to earn their keep.
- Enterprise ops robots — server operations, incident response, security checks, CVE remediation, change notices, post-incident actions, audit response. They only work when wired into internal operational data, so domain understanding is the whole game. If you've ever been paged at 3am and gone digging through logs, this one needs no pitch.
- Security and audit robots — checklists, evidence, access logs, account reviews, exception approvals, training records. In a space governed by rules and accountability, a traceable execution record matters far more than a good answer.
- Manufacturing and quoting robots — remembering drawings, materials, lead times, suppliers, margins, past quotes, revision history, and helping produce quotes. Small manufacturers run on tacit knowledge, which is exactly where memory-based AI pays off.
- Customer management robots — reservations, no-shows, repeat visits, customer preferences, messaging, review requests, sales analysis. For small businesses, what matters isn't AI as such but automation that turns into revenue and return visits.
Notice the common thread. Every one of them requires deep understanding of a specific industry's workflow, data, regulations, and execution process. A general-purpose chatbot can't reach these.
The risks are real
It'd be dishonest to paint this all rosy just because the adoption current is strong. So, the risks.
Investment overheating first. AI company valuations can run ahead of results, and pure AI-theme names are the most exposed to a correction. Monetization lag comes with it: if adoption doesn't turn into real cost savings or revenue, some services get shut down. Infrastructure cost is no joke either — GPUs, power, data centers, and cloud bills squeeze the margins on AI services.
The last two are a different kind of problem. Reliability carries hallucination, bad memories, security incidents, data leaks, and unclear accountability; until those are solved, fully autonomous execution stays fenced in. Regulation is the same story. Finance, healthcare, public sector, education, and legal will likely see tighter rules on personal data, copyright, explainability, and liability.
Those last two stay on my mind as an engineer. If working in financial IT taught me anything, it's that a system that executes also owns the consequences of executing wrong. The further AI moves from answering to doing, the heavier that gets. Which is why traceability and permission management end up being the real competitive edge.
How I'd adjust the lens
If you buy this framing, the way you look at the AI era should shift a bit. Five things.
Bet on embedding, not on the boom. Look for what becomes mandatory over time rather than what's hot right now. And look at context, not the model. Model quality converges; the differentiated asset is the context data a person or organization has built up.
Applications go domain-specific. General chatbots probably belong to big tech, and the opening is in narrow, deep territory where you understand one industry's workflow, data, rules, and execution process. Following from that, software robots reshape SaaS. Traditional SaaS is a tool that humans type into and maintain; the shape ahead is AI querying, judging, executing, and reporting directly. And infrastructure is the long-term beneficiary. The more AI spreads, the more memory, power, storage, networking, cooling, and data centers matter.
The core shift in the AI industry moves in this order:
AI 테마
↓
AI 기능
↓
AI 인프라
↓
AI 메모리
↓
AI 에이전트
↓
소프트웨어 로봇

Wrapping up
AI started as a trend, but I think it's hardening into a base layer of how work and society run. Short term, sure — overheated investment, valuation pressure, infrastructure overbuild, delayed monetization. A correction is entirely plausible. Long term, AI most likely ends up inside search, documents, development, ops, CRM, manufacturing, security, education, and financial systems as a default feature.
Which is why I think the long-run winners won't be the companies selling the word "AI." They'll be the infrastructure and domain-specific software companies that let AI remember and execute.
The bubble can pop. But putting down a tool your hands have learned turns out to be much harder than it sounds.
Was this post helpful?
One click helps me write the next one