upvote
> If you're willing to buy that will be possible, then my guess is that it will occur in the form of small scale startups and actual mavericks rather than someone trying to run an existing business who will simply be too risk adverse to go all in when the time comes. Some guy in his basement is more likely to leverage AI "properly" to build an actual "AI-native" engineering org because that person won't have much to lose.

FWIW I think the company writing this post is one of those small scale startups. But that being said, you're not the only one who thinks this. A decent amount of VCs and funds think that only smaller, newer companies have the potential to be truly AI native because there's too much organizational inertia in an existing business in keeping its existing human processes and so only a newer company can achieve the true "scaling potential" or using AI to scale without human labor.

reply
I think this is all fair, but somewhat just semantics.

Most engineers are working in "normal" engineering orgs, but can feel the ground underneath them shifting, and companies believe that if they are caught flat footed, they will be out competed in the marketplace, so they are all trying to make sure they are adopting it at least in a way that lets them keep pace if not accelerate revenue.

If you are not impacted by economic incentives, you can continue to not care about this transitional state, but most people do.

reply
Are there any companies outside of the "AI shovels" business that make more money because of AI? Every time I ask someone why they went so hard on adopting AI, I hear the same story about the fear of losing the market share or becoming less competitive. Honest question, who is benefitting from all of this? The revenues at majority of companies seem flat at best. There is a growing concern about professionals getting deskilled, the job satisfaction is not improving, wages are stagnant. Mind-boggling that we are actively engaged and often push for this experiment that hurts our own profession. Cheering for our own demise.
reply
Yes.

Engineering’s job has always been to deal with hard technical challenges and apply new technologies.

Writing code was never the point. Predictably creating specific outcomes was. Wrangling AI in a way that multiplies productivity is the new job.

I won’t lie, it kind of sucks to be young right now, learn about punch cards and assembly in school, and then graduate into a market that’s moved on to Fortran. Sorry, I meant high level languages and AI. To say otherwise might imply the industry has seen a similar shift in the past where engineers made the exact same complaints practically verbatim.

Regardless, the reality is that college teaches very little about 90% of real engineering work anyway, and we still need to hire smart people for this new type of work.

reply
Not keen on outing myself by providing evidence, but I think we do generate more revenue by using AI. We launched new products with a small team and also optimized our outcome-pricing based product using AI several times. We also reduced costs by self-hosting more software.

But we're a tiny baby startup, so things like "spin up a new product with 1 engineer and get to $1m in revenue on it" or "reduce our IaaS bill by 300k/yr" is a meaningful contribution for us.

We're also building new AI-enabled software that was not possible before.

The big breakout hits have been AI Infra, but that makes sense from a technological perspective, Cisco made a lot of money well before Google did, but Cisco is not where the money concentrated in the end.

We don't really know what the equivalent of Google as an application business will be in the AI era, but there's a pretty big chance it's not actual Google. But Google still has to do it's best to hold on.

reply
I use AI compatibility as a metric when evaluating new software to add to my stack. If an AI agent isn’t able to do most of what you can do in the app by opening it, I prefer to look for other options.

Does not apply to everything though. E.G: I don’t care about AI support for my non work chats/email, since I’d rather not give it access.

reply
I'm struggling to see what any of this has to do with the parent comment. Maybe I'm having a brain fart.
reply
Reminds me of a few things, like being a meat proxy, as well as books like Company of One or Million Dollar One Person Business, and these were published before AI so right now we will see companies with only one founder and hundreds to thousands of AI agents. There already was that drug delivery company with the one founder but apparently a lot of their revenue was fraudulent. Still, it proves the point that it is possible.
reply
If most of their revenue was fraudulent it doesn’t prove anything. I’m not saying it’s proof against, but it’s definitely not proof for, either.
reply
I was misremembering, they were sued for spam laws, not for their revenue being fraudulent so it seems it's legitimate, making a billion in revenue with one person (and later on his brother who was hired), the rest is all AI.

https://www.nytimes.com/2026/04/02/technology/ai-billion-dol...

https://www.businessinsider.com/medvi-ai-weight-loss-million...

reply
IMO most modern engineering practices are cargo culture. I’m sure in 10 years we look back on today the same way we’d look back on the days before version control was common. We are in the emailing files around stage of development
reply
> differ to the AI

defer to the AI

reply
> I feel it falls well short of what a proper, forward-thinking "AI-native" engineering org would actually look like. That is, the author is presenting this as kind of a radical departure from normal engineering, but I just see it as normal engineering with more AI. I don't see that as AI-native.

A company which proclaims they are "AI-native" isn't actually interested in engineering, they are trying to ride the hype wave. Companies who care about engineering just... do engineering, and don't make a big deal out of whether they are chasing trends.

reply
AI native shouldn't imply idiotic. And designing your execution approach around a strategy based on a technology that doesn't exist is idiotic.
reply
The reality here is even more idiotic: someone criticizing a company for a terrible strategy they aren’t using that wouldn’t work if they did. According to the critic!
reply
deleted
reply
[flagged]
reply
If you follow this logic, we get to the true "AI-native" engineer which is ecstatically floating in a bath of dopamine-stimulating liquid, while AI reads their brain pattern and instantly builds everything they didn't even form a full thought about.

"If that sounds outlandish, that's because it is. We don't have such capable AI systems yet."

reply