Search

1000 results for “im_a_GDeveloper”

DrWeb @[email protected] · 2026-02-12 · 18:31 UTC

Something big is happening in AI — and most people will be blindsided – Fortune
Matt Shumer, co-founder and CEO of OthersideAI. courtesy of OthersideAI
Commentary Entrepreneurship
Something big is happening in AI — and most people will be blindsided
By Matt Shumer, February 11, 2026, 9:22 AM ET
Matt Shumer is the co-founder and CEO of OthersideAI, an applied AI company building the most advanced autocomplete tools in the world, powered by large-scale AI systems like GPT-3. OthersideAI is the company behind HyperWrite, the leading AI autocomplete Chrome extension for consumers. Previously, while in high school, Matt founded Visos, a startup developing next-generation Virtual Reality software designed for medical use, and FURI, a company aiming to disrupt the sporting goods industry by creating high-performance products and selling them for fair prices.
Think back to February 2020.
A few people were talking about a virus spreading overseas. If someone told you they were stockpiling toilet paper you would have thought they’d been spending too much time on a weird corner of the internet. Then, over the course of about three weeks, the entire world changed.
I think we’re in the “this seems overblown” phase of something much, much bigger than Covid.
I’ve spent six years building an AI startup and investing in the space. I live in this world. And I’m writing this for the people in my life who don’t. I keep giving them the polite, cocktail-party version. Because the honest version sounds like I’ve lost my mind. But the gap between what I’ve been saying and what is actually happening has gotten far too big. The people I care about deserve to hear what is coming, even if it sounds crazy.
I should be clear about something up front: even though I work in AI, I have almost no influence over what’s about to happen, and neither does the vast majority of the industry. The future is being shaped by a remarkably small number of people: a few hundred researchers at a handful of companies… OpenAI, Anthropic, Google, DeepMind, and a few others.
Most of us who work in AI are building on top of foundations we didn’t lay. We’re watching this unfold the same as you… we just happen to be close enough to feel the ground shake first.
But it’s time now. Not in an “eventually we should talk about this” way. In a “this is happening right now and I need you to understand it” way.
I know this is real because it happened to me first
Here’s the thing nobody outside of tech quite understands yet: we’re not making predictions. We’re telling you what already occurred in our own jobs, and warning you that you’re next.
For years, AI had been improving steadily. Then in 2025, new techniques for building these models unlocked a much faster pace of progress. This year, something clicked. Not like a light switch… more like the moment you realize the water has been rising around you and is now at your chest.
I am no longer needed for the actual technical work of my job. I describe what I want built, in plain English, and it just… appears. Not a rough draft I need to fix. The finished thing. I tell the AI what I want, walk away from my computer for four hours, and come back to find the work done. Done well, done better than I would have done it myself, with no corrections needed. A couple of months ago, I was going back and forth with the AI, guiding it, making edits. Now I just describe the outcome and leave.
Let me give you an example so you can understand what this actually looks like in practice. I’ll tell the AI: “I want to build this app. Here’s what it should do, here’s roughly what it should look like. Figure out the user flow, the design, all of it.” And it does. It writes tens of thousands of lines of code. Then, and this is the part that would have been unthinkable a year ago, it opens the app itself. It clicks through the buttons. It tests the features. It uses the app the way a person would. If it doesn’t like how something looks or feels, it goes back and changes it, on its own. It iterates, like a developer would, fixing and refining until it’s satisfied. Only once it has decided the app meets its own standards does it come back to me and say: “It’s ready for you to test.” And when I test it, it’s usually perfect.
I’m not exaggerating. That is what my Monday looked like this week.
I’ve always been early to adopt AI tools. But the last few months have shocked me. These new AI models aren’t incremental improvements. This is a different thing entirely.
The experience that tech workers have had over the past year, of watching AI go from “helpful tool” to “does my job better than I do”, is the experience everyone else is about to have. Law, finance, medicine, accounting, consulting, writing, design, analysis, customer service. Not in 10 years. The people building these systems say one to five years. Some say less. The market was spooked enough this month that it wiped out $1 trillion worth of software value in just a week. And given what I’ve seen in just the last couple of months, I see more disruption, and soon.
“But I tried AI and it wasn’t that good”
If you tried ChatGPT in 2023 or early 2024 and thought “this makes stuff up” or “this isn’t that impressive”, you were right. Those early versions were genuinely limited. They hallucinated. They confidently said things that were nonsense.
The models available today are unrecognizable from what existed even six months ago. The debate about whether AI is “really getting better” or “hitting a wall” — which has been going on for over a year — is over. It’s done. Anyone still making that argument either hasn’t used the current models, has an incentive to downplay what’s happening, or is evaluating based on an experience from 2024 that is no longer relevant. I don’t say that to be dismissive. I say it because the gap between public perception and current reality is now enormous, and that gap is dangerous… because it’s preventing people from preparing.
Part of the problem is that most people are using the free version of AI tools. The free version is over a year behind what paying users have access to. Judging AI based on free-tier ChatGPT is like evaluating the state of smartphones by using a flip phone. The people paying for the best tools, and actually using them daily for real work, know what’s coming.
I think of my friend, who’s a lawyer. I keep telling him to try using AI at his firm, and he keeps finding reasons it won’t work. And I get it. But I’ve had partners at major law firms reach out to me for advice, because they’ve tried the current versions and they see where this is going. One of them, the managing partner at a large firm, spends hours every day using AI. He told me it’s like having a team of associates available instantly. He’s not using it because it’s a toy. He’s using it because it works. And he told me something that stuck with me: every couple of months, it gets significantly more capable for his work. He said if it stays on this trajectory, he expects it’ll be able to do most of what he does before long… and he’s a managing partner with decades of experience. He’s not panicking. But he’s paying very close attention.
Think about what that means for your work.
What this means for your job
I’m going to be direct with you because I think you deserve honesty more than comfort.
Dario Amodei, who is probably the most safety-focused CEO in the AI industry, has publicly predicted that AI will eliminate 50% of entry-level white-collar jobs within one to five years. And many people in the industry think he’s being conservative. Given what the latest models can do, the capability for massive disruption could be here by the end of this year. It’ll take some time to ripple through the economy, but the underlying ability is arriving now.
This is different from every previous wave of automation, and I need you to understand why. AI isn’t replacing one specific skill. It’s a general substitute for cognitive work. It gets better at everything simultaneously. When factories automated, a displaced worker could retrain as an office worker. When the internet disrupted retail, workers moved into logistics or services. But AI doesn’t leave a convenient gap to move into. Whatever you retrain for, it’s improving at that too.
I think the honest answer is that nothing that can be done on a computer is safe in the medium term. If your job happens on a screen (if the core of what you do is reading, writing, analyzing, deciding, communicating through a keyboard) then AI is coming for significant parts of it. The timeline isn’t “someday.” It’s already started.
Eventually, robots will handle physical work too. They’re not quite there yet. But “not quite there yet” in AI terms has a way of becoming “here” faster than anyone expects.
What you should actually do
I’m not writing this to make you feel helpless. I’m writing this because I think the single biggest advantage you can have right now is simply being early. Early to understand it. Early to use it. Early to adapt.
Editor’s Note: Read more online. This is a general AI-supportive post by Matt. And there are many others similar “heads up” posts about AI right now. Keep an eye out for further posts on the AI changes coming. Whatever your views, I recommend keeping up with AI over your own work, or job, society changes, regulations, world impacts, and more. –DrWeb
Continue/Read Original Article Here: Something big is happening in AI — and most people will be blindsided | Fortune
Tags: AI, AI Future, artificial intelligence, Big Changes, Fortune, Heads Up, Jobs Changing, Matt Shumer, Newer Models, OthersideAI, Rapid Developments in AI, Social Impacts, Technology
#AI #AIFuture #artificialIntelligence #BigChanges #Fortune #HeadsUp #JobsChanging #MattShumer #NewerModels #OthersideAI #RapidDevelopmentsInAI #SocialImpacts #Technology

#ai #aifuture #artificialintelligence #bigchanges #fortune #headsup
Bryan King @[email protected] · 2026-02-16 · 12:30 UTC
The 3 React Upgrades SPFx Devs Are Ignoring (And Why Your Web Parts Are Leaking Performance)

1,402 words, 7 minutes read time.
Let’s cut the fluff: if your SPFx web parts feel sluggish, your state management is spaghetti, or your page crashes under moderate load, it’s because you’re not playing with React the way it’s meant to be played in 2026. The latest version of SPFx ships with React 18 support, but most devs treat it like yesterday’s framework, dragging legacy habits into modern code. I’ve seen it countless times: web parts patched with workarounds, effects firing endlessly, unoptimized re-renders eating CPU cycles, and junior devs praying that no one notices. The hard truth? If you can’t adapt to React’s new features, your code is dying on the vine, and so is your professional credibility.
This isn’t a gentle nudge. I’m here to break down the three React upgrades SPFx developers ignore at their own peril, why they matter technically, and how they mirror discipline—or the lack thereof—in your professional and personal life. First, we tackle the core of modern React: Concurrent Rendering and Automatic Batching.

Concurrent Rendering and Automatic Batching – Your Web Parts’ Backbone
When React 18 dropped concurrent rendering and automatic batching, it wasn’t a luxury—it was a lifeline. Most SPFx devs never adjust their components for this. They cling to class components with componentDidMount hacks or use hooks incorrectly, leaving effects firing multiple times, state updates queuing chaotically, and memory leaks piling up. In SPFx, where your web part is a node on the page with other parts loading simultaneously, this isn’t minor—it’s the difference between a smooth user experience and a browser meltdown.
I’ve refactored dozens of enterprise SPFx solutions. If your useEffect calls aren’t guarded, or you don’t understand how React batches state updates automatically now, you’re wasting render cycles and bleeding performance. Imagine deploying a web part that triggers three API calls per keystroke in a search box because you didn’t wrap state changes in proper batching logic. That’s a professional facepalm waiting to happen.
This is also about integrity. Your components are the kernel of your web part. If they panic, the whole page goes down. Every unguarded effect, every missed cleanup is like leaving a socket exposed: it’s dangerous, messy, and shows laziness. Learning concurrent rendering and embracing automatic batching isn’t optional; it’s the same principle you apply in life when you keep promises, manage your commitments, and clean up after yourself. Half measures don’t cut it in code or character.
From a pure technical perspective, understand that concurrent rendering allows React to interrupt long-running renders, prioritizing urgent updates and keeping the UI responsive. Automatic batching merges multiple state updates into a single render, reducing unnecessary DOM recalculations. In SPFx web parts, where you might be calling the SharePoint REST API or Microsoft Graph, this translates into fewer wasted renders, less flicker, and a page that doesn’t tank when multiple web parts fire simultaneously. It’s subtle, but anyone ignoring this is coding in yesterday’s world.
The takeaway is simple: refactor your legacy components, embrace hooks fully, and make React 18 work for you, not against you. Stop treating batching as magic and understand the lifecycle implications. Every clean render, every optimized state transition, is a reflection of the discipline you either bring or fail to bring to your work.
Suspense, Lazy Loading, and Code Splitting – Stop Shipping Monoliths
If you’re still bundling every component into a single SPFx web part, congratulations—you’re shipping a monolith nobody wants to wait for. React 18’s Suspense, combined with lazy loading, is your ticket to scalable, maintainable, and performant web parts. Yet most devs ignore it. They either don’t understand it or they fear breaking things, so they cling to the “just load everything upfront” mindset. That’s cowardice, plain and simple.
Suspense lets React pause rendering until a component or data is ready. Lazy loading defers non-critical components, shaving precious milliseconds off initial load time. In SPFx, where your web part might pull data from multiple lists, libraries, or Microsoft Graph endpoints, ignoring this is a performance crime. I’ve watched junior developers bake everything into bundle.js, resulting in 3MB downloads for a single web part. Users hate that. Management hates that. And your reputation? Tanking.
Implementing Suspense properly isn’t just technical. It forces discipline in planning component structure, dependencies, and render order. Every lazy-loaded component you ship cleanly mirrors your ability to compartmentalize and manage complexity in real life. A man who leaves tasks half-done, who tries to juggle everything without order, is coding like he lives: chaotic, inefficient, and fragile. You want clean SPFx web parts? Start thinking like a disciplined architect.
Technically, wrapping your web parts with Suspense and splitting components using React.lazy() reduces initial payload and allows React to prioritize urgent renders. Combined with proper error boundaries, you’re not just optimizing performance—you’re creating a resilient system. Lazy-loading non-critical components is like building load-bearing walls before the decorative trim: prioritize stability, then polish. Any SPFx dev ignoring this is playing checkers in a chess game.

Strict Mode, DevTools, and Type Safety – Expose Your Weak Links
React 18’s Strict Mode is more than a debug feature—it’s a truth serum for sloppy code. When enabled, it intentionally double-invokes certain functions and effects to highlight side effects, memory leaks, and unsafe lifecycles. Most SPFx developers disable it immediately because it “spams the console.” That’s the coward’s move. You’re afraid to face your mistakes.
I run Strict Mode on every SPFx project. Every memory leak caught early saves headaches later. Every unclean effect prevented saves CPU cycles and user frustration. Pair that with TypeScript’s type enforcement and React DevTools profiling, and you’re not just coding—you’re auditing, refactoring, and hardening your web parts. Anything less is negligent.
The life lesson here is brutal but simple: discipline exposes weakness. If you’re not testing, profiling, and pushing your code to reveal flaws, you’re hiding from your own incompetence. Your character is the kernel; your habits are the state. If you panic under load, everything around you suffers. Apply Strict Mode and type safety to React in SPFx, and you build a muscle: resilience, foresight, and accountability.
Technically, the combination of Strict Mode and TypeScript ensures that your SPFx web parts are robust against async pitfalls, improper effect cleanup, and improper prop usage. Every refactor becomes a proof point that you can maintain complex systems with minimal technical debt. If you ignore it, you’re shipping spaghetti and calling it gourmet.

Conclusion: No-Excuses Mastery – Ship Like a Pro or Ship Like a Junior
Here’s the brutal truth: React 18 in SPFx is a weapon. Ignore concurrent rendering, batching, Suspense, lazy loading, Strict Mode, or TypeScript, and you’re not a developer—you’re a liability. You can’t pretend old habits will carry you; they won’t. Your web parts crash, your users suffer, and your reputation bleeds like memory leaks in an unoptimized component.
Refactor. Optimize. Audit. Stop shipping half-baked web parts. Embrace concurrent rendering to stabilize your core, implement Suspense and lazy loading to manage complexity, and enforce strict checks and type safety to expose weaknesses before they hit production. Every module you clean, every effect you guard, every render you optimize reflects the man you are—or refuse to be.
No more excuses. Ship like a professional, or get left behind. Your SPFx web parts are a reflection of your discipline, attention to detail, and mastery of modern frameworks. Treat them with respect. Treat your craft with respect. And for anyone serious about leveling up, subscribe, comment, or reach out—but only if you’re ready to put in the work. Half measures are for hobbyists.
Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

D. Bryan King

Sources
Disclaimer:
The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:
#automaticBatching #componentOptimization #concurrentRendering #effectCleanup #lazyLoading #lazyLoadedComponents #modernReact #modernWebDevelopment #React18 #React18Features #React18Hooks #React18InSPFx #ReactArchitecture #reactBestPractices #ReactCodeHygiene #ReactCoding #ReactComponentDesign #ReactConcurrency #ReactDebugging #ReactDevTools #ReactErrorBoundaries #ReactHooks #ReactLazy #ReactLearning #ReactMemoryLeaks #ReactOptimizationTechniques #ReactPerformance #ReactProfiler #ReactRefactor #ReactStateManagement #ReactStrictMode #ReactSuspenseAPI #ReactTips #ReactTraining #ReactUpdates #resilientWebParts #scalableSPFx #SharePointDevelopment #SharePointFramework #SharePointOptimization #SharePointPerformance #SharePointTips #SPFx #SPFxBestPractices #SPFxCoding #SPFxDeveloperGuide #SPFxDevelopment #SPFxLifecycle #SPFxLifecycleManagement #SPFxPerformance #SPFxTips #SPFxTutorials #SPFxWebParts #StrictMode #Suspense #TypeScript #TypeScriptSPFx #webPartArchitecture #webPartOptimization #webPartPerformance
#automaticbatching #componentoptimization #concurrentrendering #effectcleanup #lazyloading #lazyloadedcomponents
Bryan King @[email protected] · 2026-02-16 · 12:30 UTC
The 3 React Upgrades SPFx Devs Are Ignoring (And Why Your Web Parts Are Leaking Performance)

1,402 words, 7 minutes read time.
Let’s cut the fluff: if your SPFx web parts feel sluggish, your state management is spaghetti, or your page crashes under moderate load, it’s because you’re not playing with React the way it’s meant to be played in 2026. The latest version of SPFx ships with React 18 support, but most devs treat it like yesterday’s framework, dragging legacy habits into modern code. I’ve seen it countless times: web parts patched with workarounds, effects firing endlessly, unoptimized re-renders eating CPU cycles, and junior devs praying that no one notices. The hard truth? If you can’t adapt to React’s new features, your code is dying on the vine, and so is your professional credibility.
This isn’t a gentle nudge. I’m here to break down the three React upgrades SPFx developers ignore at their own peril, why they matter technically, and how they mirror discipline—or the lack thereof—in your professional and personal life. First, we tackle the core of modern React: Concurrent Rendering and Automatic Batching.

Concurrent Rendering and Automatic Batching – Your Web Parts’ Backbone
When React 18 dropped concurrent rendering and automatic batching, it wasn’t a luxury—it was a lifeline. Most SPFx devs never adjust their components for this. They cling to class components with componentDidMount hacks or use hooks incorrectly, leaving effects firing multiple times, state updates queuing chaotically, and memory leaks piling up. In SPFx, where your web part is a node on the page with other parts loading simultaneously, this isn’t minor—it’s the difference between a smooth user experience and a browser meltdown.
I’ve refactored dozens of enterprise SPFx solutions. If your useEffect calls aren’t guarded, or you don’t understand how React batches state updates automatically now, you’re wasting render cycles and bleeding performance. Imagine deploying a web part that triggers three API calls per keystroke in a search box because you didn’t wrap state changes in proper batching logic. That’s a professional facepalm waiting to happen.
This is also about integrity. Your components are the kernel of your web part. If they panic, the whole page goes down. Every unguarded effect, every missed cleanup is like leaving a socket exposed: it’s dangerous, messy, and shows laziness. Learning concurrent rendering and embracing automatic batching isn’t optional; it’s the same principle you apply in life when you keep promises, manage your commitments, and clean up after yourself. Half measures don’t cut it in code or character.
From a pure technical perspective, understand that concurrent rendering allows React to interrupt long-running renders, prioritizing urgent updates and keeping the UI responsive. Automatic batching merges multiple state updates into a single render, reducing unnecessary DOM recalculations. In SPFx web parts, where you might be calling the SharePoint REST API or Microsoft Graph, this translates into fewer wasted renders, less flicker, and a page that doesn’t tank when multiple web parts fire simultaneously. It’s subtle, but anyone ignoring this is coding in yesterday’s world.
The takeaway is simple: refactor your legacy components, embrace hooks fully, and make React 18 work for you, not against you. Stop treating batching as magic and understand the lifecycle implications. Every clean render, every optimized state transition, is a reflection of the discipline you either bring or fail to bring to your work.
Suspense, Lazy Loading, and Code Splitting – Stop Shipping Monoliths
If you’re still bundling every component into a single SPFx web part, congratulations—you’re shipping a monolith nobody wants to wait for. React 18’s Suspense, combined with lazy loading, is your ticket to scalable, maintainable, and performant web parts. Yet most devs ignore it. They either don’t understand it or they fear breaking things, so they cling to the “just load everything upfront” mindset. That’s cowardice, plain and simple.
Suspense lets React pause rendering until a component or data is ready. Lazy loading defers non-critical components, shaving precious milliseconds off initial load time. In SPFx, where your web part might pull data from multiple lists, libraries, or Microsoft Graph endpoints, ignoring this is a performance crime. I’ve watched junior developers bake everything into bundle.js, resulting in 3MB downloads for a single web part. Users hate that. Management hates that. And your reputation? Tanking.
Implementing Suspense properly isn’t just technical. It forces discipline in planning component structure, dependencies, and render order. Every lazy-loaded component you ship cleanly mirrors your ability to compartmentalize and manage complexity in real life. A man who leaves tasks half-done, who tries to juggle everything without order, is coding like he lives: chaotic, inefficient, and fragile. You want clean SPFx web parts? Start thinking like a disciplined architect.
Technically, wrapping your web parts with Suspense and splitting components using React.lazy() reduces initial payload and allows React to prioritize urgent renders. Combined with proper error boundaries, you’re not just optimizing performance—you’re creating a resilient system. Lazy-loading non-critical components is like building load-bearing walls before the decorative trim: prioritize stability, then polish. Any SPFx dev ignoring this is playing checkers in a chess game.

Strict Mode, DevTools, and Type Safety – Expose Your Weak Links
React 18’s Strict Mode is more than a debug feature—it’s a truth serum for sloppy code. When enabled, it intentionally double-invokes certain functions and effects to highlight side effects, memory leaks, and unsafe lifecycles. Most SPFx developers disable it immediately because it “spams the console.” That’s the coward’s move. You’re afraid to face your mistakes.
I run Strict Mode on every SPFx project. Every memory leak caught early saves headaches later. Every unclean effect prevented saves CPU cycles and user frustration. Pair that with TypeScript’s type enforcement and React DevTools profiling, and you’re not just coding—you’re auditing, refactoring, and hardening your web parts. Anything less is negligent.
The life lesson here is brutal but simple: discipline exposes weakness. If you’re not testing, profiling, and pushing your code to reveal flaws, you’re hiding from your own incompetence. Your character is the kernel; your habits are the state. If you panic under load, everything around you suffers. Apply Strict Mode and type safety to React in SPFx, and you build a muscle: resilience, foresight, and accountability.
Technically, the combination of Strict Mode and TypeScript ensures that your SPFx web parts are robust against async pitfalls, improper effect cleanup, and improper prop usage. Every refactor becomes a proof point that you can maintain complex systems with minimal technical debt. If you ignore it, you’re shipping spaghetti and calling it gourmet.

Conclusion: No-Excuses Mastery – Ship Like a Pro or Ship Like a Junior
Here’s the brutal truth: React 18 in SPFx is a weapon. Ignore concurrent rendering, batching, Suspense, lazy loading, Strict Mode, or TypeScript, and you’re not a developer—you’re a liability. You can’t pretend old habits will carry you; they won’t. Your web parts crash, your users suffer, and your reputation bleeds like memory leaks in an unoptimized component.
Refactor. Optimize. Audit. Stop shipping half-baked web parts. Embrace concurrent rendering to stabilize your core, implement Suspense and lazy loading to manage complexity, and enforce strict checks and type safety to expose weaknesses before they hit production. Every module you clean, every effect you guard, every render you optimize reflects the man you are—or refuse to be.
No more excuses. Ship like a professional, or get left behind. Your SPFx web parts are a reflection of your discipline, attention to detail, and mastery of modern frameworks. Treat them with respect. Treat your craft with respect. And for anyone serious about leveling up, subscribe, comment, or reach out—but only if you’re ready to put in the work. Half measures are for hobbyists.
Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

D. Bryan King

Sources
Disclaimer:
The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:
#automaticBatching #componentOptimization #concurrentRendering #effectCleanup #lazyLoading #lazyLoadedComponents #modernReact #modernWebDevelopment #React18 #React18Features #React18Hooks #React18InSPFx #ReactArchitecture #reactBestPractices #ReactCodeHygiene #ReactCoding #ReactComponentDesign #ReactConcurrency #ReactDebugging #ReactDevTools #ReactErrorBoundaries #ReactHooks #ReactLazy #ReactLearning #ReactMemoryLeaks #ReactOptimizationTechniques #ReactPerformance #ReactProfiler #ReactRefactor #ReactStateManagement #ReactStrictMode #ReactSuspenseAPI #ReactTips #ReactTraining #ReactUpdates #resilientWebParts #scalableSPFx #SharePointDevelopment #SharePointFramework #SharePointOptimization #SharePointPerformance #SharePointTips #SPFx #SPFxBestPractices #SPFxCoding #SPFxDeveloperGuide #SPFxDevelopment #SPFxLifecycle #SPFxLifecycleManagement #SPFxPerformance #SPFxTips #SPFxTutorials #SPFxWebParts #StrictMode #Suspense #TypeScript #TypeScriptSPFx #webPartArchitecture #webPartOptimization #webPartPerformance
#automaticbatching #componentoptimization #concurrentrendering #effectcleanup #lazyloading #lazyloadedcomponents
Bryan King @[email protected] · 2026-02-16 · 12:30 UTC
The 3 React Upgrades SPFx Devs Are Ignoring (And Why Your Web Parts Are Leaking Performance)

1,402 words, 7 minutes read time.
Let’s cut the fluff: if your SPFx web parts feel sluggish, your state management is spaghetti, or your page crashes under moderate load, it’s because you’re not playing with React the way it’s meant to be played in 2026. The latest version of SPFx ships with React 18 support, but most devs treat it like yesterday’s framework, dragging legacy habits into modern code. I’ve seen it countless times: web parts patched with workarounds, effects firing endlessly, unoptimized re-renders eating CPU cycles, and junior devs praying that no one notices. The hard truth? If you can’t adapt to React’s new features, your code is dying on the vine, and so is your professional credibility.
This isn’t a gentle nudge. I’m here to break down the three React upgrades SPFx developers ignore at their own peril, why they matter technically, and how they mirror discipline—or the lack thereof—in your professional and personal life. First, we tackle the core of modern React: Concurrent Rendering and Automatic Batching.

Concurrent Rendering and Automatic Batching – Your Web Parts’ Backbone
When React 18 dropped concurrent rendering and automatic batching, it wasn’t a luxury—it was a lifeline. Most SPFx devs never adjust their components for this. They cling to class components with componentDidMount hacks or use hooks incorrectly, leaving effects firing multiple times, state updates queuing chaotically, and memory leaks piling up. In SPFx, where your web part is a node on the page with other parts loading simultaneously, this isn’t minor—it’s the difference between a smooth user experience and a browser meltdown.
I’ve refactored dozens of enterprise SPFx solutions. If your useEffect calls aren’t guarded, or you don’t understand how React batches state updates automatically now, you’re wasting render cycles and bleeding performance. Imagine deploying a web part that triggers three API calls per keystroke in a search box because you didn’t wrap state changes in proper batching logic. That’s a professional facepalm waiting to happen.
This is also about integrity. Your components are the kernel of your web part. If they panic, the whole page goes down. Every unguarded effect, every missed cleanup is like leaving a socket exposed: it’s dangerous, messy, and shows laziness. Learning concurrent rendering and embracing automatic batching isn’t optional; it’s the same principle you apply in life when you keep promises, manage your commitments, and clean up after yourself. Half measures don’t cut it in code or character.
From a pure technical perspective, understand that concurrent rendering allows React to interrupt long-running renders, prioritizing urgent updates and keeping the UI responsive. Automatic batching merges multiple state updates into a single render, reducing unnecessary DOM recalculations. In SPFx web parts, where you might be calling the SharePoint REST API or Microsoft Graph, this translates into fewer wasted renders, less flicker, and a page that doesn’t tank when multiple web parts fire simultaneously. It’s subtle, but anyone ignoring this is coding in yesterday’s world.
The takeaway is simple: refactor your legacy components, embrace hooks fully, and make React 18 work for you, not against you. Stop treating batching as magic and understand the lifecycle implications. Every clean render, every optimized state transition, is a reflection of the discipline you either bring or fail to bring to your work.
Suspense, Lazy Loading, and Code Splitting – Stop Shipping Monoliths
If you’re still bundling every component into a single SPFx web part, congratulations—you’re shipping a monolith nobody wants to wait for. React 18’s Suspense, combined with lazy loading, is your ticket to scalable, maintainable, and performant web parts. Yet most devs ignore it. They either don’t understand it or they fear breaking things, so they cling to the “just load everything upfront” mindset. That’s cowardice, plain and simple.
Suspense lets React pause rendering until a component or data is ready. Lazy loading defers non-critical components, shaving precious milliseconds off initial load time. In SPFx, where your web part might pull data from multiple lists, libraries, or Microsoft Graph endpoints, ignoring this is a performance crime. I’ve watched junior developers bake everything into bundle.js, resulting in 3MB downloads for a single web part. Users hate that. Management hates that. And your reputation? Tanking.
Implementing Suspense properly isn’t just technical. It forces discipline in planning component structure, dependencies, and render order. Every lazy-loaded component you ship cleanly mirrors your ability to compartmentalize and manage complexity in real life. A man who leaves tasks half-done, who tries to juggle everything without order, is coding like he lives: chaotic, inefficient, and fragile. You want clean SPFx web parts? Start thinking like a disciplined architect.
Technically, wrapping your web parts with Suspense and splitting components using React.lazy() reduces initial payload and allows React to prioritize urgent renders. Combined with proper error boundaries, you’re not just optimizing performance—you’re creating a resilient system. Lazy-loading non-critical components is like building load-bearing walls before the decorative trim: prioritize stability, then polish. Any SPFx dev ignoring this is playing checkers in a chess game.

Strict Mode, DevTools, and Type Safety – Expose Your Weak Links
React 18’s Strict Mode is more than a debug feature—it’s a truth serum for sloppy code. When enabled, it intentionally double-invokes certain functions and effects to highlight side effects, memory leaks, and unsafe lifecycles. Most SPFx developers disable it immediately because it “spams the console.” That’s the coward’s move. You’re afraid to face your mistakes.
I run Strict Mode on every SPFx project. Every memory leak caught early saves headaches later. Every unclean effect prevented saves CPU cycles and user frustration. Pair that with TypeScript’s type enforcement and React DevTools profiling, and you’re not just coding—you’re auditing, refactoring, and hardening your web parts. Anything less is negligent.
The life lesson here is brutal but simple: discipline exposes weakness. If you’re not testing, profiling, and pushing your code to reveal flaws, you’re hiding from your own incompetence. Your character is the kernel; your habits are the state. If you panic under load, everything around you suffers. Apply Strict Mode and type safety to React in SPFx, and you build a muscle: resilience, foresight, and accountability.
Technically, the combination of Strict Mode and TypeScript ensures that your SPFx web parts are robust against async pitfalls, improper effect cleanup, and improper prop usage. Every refactor becomes a proof point that you can maintain complex systems with minimal technical debt. If you ignore it, you’re shipping spaghetti and calling it gourmet.

Conclusion: No-Excuses Mastery – Ship Like a Pro or Ship Like a Junior
Here’s the brutal truth: React 18 in SPFx is a weapon. Ignore concurrent rendering, batching, Suspense, lazy loading, Strict Mode, or TypeScript, and you’re not a developer—you’re a liability. You can’t pretend old habits will carry you; they won’t. Your web parts crash, your users suffer, and your reputation bleeds like memory leaks in an unoptimized component.
Refactor. Optimize. Audit. Stop shipping half-baked web parts. Embrace concurrent rendering to stabilize your core, implement Suspense and lazy loading to manage complexity, and enforce strict checks and type safety to expose weaknesses before they hit production. Every module you clean, every effect you guard, every render you optimize reflects the man you are—or refuse to be.
No more excuses. Ship like a professional, or get left behind. Your SPFx web parts are a reflection of your discipline, attention to detail, and mastery of modern frameworks. Treat them with respect. Treat your craft with respect. And for anyone serious about leveling up, subscribe, comment, or reach out—but only if you’re ready to put in the work. Half measures are for hobbyists.
Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

D. Bryan King

Sources
Disclaimer:
The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:
#automaticBatching #componentOptimization #concurrentRendering #effectCleanup #lazyLoading #lazyLoadedComponents #modernReact #modernWebDevelopment #React18 #React18Features #React18Hooks #React18InSPFx #ReactArchitecture #reactBestPractices #ReactCodeHygiene #ReactCoding #ReactComponentDesign #ReactConcurrency #ReactDebugging #ReactDevTools #ReactErrorBoundaries #ReactHooks #ReactLazy #ReactLearning #ReactMemoryLeaks #ReactOptimizationTechniques #ReactPerformance #ReactProfiler #ReactRefactor #ReactStateManagement #ReactStrictMode #ReactSuspenseAPI #ReactTips #ReactTraining #ReactUpdates #resilientWebParts #scalableSPFx #SharePointDevelopment #SharePointFramework #SharePointOptimization #SharePointPerformance #SharePointTips #SPFx #SPFxBestPractices #SPFxCoding #SPFxDeveloperGuide #SPFxDevelopment #SPFxLifecycle #SPFxLifecycleManagement #SPFxPerformance #SPFxTips #SPFxTutorials #SPFxWebParts #StrictMode #Suspense #TypeScript #TypeScriptSPFx #webPartArchitecture #webPartOptimization #webPartPerformance
#automaticbatching #componentoptimization #concurrentrendering #effectcleanup #lazyloading #lazyloadedcomponents
Bryan King @[email protected] · 2026-02-16 · 12:30 UTC
The 3 React Upgrades SPFx Devs Are Ignoring (And Why Your Web Parts Are Leaking Performance)

1,402 words, 7 minutes read time.
Let’s cut the fluff: if your SPFx web parts feel sluggish, your state management is spaghetti, or your page crashes under moderate load, it’s because you’re not playing with React the way it’s meant to be played in 2026. The latest version of SPFx ships with React 18 support, but most devs treat it like yesterday’s framework, dragging legacy habits into modern code. I’ve seen it countless times: web parts patched with workarounds, effects firing endlessly, unoptimized re-renders eating CPU cycles, and junior devs praying that no one notices. The hard truth? If you can’t adapt to React’s new features, your code is dying on the vine, and so is your professional credibility.
This isn’t a gentle nudge. I’m here to break down the three React upgrades SPFx developers ignore at their own peril, why they matter technically, and how they mirror discipline—or the lack thereof—in your professional and personal life. First, we tackle the core of modern React: Concurrent Rendering and Automatic Batching.

Concurrent Rendering and Automatic Batching – Your Web Parts’ Backbone
When React 18 dropped concurrent rendering and automatic batching, it wasn’t a luxury—it was a lifeline. Most SPFx devs never adjust their components for this. They cling to class components with componentDidMount hacks or use hooks incorrectly, leaving effects firing multiple times, state updates queuing chaotically, and memory leaks piling up. In SPFx, where your web part is a node on the page with other parts loading simultaneously, this isn’t minor—it’s the difference between a smooth user experience and a browser meltdown.
I’ve refactored dozens of enterprise SPFx solutions. If your useEffect calls aren’t guarded, or you don’t understand how React batches state updates automatically now, you’re wasting render cycles and bleeding performance. Imagine deploying a web part that triggers three API calls per keystroke in a search box because you didn’t wrap state changes in proper batching logic. That’s a professional facepalm waiting to happen.
This is also about integrity. Your components are the kernel of your web part. If they panic, the whole page goes down. Every unguarded effect, every missed cleanup is like leaving a socket exposed: it’s dangerous, messy, and shows laziness. Learning concurrent rendering and embracing automatic batching isn’t optional; it’s the same principle you apply in life when you keep promises, manage your commitments, and clean up after yourself. Half measures don’t cut it in code or character.
From a pure technical perspective, understand that concurrent rendering allows React to interrupt long-running renders, prioritizing urgent updates and keeping the UI responsive. Automatic batching merges multiple state updates into a single render, reducing unnecessary DOM recalculations. In SPFx web parts, where you might be calling the SharePoint REST API or Microsoft Graph, this translates into fewer wasted renders, less flicker, and a page that doesn’t tank when multiple web parts fire simultaneously. It’s subtle, but anyone ignoring this is coding in yesterday’s world.
The takeaway is simple: refactor your legacy components, embrace hooks fully, and make React 18 work for you, not against you. Stop treating batching as magic and understand the lifecycle implications. Every clean render, every optimized state transition, is a reflection of the discipline you either bring or fail to bring to your work.
Suspense, Lazy Loading, and Code Splitting – Stop Shipping Monoliths
If you’re still bundling every component into a single SPFx web part, congratulations—you’re shipping a monolith nobody wants to wait for. React 18’s Suspense, combined with lazy loading, is your ticket to scalable, maintainable, and performant web parts. Yet most devs ignore it. They either don’t understand it or they fear breaking things, so they cling to the “just load everything upfront” mindset. That’s cowardice, plain and simple.
Suspense lets React pause rendering until a component or data is ready. Lazy loading defers non-critical components, shaving precious milliseconds off initial load time. In SPFx, where your web part might pull data from multiple lists, libraries, or Microsoft Graph endpoints, ignoring this is a performance crime. I’ve watched junior developers bake everything into bundle.js, resulting in 3MB downloads for a single web part. Users hate that. Management hates that. And your reputation? Tanking.
Implementing Suspense properly isn’t just technical. It forces discipline in planning component structure, dependencies, and render order. Every lazy-loaded component you ship cleanly mirrors your ability to compartmentalize and manage complexity in real life. A man who leaves tasks half-done, who tries to juggle everything without order, is coding like he lives: chaotic, inefficient, and fragile. You want clean SPFx web parts? Start thinking like a disciplined architect.
Technically, wrapping your web parts with Suspense and splitting components using React.lazy() reduces initial payload and allows React to prioritize urgent renders. Combined with proper error boundaries, you’re not just optimizing performance—you’re creating a resilient system. Lazy-loading non-critical components is like building load-bearing walls before the decorative trim: prioritize stability, then polish. Any SPFx dev ignoring this is playing checkers in a chess game.

Strict Mode, DevTools, and Type Safety – Expose Your Weak Links
React 18’s Strict Mode is more than a debug feature—it’s a truth serum for sloppy code. When enabled, it intentionally double-invokes certain functions and effects to highlight side effects, memory leaks, and unsafe lifecycles. Most SPFx developers disable it immediately because it “spams the console.” That’s the coward’s move. You’re afraid to face your mistakes.
I run Strict Mode on every SPFx project. Every memory leak caught early saves headaches later. Every unclean effect prevented saves CPU cycles and user frustration. Pair that with TypeScript’s type enforcement and React DevTools profiling, and you’re not just coding—you’re auditing, refactoring, and hardening your web parts. Anything less is negligent.
The life lesson here is brutal but simple: discipline exposes weakness. If you’re not testing, profiling, and pushing your code to reveal flaws, you’re hiding from your own incompetence. Your character is the kernel; your habits are the state. If you panic under load, everything around you suffers. Apply Strict Mode and type safety to React in SPFx, and you build a muscle: resilience, foresight, and accountability.
Technically, the combination of Strict Mode and TypeScript ensures that your SPFx web parts are robust against async pitfalls, improper effect cleanup, and improper prop usage. Every refactor becomes a proof point that you can maintain complex systems with minimal technical debt. If you ignore it, you’re shipping spaghetti and calling it gourmet.

Conclusion: No-Excuses Mastery – Ship Like a Pro or Ship Like a Junior
Here’s the brutal truth: React 18 in SPFx is a weapon. Ignore concurrent rendering, batching, Suspense, lazy loading, Strict Mode, or TypeScript, and you’re not a developer—you’re a liability. You can’t pretend old habits will carry you; they won’t. Your web parts crash, your users suffer, and your reputation bleeds like memory leaks in an unoptimized component.
Refactor. Optimize. Audit. Stop shipping half-baked web parts. Embrace concurrent rendering to stabilize your core, implement Suspense and lazy loading to manage complexity, and enforce strict checks and type safety to expose weaknesses before they hit production. Every module you clean, every effect you guard, every render you optimize reflects the man you are—or refuse to be.
No more excuses. Ship like a professional, or get left behind. Your SPFx web parts are a reflection of your discipline, attention to detail, and mastery of modern frameworks. Treat them with respect. Treat your craft with respect. And for anyone serious about leveling up, subscribe, comment, or reach out—but only if you’re ready to put in the work. Half measures are for hobbyists.
Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

D. Bryan King

Sources
Disclaimer:
The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:
#automaticBatching #componentOptimization #concurrentRendering #effectCleanup #lazyLoading #lazyLoadedComponents #modernReact #modernWebDevelopment #React18 #React18Features #React18Hooks #React18InSPFx #ReactArchitecture #reactBestPractices #ReactCodeHygiene #ReactCoding #ReactComponentDesign #ReactConcurrency #ReactDebugging #ReactDevTools #ReactErrorBoundaries #ReactHooks #ReactLazy #ReactLearning #ReactMemoryLeaks #ReactOptimizationTechniques #ReactPerformance #ReactProfiler #ReactRefactor #ReactStateManagement #ReactStrictMode #ReactSuspenseAPI #ReactTips #ReactTraining #ReactUpdates #resilientWebParts #scalableSPFx #SharePointDevelopment #SharePointFramework #SharePointOptimization #SharePointPerformance #SharePointTips #SPFx #SPFxBestPractices #SPFxCoding #SPFxDeveloperGuide #SPFxDevelopment #SPFxLifecycle #SPFxLifecycleManagement #SPFxPerformance #SPFxTips #SPFxTutorials #SPFxWebParts #StrictMode #Suspense #TypeScript #TypeScriptSPFx #webPartArchitecture #webPartOptimization #webPartPerformance
#webpartperformance #webpartoptimization #webpartarchitecture #typescriptspfx #typescript #suspense
Bryan King @[email protected] · 2026-02-16 · 12:30 UTC
The 3 React Upgrades SPFx Devs Are Ignoring (And Why Your Web Parts Are Leaking Performance)

1,402 words, 7 minutes read time.
Let’s cut the fluff: if your SPFx web parts feel sluggish, your state management is spaghetti, or your page crashes under moderate load, it’s because you’re not playing with React the way it’s meant to be played in 2026. The latest version of SPFx ships with React 18 support, but most devs treat it like yesterday’s framework, dragging legacy habits into modern code. I’ve seen it countless times: web parts patched with workarounds, effects firing endlessly, unoptimized re-renders eating CPU cycles, and junior devs praying that no one notices. The hard truth? If you can’t adapt to React’s new features, your code is dying on the vine, and so is your professional credibility.
This isn’t a gentle nudge. I’m here to break down the three React upgrades SPFx developers ignore at their own peril, why they matter technically, and how they mirror discipline—or the lack thereof—in your professional and personal life. First, we tackle the core of modern React: Concurrent Rendering and Automatic Batching.

Concurrent Rendering and Automatic Batching – Your Web Parts’ Backbone
When React 18 dropped concurrent rendering and automatic batching, it wasn’t a luxury—it was a lifeline. Most SPFx devs never adjust their components for this. They cling to class components with componentDidMount hacks or use hooks incorrectly, leaving effects firing multiple times, state updates queuing chaotically, and memory leaks piling up. In SPFx, where your web part is a node on the page with other parts loading simultaneously, this isn’t minor—it’s the difference between a smooth user experience and a browser meltdown.
I’ve refactored dozens of enterprise SPFx solutions. If your useEffect calls aren’t guarded, or you don’t understand how React batches state updates automatically now, you’re wasting render cycles and bleeding performance. Imagine deploying a web part that triggers three API calls per keystroke in a search box because you didn’t wrap state changes in proper batching logic. That’s a professional facepalm waiting to happen.
This is also about integrity. Your components are the kernel of your web part. If they panic, the whole page goes down. Every unguarded effect, every missed cleanup is like leaving a socket exposed: it’s dangerous, messy, and shows laziness. Learning concurrent rendering and embracing automatic batching isn’t optional; it’s the same principle you apply in life when you keep promises, manage your commitments, and clean up after yourself. Half measures don’t cut it in code or character.
From a pure technical perspective, understand that concurrent rendering allows React to interrupt long-running renders, prioritizing urgent updates and keeping the UI responsive. Automatic batching merges multiple state updates into a single render, reducing unnecessary DOM recalculations. In SPFx web parts, where you might be calling the SharePoint REST API or Microsoft Graph, this translates into fewer wasted renders, less flicker, and a page that doesn’t tank when multiple web parts fire simultaneously. It’s subtle, but anyone ignoring this is coding in yesterday’s world.
The takeaway is simple: refactor your legacy components, embrace hooks fully, and make React 18 work for you, not against you. Stop treating batching as magic and understand the lifecycle implications. Every clean render, every optimized state transition, is a reflection of the discipline you either bring or fail to bring to your work.
Suspense, Lazy Loading, and Code Splitting – Stop Shipping Monoliths
If you’re still bundling every component into a single SPFx web part, congratulations—you’re shipping a monolith nobody wants to wait for. React 18’s Suspense, combined with lazy loading, is your ticket to scalable, maintainable, and performant web parts. Yet most devs ignore it. They either don’t understand it or they fear breaking things, so they cling to the “just load everything upfront” mindset. That’s cowardice, plain and simple.
Suspense lets React pause rendering until a component or data is ready. Lazy loading defers non-critical components, shaving precious milliseconds off initial load time. In SPFx, where your web part might pull data from multiple lists, libraries, or Microsoft Graph endpoints, ignoring this is a performance crime. I’ve watched junior developers bake everything into bundle.js, resulting in 3MB downloads for a single web part. Users hate that. Management hates that. And your reputation? Tanking.
Implementing Suspense properly isn’t just technical. It forces discipline in planning component structure, dependencies, and render order. Every lazy-loaded component you ship cleanly mirrors your ability to compartmentalize and manage complexity in real life. A man who leaves tasks half-done, who tries to juggle everything without order, is coding like he lives: chaotic, inefficient, and fragile. You want clean SPFx web parts? Start thinking like a disciplined architect.
Technically, wrapping your web parts with Suspense and splitting components using React.lazy() reduces initial payload and allows React to prioritize urgent renders. Combined with proper error boundaries, you’re not just optimizing performance—you’re creating a resilient system. Lazy-loading non-critical components is like building load-bearing walls before the decorative trim: prioritize stability, then polish. Any SPFx dev ignoring this is playing checkers in a chess game.

Strict Mode, DevTools, and Type Safety – Expose Your Weak Links
React 18’s Strict Mode is more than a debug feature—it’s a truth serum for sloppy code. When enabled, it intentionally double-invokes certain functions and effects to highlight side effects, memory leaks, and unsafe lifecycles. Most SPFx developers disable it immediately because it “spams the console.” That’s the coward’s move. You’re afraid to face your mistakes.
I run Strict Mode on every SPFx project. Every memory leak caught early saves headaches later. Every unclean effect prevented saves CPU cycles and user frustration. Pair that with TypeScript’s type enforcement and React DevTools profiling, and you’re not just coding—you’re auditing, refactoring, and hardening your web parts. Anything less is negligent.
The life lesson here is brutal but simple: discipline exposes weakness. If you’re not testing, profiling, and pushing your code to reveal flaws, you’re hiding from your own incompetence. Your character is the kernel; your habits are the state. If you panic under load, everything around you suffers. Apply Strict Mode and type safety to React in SPFx, and you build a muscle: resilience, foresight, and accountability.
Technically, the combination of Strict Mode and TypeScript ensures that your SPFx web parts are robust against async pitfalls, improper effect cleanup, and improper prop usage. Every refactor becomes a proof point that you can maintain complex systems with minimal technical debt. If you ignore it, you’re shipping spaghetti and calling it gourmet.

Conclusion: No-Excuses Mastery – Ship Like a Pro or Ship Like a Junior
Here’s the brutal truth: React 18 in SPFx is a weapon. Ignore concurrent rendering, batching, Suspense, lazy loading, Strict Mode, or TypeScript, and you’re not a developer—you’re a liability. You can’t pretend old habits will carry you; they won’t. Your web parts crash, your users suffer, and your reputation bleeds like memory leaks in an unoptimized component.
Refactor. Optimize. Audit. Stop shipping half-baked web parts. Embrace concurrent rendering to stabilize your core, implement Suspense and lazy loading to manage complexity, and enforce strict checks and type safety to expose weaknesses before they hit production. Every module you clean, every effect you guard, every render you optimize reflects the man you are—or refuse to be.
No more excuses. Ship like a professional, or get left behind. Your SPFx web parts are a reflection of your discipline, attention to detail, and mastery of modern frameworks. Treat them with respect. Treat your craft with respect. And for anyone serious about leveling up, subscribe, comment, or reach out—but only if you’re ready to put in the work. Half measures are for hobbyists.
Call to Action

If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a comment sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

D. Bryan King

Sources
Disclaimer:
The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:
#automaticBatching #componentOptimization #concurrentRendering #effectCleanup #lazyLoading #lazyLoadedComponents #modernReact #modernWebDevelopment #React18 #React18Features #React18Hooks #React18InSPFx #ReactArchitecture #reactBestPractices #ReactCodeHygiene #ReactCoding #ReactComponentDesign #ReactConcurrency #ReactDebugging #ReactDevTools #ReactErrorBoundaries #ReactHooks #ReactLazy #ReactLearning #ReactMemoryLeaks #ReactOptimizationTechniques #ReactPerformance #ReactProfiler #ReactRefactor #ReactStateManagement #ReactStrictMode #ReactSuspenseAPI #ReactTips #ReactTraining #ReactUpdates #resilientWebParts #scalableSPFx #SharePointDevelopment #SharePointFramework #SharePointOptimization #SharePointPerformance #SharePointTips #SPFx #SPFxBestPractices #SPFxCoding #SPFxDeveloperGuide #SPFxDevelopment #SPFxLifecycle #SPFxLifecycleManagement #SPFxPerformance #SPFxTips #SPFxTutorials #SPFxWebParts #StrictMode #Suspense #TypeScript #TypeScriptSPFx #webPartArchitecture #webPartOptimization #webPartPerformance
#automaticbatching #componentoptimization #concurrentrendering #effectcleanup #lazyloading #lazyloadedcomponents
DrWeb @[email protected] · 2026-02-12 · 18:31 UTC

Something big is happening in AI — and most people will be blindsided – Fortune
Matt Shumer, co-founder and CEO of OthersideAI. courtesy of OthersideAI
Commentary Entrepreneurship
Something big is happening in AI — and most people will be blindsided
By Matt Shumer, February 11, 2026, 9:22 AM ET
Matt Shumer is the co-founder and CEO of OthersideAI, an applied AI company building the most advanced autocomplete tools in the world, powered by large-scale AI systems like GPT-3. OthersideAI is the company behind HyperWrite, the leading AI autocomplete Chrome extension for consumers. Previously, while in high school, Matt founded Visos, a startup developing next-generation Virtual Reality software designed for medical use, and FURI, a company aiming to disrupt the sporting goods industry by creating high-performance products and selling them for fair prices.
Think back to February 2020.
A few people were talking about a virus spreading overseas. If someone told you they were stockpiling toilet paper you would have thought they’d been spending too much time on a weird corner of the internet. Then, over the course of about three weeks, the entire world changed.
I think we’re in the “this seems overblown” phase of something much, much bigger than Covid.
I’ve spent six years building an AI startup and investing in the space. I live in this world. And I’m writing this for the people in my life who don’t. I keep giving them the polite, cocktail-party version. Because the honest version sounds like I’ve lost my mind. But the gap between what I’ve been saying and what is actually happening has gotten far too big. The people I care about deserve to hear what is coming, even if it sounds crazy.
I should be clear about something up front: even though I work in AI, I have almost no influence over what’s about to happen, and neither does the vast majority of the industry. The future is being shaped by a remarkably small number of people: a few hundred researchers at a handful of companies… OpenAI, Anthropic, Google, DeepMind, and a few others.
Most of us who work in AI are building on top of foundations we didn’t lay. We’re watching this unfold the same as you… we just happen to be close enough to feel the ground shake first.
But it’s time now. Not in an “eventually we should talk about this” way. In a “this is happening right now and I need you to understand it” way.
I know this is real because it happened to me first
Here’s the thing nobody outside of tech quite understands yet: we’re not making predictions. We’re telling you what already occurred in our own jobs, and warning you that you’re next.
For years, AI had been improving steadily. Then in 2025, new techniques for building these models unlocked a much faster pace of progress. This year, something clicked. Not like a light switch… more like the moment you realize the water has been rising around you and is now at your chest.
I am no longer needed for the actual technical work of my job. I describe what I want built, in plain English, and it just… appears. Not a rough draft I need to fix. The finished thing. I tell the AI what I want, walk away from my computer for four hours, and come back to find the work done. Done well, done better than I would have done it myself, with no corrections needed. A couple of months ago, I was going back and forth with the AI, guiding it, making edits. Now I just describe the outcome and leave.
Let me give you an example so you can understand what this actually looks like in practice. I’ll tell the AI: “I want to build this app. Here’s what it should do, here’s roughly what it should look like. Figure out the user flow, the design, all of it.” And it does. It writes tens of thousands of lines of code. Then, and this is the part that would have been unthinkable a year ago, it opens the app itself. It clicks through the buttons. It tests the features. It uses the app the way a person would. If it doesn’t like how something looks or feels, it goes back and changes it, on its own. It iterates, like a developer would, fixing and refining until it’s satisfied. Only once it has decided the app meets its own standards does it come back to me and say: “It’s ready for you to test.” And when I test it, it’s usually perfect.
I’m not exaggerating. That is what my Monday looked like this week.
I’ve always been early to adopt AI tools. But the last few months have shocked me. These new AI models aren’t incremental improvements. This is a different thing entirely.
The experience that tech workers have had over the past year, of watching AI go from “helpful tool” to “does my job better than I do”, is the experience everyone else is about to have. Law, finance, medicine, accounting, consulting, writing, design, analysis, customer service. Not in 10 years. The people building these systems say one to five years. Some say less. The market was spooked enough this month that it wiped out $1 trillion worth of software value in just a week. And given what I’ve seen in just the last couple of months, I see more disruption, and soon.
“But I tried AI and it wasn’t that good”
If you tried ChatGPT in 2023 or early 2024 and thought “this makes stuff up” or “this isn’t that impressive”, you were right. Those early versions were genuinely limited. They hallucinated. They confidently said things that were nonsense.
The models available today are unrecognizable from what existed even six months ago. The debate about whether AI is “really getting better” or “hitting a wall” — which has been going on for over a year — is over. It’s done. Anyone still making that argument either hasn’t used the current models, has an incentive to downplay what’s happening, or is evaluating based on an experience from 2024 that is no longer relevant. I don’t say that to be dismissive. I say it because the gap between public perception and current reality is now enormous, and that gap is dangerous… because it’s preventing people from preparing.
Part of the problem is that most people are using the free version of AI tools. The free version is over a year behind what paying users have access to. Judging AI based on free-tier ChatGPT is like evaluating the state of smartphones by using a flip phone. The people paying for the best tools, and actually using them daily for real work, know what’s coming.
I think of my friend, who’s a lawyer. I keep telling him to try using AI at his firm, and he keeps finding reasons it won’t work. And I get it. But I’ve had partners at major law firms reach out to me for advice, because they’ve tried the current versions and they see where this is going. One of them, the managing partner at a large firm, spends hours every day using AI. He told me it’s like having a team of associates available instantly. He’s not using it because it’s a toy. He’s using it because it works. And he told me something that stuck with me: every couple of months, it gets significantly more capable for his work. He said if it stays on this trajectory, he expects it’ll be able to do most of what he does before long… and he’s a managing partner with decades of experience. He’s not panicking. But he’s paying very close attention.
Think about what that means for your work.
What this means for your job
I’m going to be direct with you because I think you deserve honesty more than comfort.
Dario Amodei, who is probably the most safety-focused CEO in the AI industry, has publicly predicted that AI will eliminate 50% of entry-level white-collar jobs within one to five years. And many people in the industry think he’s being conservative. Given what the latest models can do, the capability for massive disruption could be here by the end of this year. It’ll take some time to ripple through the economy, but the underlying ability is arriving now.
This is different from every previous wave of automation, and I need you to understand why. AI isn’t replacing one specific skill. It’s a general substitute for cognitive work. It gets better at everything simultaneously. When factories automated, a displaced worker could retrain as an office worker. When the internet disrupted retail, workers moved into logistics or services. But AI doesn’t leave a convenient gap to move into. Whatever you retrain for, it’s improving at that too.
I think the honest answer is that nothing that can be done on a computer is safe in the medium term. If your job happens on a screen (if the core of what you do is reading, writing, analyzing, deciding, communicating through a keyboard) then AI is coming for significant parts of it. The timeline isn’t “someday.” It’s already started.
Eventually, robots will handle physical work too. They’re not quite there yet. But “not quite there yet” in AI terms has a way of becoming “here” faster than anyone expects.
What you should actually do
I’m not writing this to make you feel helpless. I’m writing this because I think the single biggest advantage you can have right now is simply being early. Early to understand it. Early to use it. Early to adapt.
Editor’s Note: Read more online. This is a general AI-supportive post by Matt. And there are many others similar “heads up” posts about AI right now. Keep an eye out for further posts on the AI changes coming. Whatever your views, I recommend keeping up with AI over your own work, or job, society changes, regulations, world impacts, and more. –DrWeb
Continue/Read Original Article Here: Something big is happening in AI — and most people will be blindsided | Fortune
Tags: AI, AI Future, artificial intelligence, Big Changes, Fortune, Heads Up, Jobs Changing, Matt Shumer, Newer Models, OthersideAI, Rapid Developments in AI, Social Impacts, Technology
#AI #AIFuture #artificialIntelligence #BigChanges #Fortune #HeadsUp #JobsChanging #MattShumer #NewerModels #OthersideAI #RapidDevelopmentsInAI #SocialImpacts #Technology

#ai #aifuture #artificialintelligence #bigchanges #fortune #headsup
DrWeb @[email protected] · 2026-02-12 · 18:31 UTC

Something big is happening in AI — and most people will be blindsided – Fortune
Matt Shumer, co-founder and CEO of OthersideAI. courtesy of OthersideAI
Commentary Entrepreneurship
Something big is happening in AI — and most people will be blindsided
By Matt Shumer, February 11, 2026, 9:22 AM ET
Matt Shumer is the co-founder and CEO of OthersideAI, an applied AI company building the most advanced autocomplete tools in the world, powered by large-scale AI systems like GPT-3. OthersideAI is the company behind HyperWrite, the leading AI autocomplete Chrome extension for consumers. Previously, while in high school, Matt founded Visos, a startup developing next-generation Virtual Reality software designed for medical use, and FURI, a company aiming to disrupt the sporting goods industry by creating high-performance products and selling them for fair prices.
Think back to February 2020.
A few people were talking about a virus spreading overseas. If someone told you they were stockpiling toilet paper you would have thought they’d been spending too much time on a weird corner of the internet. Then, over the course of about three weeks, the entire world changed.
I think we’re in the “this seems overblown” phase of something much, much bigger than Covid.
I’ve spent six years building an AI startup and investing in the space. I live in this world. And I’m writing this for the people in my life who don’t. I keep giving them the polite, cocktail-party version. Because the honest version sounds like I’ve lost my mind. But the gap between what I’ve been saying and what is actually happening has gotten far too big. The people I care about deserve to hear what is coming, even if it sounds crazy.
I should be clear about something up front: even though I work in AI, I have almost no influence over what’s about to happen, and neither does the vast majority of the industry. The future is being shaped by a remarkably small number of people: a few hundred researchers at a handful of companies… OpenAI, Anthropic, Google, DeepMind, and a few others.
Most of us who work in AI are building on top of foundations we didn’t lay. We’re watching this unfold the same as you… we just happen to be close enough to feel the ground shake first.
But it’s time now. Not in an “eventually we should talk about this” way. In a “this is happening right now and I need you to understand it” way.
I know this is real because it happened to me first
Here’s the thing nobody outside of tech quite understands yet: we’re not making predictions. We’re telling you what already occurred in our own jobs, and warning you that you’re next.
For years, AI had been improving steadily. Then in 2025, new techniques for building these models unlocked a much faster pace of progress. This year, something clicked. Not like a light switch… more like the moment you realize the water has been rising around you and is now at your chest.
I am no longer needed for the actual technical work of my job. I describe what I want built, in plain English, and it just… appears. Not a rough draft I need to fix. The finished thing. I tell the AI what I want, walk away from my computer for four hours, and come back to find the work done. Done well, done better than I would have done it myself, with no corrections needed. A couple of months ago, I was going back and forth with the AI, guiding it, making edits. Now I just describe the outcome and leave.
Let me give you an example so you can understand what this actually looks like in practice. I’ll tell the AI: “I want to build this app. Here’s what it should do, here’s roughly what it should look like. Figure out the user flow, the design, all of it.” And it does. It writes tens of thousands of lines of code. Then, and this is the part that would have been unthinkable a year ago, it opens the app itself. It clicks through the buttons. It tests the features. It uses the app the way a person would. If it doesn’t like how something looks or feels, it goes back and changes it, on its own. It iterates, like a developer would, fixing and refining until it’s satisfied. Only once it has decided the app meets its own standards does it come back to me and say: “It’s ready for you to test.” And when I test it, it’s usually perfect.
I’m not exaggerating. That is what my Monday looked like this week.
I’ve always been early to adopt AI tools. But the last few months have shocked me. These new AI models aren’t incremental improvements. This is a different thing entirely.
The experience that tech workers have had over the past year, of watching AI go from “helpful tool” to “does my job better than I do”, is the experience everyone else is about to have. Law, finance, medicine, accounting, consulting, writing, design, analysis, customer service. Not in 10 years. The people building these systems say one to five years. Some say less. The market was spooked enough this month that it wiped out $1 trillion worth of software value in just a week. And given what I’ve seen in just the last couple of months, I see more disruption, and soon.
“But I tried AI and it wasn’t that good”
If you tried ChatGPT in 2023 or early 2024 and thought “this makes stuff up” or “this isn’t that impressive”, you were right. Those early versions were genuinely limited. They hallucinated. They confidently said things that were nonsense.
The models available today are unrecognizable from what existed even six months ago. The debate about whether AI is “really getting better” or “hitting a wall” — which has been going on for over a year — is over. It’s done. Anyone still making that argument either hasn’t used the current models, has an incentive to downplay what’s happening, or is evaluating based on an experience from 2024 that is no longer relevant. I don’t say that to be dismissive. I say it because the gap between public perception and current reality is now enormous, and that gap is dangerous… because it’s preventing people from preparing.
Part of the problem is that most people are using the free version of AI tools. The free version is over a year behind what paying users have access to. Judging AI based on free-tier ChatGPT is like evaluating the state of smartphones by using a flip phone. The people paying for the best tools, and actually using them daily for real work, know what’s coming.
I think of my friend, who’s a lawyer. I keep telling him to try using AI at his firm, and he keeps finding reasons it won’t work. And I get it. But I’ve had partners at major law firms reach out to me for advice, because they’ve tried the current versions and they see where this is going. One of them, the managing partner at a large firm, spends hours every day using AI. He told me it’s like having a team of associates available instantly. He’s not using it because it’s a toy. He’s using it because it works. And he told me something that stuck with me: every couple of months, it gets significantly more capable for his work. He said if it stays on this trajectory, he expects it’ll be able to do most of what he does before long… and he’s a managing partner with decades of experience. He’s not panicking. But he’s paying very close attention.
Think about what that means for your work.
What this means for your job
I’m going to be direct with you because I think you deserve honesty more than comfort.
Dario Amodei, who is probably the most safety-focused CEO in the AI industry, has publicly predicted that AI will eliminate 50% of entry-level white-collar jobs within one to five years. And many people in the industry think he’s being conservative. Given what the latest models can do, the capability for massive disruption could be here by the end of this year. It’ll take some time to ripple through the economy, but the underlying ability is arriving now.
This is different from every previous wave of automation, and I need you to understand why. AI isn’t replacing one specific skill. It’s a general substitute for cognitive work. It gets better at everything simultaneously. When factories automated, a displaced worker could retrain as an office worker. When the internet disrupted retail, workers moved into logistics or services. But AI doesn’t leave a convenient gap to move into. Whatever you retrain for, it’s improving at that too.
I think the honest answer is that nothing that can be done on a computer is safe in the medium term. If your job happens on a screen (if the core of what you do is reading, writing, analyzing, deciding, communicating through a keyboard) then AI is coming for significant parts of it. The timeline isn’t “someday.” It’s already started.
Eventually, robots will handle physical work too. They’re not quite there yet. But “not quite there yet” in AI terms has a way of becoming “here” faster than anyone expects.
What you should actually do
I’m not writing this to make you feel helpless. I’m writing this because I think the single biggest advantage you can have right now is simply being early. Early to understand it. Early to use it. Early to adapt.
Editor’s Note: Read more online. This is a general AI-supportive post by Matt. And there are many others similar “heads up” posts about AI right now. Keep an eye out for further posts on the AI changes coming. Whatever your views, I recommend keeping up with AI over your own work, or job, society changes, regulations, world impacts, and more. –DrWeb
Continue/Read Original Article Here: Something big is happening in AI — and most people will be blindsided | Fortune
Tags: AI, AI Future, artificial intelligence, Big Changes, Fortune, Heads Up, Jobs Changing, Matt Shumer, Newer Models, OthersideAI, Rapid Developments in AI, Social Impacts, Technology
#AI #AIFuture #artificialIntelligence #BigChanges #Fortune #HeadsUp #JobsChanging #MattShumer #NewerModels #OthersideAI #RapidDevelopmentsInAI #SocialImpacts #Technology

#ai #aifuture #artificialintelligence #bigchanges #fortune #headsup
DrWeb @[email protected] · 2026-02-12 · 18:31 UTC

Something big is happening in AI — and most people will be blindsided – Fortune
Matt Shumer, co-founder and CEO of OthersideAI. courtesy of OthersideAI
Commentary Entrepreneurship
Something big is happening in AI — and most people will be blindsided
By Matt Shumer, February 11, 2026, 9:22 AM ET
Matt Shumer is the co-founder and CEO of OthersideAI, an applied AI company building the most advanced autocomplete tools in the world, powered by large-scale AI systems like GPT-3. OthersideAI is the company behind HyperWrite, the leading AI autocomplete Chrome extension for consumers. Previously, while in high school, Matt founded Visos, a startup developing next-generation Virtual Reality software designed for medical use, and FURI, a company aiming to disrupt the sporting goods industry by creating high-performance products and selling them for fair prices.
Think back to February 2020.
A few people were talking about a virus spreading overseas. If someone told you they were stockpiling toilet paper you would have thought they’d been spending too much time on a weird corner of the internet. Then, over the course of about three weeks, the entire world changed.
I think we’re in the “this seems overblown” phase of something much, much bigger than Covid.
I’ve spent six years building an AI startup and investing in the space. I live in this world. And I’m writing this for the people in my life who don’t. I keep giving them the polite, cocktail-party version. Because the honest version sounds like I’ve lost my mind. But the gap between what I’ve been saying and what is actually happening has gotten far too big. The people I care about deserve to hear what is coming, even if it sounds crazy.
I should be clear about something up front: even though I work in AI, I have almost no influence over what’s about to happen, and neither does the vast majority of the industry. The future is being shaped by a remarkably small number of people: a few hundred researchers at a handful of companies… OpenAI, Anthropic, Google, DeepMind, and a few others.
Most of us who work in AI are building on top of foundations we didn’t lay. We’re watching this unfold the same as you… we just happen to be close enough to feel the ground shake first.
But it’s time now. Not in an “eventually we should talk about this” way. In a “this is happening right now and I need you to understand it” way.
I know this is real because it happened to me first
Here’s the thing nobody outside of tech quite understands yet: we’re not making predictions. We’re telling you what already occurred in our own jobs, and warning you that you’re next.
For years, AI had been improving steadily. Then in 2025, new techniques for building these models unlocked a much faster pace of progress. This year, something clicked. Not like a light switch… more like the moment you realize the water has been rising around you and is now at your chest.
I am no longer needed for the actual technical work of my job. I describe what I want built, in plain English, and it just… appears. Not a rough draft I need to fix. The finished thing. I tell the AI what I want, walk away from my computer for four hours, and come back to find the work done. Done well, done better than I would have done it myself, with no corrections needed. A couple of months ago, I was going back and forth with the AI, guiding it, making edits. Now I just describe the outcome and leave.
Let me give you an example so you can understand what this actually looks like in practice. I’ll tell the AI: “I want to build this app. Here’s what it should do, here’s roughly what it should look like. Figure out the user flow, the design, all of it.” And it does. It writes tens of thousands of lines of code. Then, and this is the part that would have been unthinkable a year ago, it opens the app itself. It clicks through the buttons. It tests the features. It uses the app the way a person would. If it doesn’t like how something looks or feels, it goes back and changes it, on its own. It iterates, like a developer would, fixing and refining until it’s satisfied. Only once it has decided the app meets its own standards does it come back to me and say: “It’s ready for you to test.” And when I test it, it’s usually perfect.
I’m not exaggerating. That is what my Monday looked like this week.
I’ve always been early to adopt AI tools. But the last few months have shocked me. These new AI models aren’t incremental improvements. This is a different thing entirely.
The experience that tech workers have had over the past year, of watching AI go from “helpful tool” to “does my job better than I do”, is the experience everyone else is about to have. Law, finance, medicine, accounting, consulting, writing, design, analysis, customer service. Not in 10 years. The people building these systems say one to five years. Some say less. The market was spooked enough this month that it wiped out $1 trillion worth of software value in just a week. And given what I’ve seen in just the last couple of months, I see more disruption, and soon.
“But I tried AI and it wasn’t that good”
If you tried ChatGPT in 2023 or early 2024 and thought “this makes stuff up” or “this isn’t that impressive”, you were right. Those early versions were genuinely limited. They hallucinated. They confidently said things that were nonsense.
The models available today are unrecognizable from what existed even six months ago. The debate about whether AI is “really getting better” or “hitting a wall” — which has been going on for over a year — is over. It’s done. Anyone still making that argument either hasn’t used the current models, has an incentive to downplay what’s happening, or is evaluating based on an experience from 2024 that is no longer relevant. I don’t say that to be dismissive. I say it because the gap between public perception and current reality is now enormous, and that gap is dangerous… because it’s preventing people from preparing.
Part of the problem is that most people are using the free version of AI tools. The free version is over a year behind what paying users have access to. Judging AI based on free-tier ChatGPT is like evaluating the state of smartphones by using a flip phone. The people paying for the best tools, and actually using them daily for real work, know what’s coming.
I think of my friend, who’s a lawyer. I keep telling him to try using AI at his firm, and he keeps finding reasons it won’t work. And I get it. But I’ve had partners at major law firms reach out to me for advice, because they’ve tried the current versions and they see where this is going. One of them, the managing partner at a large firm, spends hours every day using AI. He told me it’s like having a team of associates available instantly. He’s not using it because it’s a toy. He’s using it because it works. And he told me something that stuck with me: every couple of months, it gets significantly more capable for his work. He said if it stays on this trajectory, he expects it’ll be able to do most of what he does before long… and he’s a managing partner with decades of experience. He’s not panicking. But he’s paying very close attention.
Think about what that means for your work.
What this means for your job
I’m going to be direct with you because I think you deserve honesty more than comfort.
Dario Amodei, who is probably the most safety-focused CEO in the AI industry, has publicly predicted that AI will eliminate 50% of entry-level white-collar jobs within one to five years. And many people in the industry think he’s being conservative. Given what the latest models can do, the capability for massive disruption could be here by the end of this year. It’ll take some time to ripple through the economy, but the underlying ability is arriving now.
This is different from every previous wave of automation, and I need you to understand why. AI isn’t replacing one specific skill. It’s a general substitute for cognitive work. It gets better at everything simultaneously. When factories automated, a displaced worker could retrain as an office worker. When the internet disrupted retail, workers moved into logistics or services. But AI doesn’t leave a convenient gap to move into. Whatever you retrain for, it’s improving at that too.
I think the honest answer is that nothing that can be done on a computer is safe in the medium term. If your job happens on a screen (if the core of what you do is reading, writing, analyzing, deciding, communicating through a keyboard) then AI is coming for significant parts of it. The timeline isn’t “someday.” It’s already started.
Eventually, robots will handle physical work too. They’re not quite there yet. But “not quite there yet” in AI terms has a way of becoming “here” faster than anyone expects.
What you should actually do
I’m not writing this to make you feel helpless. I’m writing this because I think the single biggest advantage you can have right now is simply being early. Early to understand it. Early to use it. Early to adapt.
Editor’s Note: Read more online. This is a general AI-supportive post by Matt. And there are many others similar “heads up” posts about AI right now. Keep an eye out for further posts on the AI changes coming. Whatever your views, I recommend keeping up with AI over your own work, or job, society changes, regulations, world impacts, and more. –DrWeb
Continue/Read Original Article Here: Something big is happening in AI — and most people will be blindsided | Fortune
Tags: AI, AI Future, artificial intelligence, Big Changes, Fortune, Heads Up, Jobs Changing, Matt Shumer, Newer Models, OthersideAI, Rapid Developments in AI, Social Impacts, Technology
#AI #AIFuture #artificialIntelligence #BigChanges #Fortune #HeadsUp #JobsChanging #MattShumer #NewerModels #OthersideAI #RapidDevelopmentsInAI #SocialImpacts #Technology

#technology #socialimpacts #rapiddevelopmentsinai #othersideai #newermodels #mattshumer
DrWeb @[email protected] · 2026-02-12 · 18:31 UTC

Something big is happening in AI — and most people will be blindsided – Fortune
Matt Shumer, co-founder and CEO of OthersideAI. courtesy of OthersideAI
Commentary Entrepreneurship
Something big is happening in AI — and most people will be blindsided
By Matt Shumer, February 11, 2026, 9:22 AM ET
Matt Shumer is the co-founder and CEO of OthersideAI, an applied AI company building the most advanced autocomplete tools in the world, powered by large-scale AI systems like GPT-3. OthersideAI is the company behind HyperWrite, the leading AI autocomplete Chrome extension for consumers. Previously, while in high school, Matt founded Visos, a startup developing next-generation Virtual Reality software designed for medical use, and FURI, a company aiming to disrupt the sporting goods industry by creating high-performance products and selling them for fair prices.
Think back to February 2020.
A few people were talking about a virus spreading overseas. If someone told you they were stockpiling toilet paper you would have thought they’d been spending too much time on a weird corner of the internet. Then, over the course of about three weeks, the entire world changed.
I think we’re in the “this seems overblown” phase of something much, much bigger than Covid.
I’ve spent six years building an AI startup and investing in the space. I live in this world. And I’m writing this for the people in my life who don’t. I keep giving them the polite, cocktail-party version. Because the honest version sounds like I’ve lost my mind. But the gap between what I’ve been saying and what is actually happening has gotten far too big. The people I care about deserve to hear what is coming, even if it sounds crazy.
I should be clear about something up front: even though I work in AI, I have almost no influence over what’s about to happen, and neither does the vast majority of the industry. The future is being shaped by a remarkably small number of people: a few hundred researchers at a handful of companies… OpenAI, Anthropic, Google, DeepMind, and a few others.
Most of us who work in AI are building on top of foundations we didn’t lay. We’re watching this unfold the same as you… we just happen to be close enough to feel the ground shake first.
But it’s time now. Not in an “eventually we should talk about this” way. In a “this is happening right now and I need you to understand it” way.
I know this is real because it happened to me first
Here’s the thing nobody outside of tech quite understands yet: we’re not making predictions. We’re telling you what already occurred in our own jobs, and warning you that you’re next.
For years, AI had been improving steadily. Then in 2025, new techniques for building these models unlocked a much faster pace of progress. This year, something clicked. Not like a light switch… more like the moment you realize the water has been rising around you and is now at your chest.
I am no longer needed for the actual technical work of my job. I describe what I want built, in plain English, and it just… appears. Not a rough draft I need to fix. The finished thing. I tell the AI what I want, walk away from my computer for four hours, and come back to find the work done. Done well, done better than I would have done it myself, with no corrections needed. A couple of months ago, I was going back and forth with the AI, guiding it, making edits. Now I just describe the outcome and leave.
Let me give you an example so you can understand what this actually looks like in practice. I’ll tell the AI: “I want to build this app. Here’s what it should do, here’s roughly what it should look like. Figure out the user flow, the design, all of it.” And it does. It writes tens of thousands of lines of code. Then, and this is the part that would have been unthinkable a year ago, it opens the app itself. It clicks through the buttons. It tests the features. It uses the app the way a person would. If it doesn’t like how something looks or feels, it goes back and changes it, on its own. It iterates, like a developer would, fixing and refining until it’s satisfied. Only once it has decided the app meets its own standards does it come back to me and say: “It’s ready for you to test.” And when I test it, it’s usually perfect.
I’m not exaggerating. That is what my Monday looked like this week.
I’ve always been early to adopt AI tools. But the last few months have shocked me. These new AI models aren’t incremental improvements. This is a different thing entirely.
The experience that tech workers have had over the past year, of watching AI go from “helpful tool” to “does my job better than I do”, is the experience everyone else is about to have. Law, finance, medicine, accounting, consulting, writing, design, analysis, customer service. Not in 10 years. The people building these systems say one to five years. Some say less. The market was spooked enough this month that it wiped out $1 trillion worth of software value in just a week. And given what I’ve seen in just the last couple of months, I see more disruption, and soon.
“But I tried AI and it wasn’t that good”
If you tried ChatGPT in 2023 or early 2024 and thought “this makes stuff up” or “this isn’t that impressive”, you were right. Those early versions were genuinely limited. They hallucinated. They confidently said things that were nonsense.
The models available today are unrecognizable from what existed even six months ago. The debate about whether AI is “really getting better” or “hitting a wall” — which has been going on for over a year — is over. It’s done. Anyone still making that argument either hasn’t used the current models, has an incentive to downplay what’s happening, or is evaluating based on an experience from 2024 that is no longer relevant. I don’t say that to be dismissive. I say it because the gap between public perception and current reality is now enormous, and that gap is dangerous… because it’s preventing people from preparing.
Part of the problem is that most people are using the free version of AI tools. The free version is over a year behind what paying users have access to. Judging AI based on free-tier ChatGPT is like evaluating the state of smartphones by using a flip phone. The people paying for the best tools, and actually using them daily for real work, know what’s coming.
I think of my friend, who’s a lawyer. I keep telling him to try using AI at his firm, and he keeps finding reasons it won’t work. And I get it. But I’ve had partners at major law firms reach out to me for advice, because they’ve tried the current versions and they see where this is going. One of them, the managing partner at a large firm, spends hours every day using AI. He told me it’s like having a team of associates available instantly. He’s not using it because it’s a toy. He’s using it because it works. And he told me something that stuck with me: every couple of months, it gets significantly more capable for his work. He said if it stays on this trajectory, he expects it’ll be able to do most of what he does before long… and he’s a managing partner with decades of experience. He’s not panicking. But he’s paying very close attention.
Think about what that means for your work.
What this means for your job
I’m going to be direct with you because I think you deserve honesty more than comfort.
Dario Amodei, who is probably the most safety-focused CEO in the AI industry, has publicly predicted that AI will eliminate 50% of entry-level white-collar jobs within one to five years. And many people in the industry think he’s being conservative. Given what the latest models can do, the capability for massive disruption could be here by the end of this year. It’ll take some time to ripple through the economy, but the underlying ability is arriving now.
This is different from every previous wave of automation, and I need you to understand why. AI isn’t replacing one specific skill. It’s a general substitute for cognitive work. It gets better at everything simultaneously. When factories automated, a displaced worker could retrain as an office worker. When the internet disrupted retail, workers moved into logistics or services. But AI doesn’t leave a convenient gap to move into. Whatever you retrain for, it’s improving at that too.
I think the honest answer is that nothing that can be done on a computer is safe in the medium term. If your job happens on a screen (if the core of what you do is reading, writing, analyzing, deciding, communicating through a keyboard) then AI is coming for significant parts of it. The timeline isn’t “someday.” It’s already started.
Eventually, robots will handle physical work too. They’re not quite there yet. But “not quite there yet” in AI terms has a way of becoming “here” faster than anyone expects.
What you should actually do
I’m not writing this to make you feel helpless. I’m writing this because I think the single biggest advantage you can have right now is simply being early. Early to understand it. Early to use it. Early to adapt.
Editor’s Note: Read more online. This is a general AI-supportive post by Matt. And there are many others similar “heads up” posts about AI right now. Keep an eye out for further posts on the AI changes coming. Whatever your views, I recommend keeping up with AI over your own work, or job, society changes, regulations, world impacts, and more. –DrWeb
Continue/Read Original Article Here: Something big is happening in AI — and most people will be blindsided | Fortune
Tags: AI, AI Future, artificial intelligence, Big Changes, Fortune, Heads Up, Jobs Changing, Matt Shumer, Newer Models, OthersideAI, Rapid Developments in AI, Social Impacts, Technology
#AI #AIFuture #artificialIntelligence #BigChanges #Fortune #HeadsUp #JobsChanging #MattShumer #NewerModels #OthersideAI #RapidDevelopmentsInAI #SocialImpacts #Technology

#ai #aifuture #artificialintelligence #bigchanges #fortune #headsup