No, most people don't cheat. The world would fall apart if they did.
In a lot of occupations the skills you learn in college are real and meaningful. If you don't have the skills, you can't do the job. You can't fake it 'till you make it if it's painfully obvious to your coworkers that you don't understand basic concepts.
When Chrome 1.0 came out in 2008, it only ran on Windows, and it couldn't do basic things like print or export to PDF, didn't have any accessibility, didn't work in RTL languages, and didn't have any graphics acceleration, among other limitations. Don't get me wrong, it was a marvelous piece of engineering - but it was extremely incomplete. By the time it was what we think of as a modern, complete browser, they had many hundreds of engineers working on it.
Also, you're comparing the number of engineers working on one product, to the number of engineers working at Shopify across their entire company today, which includes far more than just one app.
You're entitled to your opinion that Shopify is a poor app or that it's overengineered, but clearly it's not simple. That's just a fact. If it looks like a simple app to you, that's because you're not seeing most of it.
It's like looking at the YouTube mobile app as someone who watches videos and saying that the app frontend looks simple. You're only seeing 5% of the app. The other 95% is for video creators and advertisers, and it is decidedly NOT simple. I think that's the same here.
I agree with what you're saying that it's not exactly what we're seeing which makes it not as simple.
However, I've seen this play out in many a big companies where there's a big mess going on. Answer is always similar pointing to -> "clearly it's not simple" and that's kind of the whole point. They made it not simple. 3k ENGINEERS, my sweet dude. THREE THOUSAND. By any and all account that's half as much as current chrome team or in total if you account for open source contributors as well. If robot is to believed that's also a headcount of windows and macos core teams. What is even going on, I don't even..
Taxes, compliance, regulatory bodies, logistics multiplied by X countries X products has an amazing way to bog you down. If you have money and problems money solves (eg you could hire more people to do something) you do not have a problem (except for people on the internet making arguments from personal inexperience)
I think there is something like Parkinson's Law: "Work expands so as to fill the time available for its completion."
This is more like the engineering team scales to match your budget.
It is why successful companies, when starting out and getting to their defining project completion state have significantly less engineers then 10 years later when they are massively more successful.
The cost of having the engineers is nothing compared to the profits, so why not hire more so you can defend your position. Are 80% of them needed to keep the system going, I think Elon showed that you can prune most of them away and the system will keep humming along (ignoring some initial problems). The trouble is bureaucracy, lack of technical knowledge at the top, and the hazy difficulty of identifying what is needed is really difficult, and if you mess it up, you could ruin a billion dollar business to save a hundred million dollars in salaries.
That is the crux of it. You can't know who to cut, and even if you are really good at it, you will still create problems and create ill will. Elon was pretty successful, but it did have some momentary problems. If his negative cult of personality didn't get in the way, it would have been better off.
I certainly wouldn’t go anywhere near Twitter these days, but the question is how much of that is to do with engineering failures and how much is to do with the overall change of culture and moderation practices that Musk has introduced.
I get that, I truly do since I see it all and every day. We're talking engineering hands here though. Presumably programmers and infrastructure and SRE.
> If you have money and problems money solves (eg you could hire more people to do something) you do not have a problem
If you have money there's a greater chance that someone in that X by X matrix might see you as a juicy target to go after so your expensive handling of every item in that matrix needed to be better still.
Very much this. If you have 3000 engineers (and all the associated non-engineering roles that inevitably come with that) then you have guaranteed that no problem will ever be easy to solve. Possibly you might be able to solve some extremely difficult problems that you couldn’t solve with fewer engineers.
> When Chrome 1.0 came out in 2008, it only ran on Windows, and it couldn't do basic things like print or export to PDF, didn't have any accessibility, didn't work in RTL languages, and didn't have any graphics acceleration, among other limitations.
It also was reusing the WebKit browser engine, work on which started in the 20th century (as KHTML)
As to Shopify needing zillion of engineers: does their backend query seller APIs? If so, I expect many of their engineers work on keeping that working.
And Chrome doesn't even need to support millions (billions) of users on a single, coherent "system". There's no scaling, it's just people running it on their computers and phones.
I suspect the vast majority of Shopify engineers never touch the core Shopify experience, but work on the long tail of invisible things that are nevertheless considered important. I'm talking along the lines of "direct integration with bank X for UPI in India to save 0.3% on payment costs in scenario Y."
Most of the modern software tooling you have today wasn't available back then, from great IDE's to popular libraries, writing software in 2008 was a different beast compared to today.
Tja, besides LLMs I can't really see the major improvement todays IDEs and language combination brings over Eclipse+Java. Great docs, good autocomplete, good compiler feedback.
When Visual Studio (not VSCode) incorporated a time travel debugger, that felt like a major advance in an IDE. I don’t remember exactly when that was, but I think it was around 2013.
I am still a little stunned by the rapid adoption of VSCode over IntelliJ and the original Visual Studio. Maybe being free was the important part, but I still chafe at the idea that we should configure our tools using JSON instead of just, you know, buttons and checkboxes.
Of course, VSCode and its ilk are jam packed with AI stuff I don’t not want, so it is mostly back to a fancy text editor for me.
DevOps and infrastructure, Security. Internal tools is correct, but speed, video quality as well as sound seems so easy. Google is responsible for many compression algorithms and standards - byproducts so to say. And they are top notch.
I have insights into the matters, and a lot goes into behind the scene optimization. Some specialists in the pre-AI phase were tasked to do nothing else but optimize build tools but in the sense of tweaking every millisecond out of it. This guy saved Google Billions over the years.
Others work in compiler building etc.
There are a couple of hints in the books by Google engineers but I am regularily blown away during meetings what really highly inspiring things are there to discover as well as presented.
Another factor: Google is spread around the globe. Regulation, law. Believe me, having over a billion users per app is mindblowing.
And it is 24/7/365. And support. And research.
Google is a company I admire. Technical provess at its finest.
Rubbish. Most of the stuff you’re listing is handled by OS and frameworks themselves, you don’t need hundreds of SE to handle RTL or a11y. I work in one of those companies, most people just regurgitate existing shit into another form of shit and collect salary (not complaining, as I’m one of them, but let’s be honest).
The original Edge had to switch over to Chromium because it was hard to build a compliant accessible browser from scratch and this is Microsoft we are talking about.
More seriously, it not just about building a compliant web browser engine, it is about tracking the dominant browser engine which introduces their own "standards" along the way too.
Microsoft could have easily continued to invest in maintaining their browser engine, but it would have to be comparable to what Google is doing, and yet they'd always be perceived as "behind" due to non-dominant position they have.
I'd say strategically they do not want to invest in tech that's not winning (in marketshare), so when they are not dominant, they'll instead adopt and extend (not just web browsers, look at WSL too).
We live in a time now where libraries are free and plentiful and pretty good. It is easy to forget that this was not the case for the vast majority of time that computers have existed.
Chrome’s original design definitely predates our current rich ecosystem. Plus, V8 and Chrome’s performance profile are demanding enough that there would be a pretty high bar for those dependencies anyway.
Chrome was invented in 2008. Abseil[1] didn't exist publicly until 2017, derived partly from Chromium.
HarfBuzz wasn't ported to C++ until 2010. I don't know the entire constellation of libs Chrome would use if it was designed in C++ today, but I bet a lot of them didn't exist before Chrome or were even created partly as a downstream byproduct of Chromium.
In other ecosystems: if Chrome were designed in Rust in 2008, there would be no crates.io to pull from. There would be no NPM, since Node followed V8/Chrome's invention in 2009. Maven Central had ~50K packages in 2009[2], which was a lot back then. In 2026, Maven Central hosts over 3 million.
I think you've come from an npm world because c++ still doesn't have a great library ecosystem if thats what you mean.
> In other ecosystems: if Chrome were designed in Rust in 2008, there would be no crates.io to pull from. There would be no NPM, since Node followed V8/Chrome's invention in 2009. Maven Central had ~50K packages in 2009[2], which was a lot back then. In 2026, Maven Central hosts over 3 million.
Yeah, this is all web development stuff.... Doesn't apply to c++
A browser isn't drawing its content using OS frameworks, so A11Y is a major undertaking. Much more so because A11Y for web content specifically is a bit of a different beast than native widgets, and the amount of stuff you have on the web these days means that you have to pay a lot more attention to performance.
This is plain wrong. For a browser, a11y doesn't just get handled by the OS automatically. In general, claiming a11y is easy or will be done by someone else is bordering on evil.
This is based on my understanding from several pilots who have weighted in.
The cockpit voice recorder transcript has the copilot repeatedly saying "we're coming in too fast" but the pilot never clearly acknolwedges.
The copilot ought to have been more assertive and said "We need to go around. NOW."
The pilot shouldn't have needed that. He should have made the call himself, but even if he was unsure, once his copilot called that he should have done the right thing.
Neither of them will ever fly again. The only question now is if either of them will go to prison. There's already a civil wrongful death lawsuit against them.
I think that’s true when you compare to the average white collar professional who does a lot of writing: better at writing, not better at communicating.
But compared to the average adult? I think you forget just how bad at writing the average person is.
If you ask a non-programmer to install Claude Code, just installing it will be a challenge, then opening the shell and interacting with it. Things as simple as copying and pasting can present roadblocks if you've never used a shell before, and things intuitive to programmers like using up-arrow to go back to a previous prompt would never occur to someone in the field.
Claude Code seems so simple and natural of a UI to programmers, it's easy to forget how much it builds on.
Zoom out one step. The experiment should have been searching for "build website with AI", or "build website with <product name>", not "hey use this very specific UI to do something I know will fail"
(FWIW I think people betting their whole companies on AI are trusting shitty one-wish genie goblins, but the terrible irony is that anyone "technical" with years-old knowledge is talking about something else entirely in today's context)
Claude Cowork is the application aimed at non-developers that gives them a lot of the same functionality. My girlfriend uses it and has gotten quite far in producing her own software.
With Claude it's actually not that hard. I set up a system for a startup where devs used a full dev environment and non-devs could use the Claude web UI to open rougher PRs, and one of the non-devs asked me what was involved with getting a full dev environment set up, so Claude could iterate and he could test locally, which was faster than the "push to GitHub, use the Vercel/Supabase preview deployment" workflow he was using.
I gave him a link to Ghostty, a link to the claude code copy/paste pipe to bash thing, told him how to cd/ls/pwd into the folder he had locally from the GitHub app, and he was off to the races. I told him to type `claude` to open Claude Code in the terminal and gave him a prompt to use about being a non-dev getting his environment set up to the point of being able to pnpm dev and test, and Claude took it from there. The repo's readme had a setup section which it followed to install brew, asdf, pnpm, etc. With the GitHub MCP he's now opening PRs the same way devs do.
This feels like trying to rewrite history. Those of us who lived through that time know that it was real - Microsoft was extremely anti-Linux. That famous Ballmer quote wasn't taken out of context, it was one of many. Ballmer and Gates were vehemently anti-Linux for years, and Microsoft engaged in deliberate marketing campaigns to smear Linux. They saw it as real competition, and they fought dirty, as they did with all of their competitors.
Here are just a few examples I found of evidence in just a few minutes of searching:
The legal questions were always overblown. The concern Ballmer was raising was that if you incorporate a bit of GPL software into your own, then it could "infect" the rest of your code and force you to release more. But that's ridiculous because nobody is forcing you to incorporate GPL software into your own. There was no serious legal concern about simply using Linux - Microsoft was just trying to scare people.
Is Microsoft a different company today? Yes, in many ways. They're much better about open-source software, for sure.
I still think they're anticompetitive in many ways. Their marketing team still prefers to try to spread lies about their competition (e.g. Chrome) rather than promote their own product on its own merits.
Yess indeed. Additionally, one of the marketing campaigns (“Get the facts”) seemed deliberately arranged to interfere with the SCO vs IBM and SCO vs RedHat legal cases where SCO tried to claim they owned Linux. For people who weren’t around reading “groklaw” on a daily basis at the time this is a bit of a rabbit hole, so be warned https://en.wikipedia.org/wiki/SCO%E2%80%93Linux_disputes
My initial thought there is that you'd have an imbalance. Many token patterns would almost never come up with the assistant tag on them, for example words with typos in them.
In a lot of occupations the skills you learn in college are real and meaningful. If you don't have the skills, you can't do the job. You can't fake it 'till you make it if it's painfully obvious to your coworkers that you don't understand basic concepts.
reply