Jul 21, 2026 - How New Technology Changes Business Models

Whenever a new technology appears, almost everyone claims it will be “transformational.” Usually, that claim is too vague to be useful.

A company may adopt a technology, launch a feature, or improve a few internal processes, all of that without materially changing its business.

A more useful question is:

What fundamental constraint does the technology remove?

I use this question to classify the impact of new technologies on companies, products, and business models.

The framework

A new technology can affect a business model in five distinct ways.

Classification What constraint the technology removes
No Material Impact It removes no constraint that materially affects the business model
Existing Model Leverage It removes a constraint that limited the performance of an already viable model
Economic Enablement It removes a cost constraint that prevented a technically possible model from being viable
Technological Enablement It removes a capability constraint that made the model technically infeasible
Model Destruction It removes a constraint that an existing model depended on to create or capture value

1 - No Material Impact

The technology removes no fundamental constraint that materially affects the business model’s performance, differentiation, or viability.

The company may still use the technology to automate internal tasks, improve marketing output, or reduce minor operating costs.

Consider a restaurant using an LLM to draft job descriptions and marketing copy. The tool may be useful, but the restaurant still depends on locations, food, labor, customer traffic, and operational execution.

The technology improves activities around the business. It does not materially change the business itself.

2 - Existing Model Leverage

The business was already viable, and the technology removes a constraint that limited its scale, margins, productivity, differentiation, or monetization potential.

Rather than creating something fundamentally novel, the technology amplifies a model that already worked.

An established software product, for example, may use AI to automate part of an existing workflow. Customers complete the same job faster, the product becomes more valuable, and the company may charge more or serve more customers with the same resources.

The product can change substantially while the core business model remains intact.

This category is called leverage, not transformation, because the technology acts as a multiplier on an existing economic engine.

This can improve scale or market share, but the company still competes with established rivals in an existing market.

3 - Economic Enablement

The business was technically possible, but a cost or resource constraint prevented it from being economically viable at scale.

The economic equation changes through lower delivery costs, greater monetization potential, or both.

Personalized tutoring is a useful example.

One-to-one tutoring has always been possible, but it is expensive because each additional student requires additional human time. An AI-based tutor can provide continuous assistance at a much lower marginal cost.

The underlying capability and need are not new. What changes is the cost of delivering the service at scale.

The same pattern can apply to customer support, translation, legal assistance, research, design, and other services historically constrained by skilled labor.

If executed well, the company may expand its total addressable market by making the product or service available to a wider audience.

4 - Technological Enablement

The business was not practically possible because a required technical capability did not exist or was not sufficiently mature.

The technology creates a fundamentally new capability, rather than making an existing capability cheaper.

AI-based protein design is an example.

Companies such as EvolutionaryScale use generative models to reason across protein sequence, structure, and function, allowing scientists to design novel proteins with desired characteristics.

Traditional methods could analyze existing proteins or test variations through slow experimental cycles. They could not explore and generate entirely new biological designs with the same breadth and speed.

This goes beyond reducing research costs. It creates a new design capability around which new medicines, materials, and biological products may emerge.

Companies in this category may create entirely new markets and have the greatest disruptive potential.

5 - Model Destruction

The technology removes a constraint that an existing business model depended on to create or capture value, undermining its viability.

The technology may eliminate the scarcity, friction, or intermediary role that made the model viable.

Stock photography marketplaces, for example, depend on the scarcity of suitable images and on licensing access to large existing catalogs. Generative image models allow users to create customized images on demand, reducing the need to search, license, and adapt pre-existing content.

The companies do not necessarily disappear, but their existing business model loses viability unless they adapt.

Applying the framework

The classification depends on the unit of analysis. A company, product, business line, or internal process may fall into different categories.

A classification can also change over time. What begins as technological enablement may later become economic enablement or a standard source of leverage as the technology matures and becomes widely available.

The framework is not intended to predict winners. It is intended to force a more concrete question:

What wasn’t scalable, economically viable, or even possible before this technology existed?

The answer can help clarify how much a new technology may change a company’s business model and how strategically significant that shift could be.

Mar 18, 2026 - This blog is on the Small Web

I was browsing Hacker News yesterday and saw a post titled Kagi Small Web ranking high on the front page. Curiosity got the better of me, so I clicked through. I ended up spending some time there just jumping through random posts comprised of actually interesting stuff written by real people, not the usual SEO-optimized or AI “slop” we see everywhere now.

Then I did a bit of digging. It turns out, this blog is on that list too 🙂

What is this list?

I went over to their GitHub repository to see what was going on. As of today, the smallweb.txt file is comprised of 34,492 blogs and personal websites. It’s basically a very large, curated index of a (more?) “human” internet.

If you’re wondering how a site gets included, they have a specific set of rules:

  • Non-Commercial: No intrusive ads, paywalls, or heavy affiliate marketing.
  • Human-Centric: Absolutely no AI-generated or LLM “spam” content.
  • Technical: You must have a valid RSS or Atom feed.
  • Recent-ish: The blog needs at least one post in the last 12 months to stay in the index.
  • Personal: It favors personal diaries, niche technical deep-dives, and independent essays over corporate blogs or newsletters (Substack seems like a no-go).

Turns out, these criteria favor both better content and a better experience, exactly what I value.

Seven years of “Zero Maintenance”

I actually never submitted my blog to be included. It likely got picked up because I’ve been running this blog for seven years now, since 2019. I use Jekyll - don’t know if it’s still a thing, but it works.

The best part? Jekyll generates an RSS feed out of the box, which turned out to be one of the requirements for getting indexed by Kagi. I host everything on GitHub Pages, which I highly recommend. It’s free, requires zero maintenance time, and it’s surprisingly robust. It can handle a “Hacker News hug of death” without breaking a sweat whenever one of my posts accidentally hits the front page.

If you’ve been thinking about starting your own blog and you have some technical skills, you don’t need a complex setup / CMS. You could literally just clone my repo, restyle the layout, and set up your own domain on GitHub Pages for free.

Is the small web actually useful?

The original HN thread had some mixed feelings. A few people were underwhelmed by the current implementation, calling it “more like a curated blog ring than a discovery engine for the broader indie web.” Others were more optimistic, acknowledging that it’s a “good idea with a decent foundation.”

Personally, I just appreciate the small bit of recognition. In a world where every search result feels like it was written by a bot to sell me a mattress, it’s nice to be officially part of the “Small Web”, even more since I didn’t subscribe to be on the list myself.


Cheers! 🍻

Feb 13, 2026 - Craftsmanship coding and the five stages of grief

If you’ve been reading recent Hacker News threads, you’ve probably noticed a recurring tone: a recurring mourning for “craftsmanship” in software, for the clay-in-hands feeling of shaping code line by line.

Here’s some evidence:

If we borrow the “five stages of grief” as a metaphor, it feels like part of our industry is hovering around depression. Not because people are lacking resilience, but because the change is structural, not cosmetic. And structural change hits identity.

The next stage is acceptance.

Not “AI will code everything,” but “AI will code most of it”, and in many teams, it already does. But what does that mean? Simply put, software engineers will delegate most tasks to AI.

Here’s some truth about professional software:

Most developer time isn’t cathedral-building. It’s digital plumbing.

It’s reading code, changing code, moving data between systems, integrating APIs, handling edge cases, and keeping production stable.

That’s exactly where “agentic coding” is already meaningfully useful, because it’s fast at the repetitive, low-cognition parts, and when you can verify outputs/diffs (with your own eyes) cheaply. So why not use it in this context?

But bear in mind: most tasks don’t mean most value. So at a minimum treat agentic coding as a great tool to delegate lower-value tasks so that you can spend more time on higher-value work.

A practical ladder (most to least delegable)

Work type What agents are good at Your job stays
CRUD patterns, scaffolding, consistency schema/constraints, tests, review
Data plumbing / transfer adapters, ETL-ish glue, client code contracts, failure modes, monitoring
Simple transformations / integrations deterministic changes, refactors golden tests, invariants, change safety
Algorithms (well-specified) standard approaches + edge handling spec, complexity targets, property tests
Architecture exploring options, drafting designs making implicit constraints explicit
High-assurance software helping with review and test drafts ownership, compliance, zero-tolerance gates

There are many levels of delegation; it isn’t (and shouldn’t be) all-or-nothing. The less complex, less sensitive, and more reversible a task is, the more you can delegate the bulk of the work and let the agent drive. At the other end of the spectrum: complex or high-stakes work where failures are costly and reversals are painful, you keep your hands on the wheel.

What I’ve experienced in real projects

When the codebase has clear boundaries and coherent architecture, agents can be genuinely productive. When it’s spaghetti code, agents degrade quickly and produce mediocre output, because the system itself has weak signals.

Starting projects from scratch with agentic tools is also possible, but usually harder. You can make it work, but only if you provide much stronger specs. The broader and more ambiguous the task, the worse the output variance.

In other words, agents excel when scope is narrower, objectives are explicit, and review is cheap. The best use cases are tasks you’d feel comfortable coding yourself: you can write clear instructions, verify results, and do small adjustments before shipping.

That’s where the efficiency gains are real.

So, how to stay ahead in an agentic world

It isn’t about typing faster. It’s about moving craftsmanship upstream.

When agents write more of the code, the “handmade” part doesn’t disappear, it relocates. Craft becomes the ability to shape intent into constraints, turn ambiguity into decisions, and build systems where correctness is the default, not a happy accident.

Acceptance is not surrender. It’s admitting that most work is plumbing, and choosing to spend your human attention where it compounds: on higher-value, higher-stakes tasks.

So I say embrace the new paradigm agentic tools enable, where specification and intent are ever more important, low-complexity tasks delegated in bulk, and we can leverage our time to focus on higher-level challenges.