1. Check frequency (between every single time and spot checks).
2. Check thoroughness (between antagonistic in-depth vs high level).
I'd agree that, if you're towards the end of both dimensions, the system is not generating any value.
A lot of folks are taking calculated (or I guess in some cases, reckless) risks right now, by moving one or both of those dimensions. I'd argue that in many situations, the risk is small and worth it. In many others, not so much.
> Especially if they are earning 5k per year as the title suggests.
Not sure that's how the math goes. TFA mentions every employed worker has a team behind them, and is often successful in their job as a result.
Kinda fascinating. Here we are, usually dreaming about how one person could do multiple jobs. There they are, having multiple people do one job in the best (looking) way.
I'd consider shipping LLM generated code without review risky. Far riskier than shipping human-generated code without review.
But it's arguably faster in the short run. Also cheaper.
So we have a risk vs speed to market / near term cost situation. Or in other words, a risk vs gain situation.
If you want higher gains, you typically accept more risk. Technically it's a weird decision to ship something that might break, that you don't understand. But depending on the business making that decision, their situation and strategy, it can absolutely make sense.
How to balance revenue, costs and risks is pretty much what companies do. So that's how I think about this kind of stuff. Is it a stupid risk to take for questionable gains in most situations? I'd say so. But it's not my call, and I don't have all the information. I can imagine it making sense for some.
But if you start from the beginning with a code base that is always only generated from a spec, presumably as the tools improve you'd be able to grow to a big industrial-grade app that is 100% based on a spec.
The question is how many giant apps out there have yet to be even started vs. how many brownfield apps out there that will outlive all of us.
If the spec covers 100% of the code paths, then yes, you're right. But now spec and code are entirely redundant. Changing the spec or changing the code takes the same effort.
If the spec doesn't specify all the details, then there are gaps for the code to fill. For example, code for a UI is highly specific, down to the last pixel. A spec might say "a dialog with two buttons, labelled OK and cancel". That dialog would look different every time the spec is reimplemented.
Unless of course, there was also a spec for the dialog, that we could refer to in the other spec? That's really just code and reuse.
A lot of this rings true for a development agency, in 2026:
> You cannot succeed in design services unless you really believe in your clients and your client’s products. Just as it’s essential to enjoy working with the people you form a company with, working with clients that you like is essential too.
Yup. Otherwise you're just "implementing specifications", which I'd argue is generally not the best form of collaboration.
> I’ve known lots of people who got into services thinking that they can use the income from clients to bankroll their own product ideas. That is not an impossible scenario — it’s been done before more than a few times, and it’s a beautiful thing when it happens. But it’s very, very difficult to pull off. To do services, you need to wake up in the morning with a different approach to life from the way you wake up in the morning to do products, and only a few people have the skill — and stamina — to juggle both at once.
Yup, I don't think anyone I know (and not myself either) pulled this off. I bet many did, just from anecdotal evidence I'd consider it rare, and subjectively, I agree that it's hard.
> Most clients, when they hire a design studio, take the attitude that the studio is lucky to work with them, that they selected them from a plentiful pool of design companies bidding on their business. To many clients, design studios are, in a sense, interchangeable. [...] This is a deadly position for a design studio because it essentially commoditizes the studio’s value.
Yup. If clients start comparing hourly rates, they are a) making a rather meaningless comparison, looking only at a single factor in a larger equation and b) going to try and haggle you down, which is unpleasant for both sides.
I usually give a rough estimate of what I think it's gonna cost, and then we talk about what _not_ to do and where to cut corners to get it down to the ballpark of the budget, if needed.
That's not even all, but I have a feeling my comment shouldn't end up exceeding TFA in length.
That commoditization already happened for software developers, years ago. (Just look at the big-tech commodity worker interview process that even startups now mimic.)
Kudos to design studios who can still avoid that, and shine as unique talent.
Businesses naturally see their "suppliers" and "resources" as exchangeable. And to a degree, they really are, at the end of the day.
But it's still a non-trivial activity with long feedback loops, that requires a level of expertise.
Making workers easily exchangeable requires processes that ultimately underutilise their abilities, finding the lowest common denominator. Some businesses clearly can and want to afford that. Pretty much by definition, that leads to mediocre work.
From what I gather, a good chunk, if not the majority of agency work serves that particular need. But there's plenty of clients out there that want something else. Like all of mine.
It's because there's a lot of overlap between people thinking "those damn lazy workers better get back to the office so they don't slack off" and people thinking "a woman's role is in the household, raising children and cooking".
Enabling women to be with their children during their early years is a good thing. Mothers are not replaceable by fathers or by strangers. You can do it, sometimes you must, but it's sub-optimal for young children. Being able to live on a single income during those years is fantastic, but when it isn't possible, WFH can be a big improvement.
(That being said, this isn't an excuse to be an absentee, deadbeat dad. Traditionally, most people lived in villages, living agrarian lives. Family life was much more involved. That meant both parents were generally present throughout the day. And with age, the fatherly role becomes increasingly important for development. The strict division of mom-in-suburban-home/dad-away-at-urban-office is hardly traditional or representative of historical realities.)
OP never said that. They said the venn diagram of attitudes promoting RTO coincidentally seems to largely overlap the regressive "women should be homemakers" attitudes.
Why? The data supports it. Women were more likely to leave during RTO efforts than men. WFH being a massive boon for workers with childcare responsibilities or medical issues is widely recognized; there’s a reason why there was a baby boom during the pandemic. A lot of the backlash against WFH workers was blatantly sexist; remember all the rage against those “day in the life of a remote worker” type TikToks? Note how they got way, way more hate than the objectively worse ‘working’ several jobs or modern hustle culture scam stuff?
I don’t think it’s the be-all end-all explanation, but the shoe fits.
Women being more likely to leave than men because of a policy does not inherently make that policy sexist. You could say the same thing about a policy that requires police officers in full patrol kit be able to scale an 8' wall or drag a certain amount of weight a certain distance in a given time frame - that instituting that policy in a department that didn't have it previously would result in more women leaving than men doesn't make the policy sexist unless it's both actually unnecessary for the job and implementation with sexist intent.
Those meme-level DITL and older hustle culture stuff are two completely different things, targeting different audiences, and using different methods, so it makes sense that people would have two different reactions to them, even if you think both of them are stupid?
Are there any reports of someone moving their company from WFH to full RTO in order to get women writ large to leave their company? I think it's much more likely that capital owners just want their building full so they don't lose their investments, business owners and executives don't like WFH for various reasons including the extremely overblown risk of overemployment, managers on average want to micromanage and find it easier in-office, and there's no public health backstop to justify WFH like there was 5 years ago.
Separately but related, I don't think there's anything wrong with a factory worker getting paid $18/hr watching someone spread 2 hours of work over 7 hours in the office with two catered meals plus snacks and making jokes about "email jobs" not being real. I probably watched all the DITL things that went truly viral and the comments were never any more sexist than any other viral video on the internet.
It's a return to form, a reinforcement of the status-quo, and in that since it's inherently socially conservative.
You know what else is socially conservative?
RTO makes relationships outside of the traditional nuclear family more difficult. It discourages career building which, because of the patriarchy and our history, is going to primarily affect women.
Sexism and misogyny is actually very complicated. It's built-in to just about every system that exists in America. It's not the sort of simple "woman bad" some people think. It's the choices we make when we design structures. It's part of our DNA, it's not a symptom.
I have been thinking that this is a reason why the megacities are winning. In the largest cities, a couple can cohabitate and both find jobs. In smaller cities, you have to get lucky, and if one partner's job falls through (which may be unavoidable) then you might have to move! In a one-income household you can live in a city with one industry. Two is a coordination problem. The eleven largest cities have reached escape velocity. Detroit is hovering right on the edge. Seattle has favorable climate and a port. Other cities are boom and bust.
I associate it with cool summers which are rare in the US. The rain and dark won't be everyone's cup of tea, but other places with similarly cool summers either have very harsh winters or rhyme with "Nabisco".
It seems like this comment boils down to "relationships require compromise and sacrifice and this scales with more people" which is almost tautological.
Sort of. I was arguing that I see WFH as the superior model for people in relationships, because it eliminates the need for sacrifice and compromise on one dimension: Career beneficial location.
Not on all dimensions, of course. People with kids e.g. will have to find a solution for who gets to work how much, it's a similar conflict WFH addresses partly at best.
Sure, depends on the field. Some fields can't realistically WFH to begin with. Some easily can though. If you have a doctor and a programmer, the doctor can work at a hospital that provides the best career opportunity for them, while the programmer can work at the place that provides the best opportunity for them, given WFH.
If both can WFH, they can even choose the place they want to live in regardless of where their optimal employment options are based.
> This was McKinsey & Company — a firm with world-class technology teams [...]
Not exactly the word on the street in my experience. Is McKinsey more respected for software than I thought? Otherwise I'm curious why TFA didn't just politely leave this bit out.
Can we stop softening the blow? This isn't "drafted with at least major AI help", it's just straight up AI slop writing. Let's call a spade a spade. I have yet to meet anyone claiming they "write with AI help but thoughts are my own" that had anything interesting to say. I don't particularly agree with a lot of Simon Willison's posts but his proofreading prompt should pretty much be the line on what constitutes acceptable AI use for writing.
Grammar check, typo check, calls you out on factual mistakes and missing links and that's it. I've used this prompt once or twice for my own blog posts and it does just what you expect. You just don't end up with writing like this post by having AI "assistance" - you end up with this type of post by asking Claude, probably the same Claude that found the vulnerability to begin with, to make the whole ass blog post. No human thought went into this. If it did, I strongly urge the authors to change their writing style asap.
"So we decided to point our autonomous offensive agent at it. No credentials. No insider knowledge. And no human-in-the-loop. Just a domain name and a dream."
Your reaction is worse than the article. There's no way you could know for sure what their writing process was, but that doesn't stop you from making overconfident claims.
That's the problem with AI writing in a nutshell. In a blind, relatively short comparison (similarly used for RLHF), AI writing has a florid, punchy quality that intuitively feels like high quality writing.
But then after you read the exact same structure a dozen times a day on the web, it becomes like nails on the chalkboard. It's a combination of "too much of a good thing" with little variation throughout a long piece of prose, and basic pattern recognition of AI output from a model coalescing to a consistent style that can be spotted as if 1-3 human ghost writers wrote 1/4 of the content on the web.
One thing I've learned recently is a lot guys (like here) have been out here reading each word of a given company's tech blog, closely parsing each sentence construction.. I really cant imagine being even concious of the prose for something like this. A corporate blog, to me, has some base level of banality to it. It's like reading a cereal box and getting angry at the lack of nuance.
Like who cares? Is there really some nostalgia for a time before this? When reading some press release from a cybersecurity company was akin to Joyce or Nabakov or whatever? (Maybe Hemingway...)
We really gotta be picking our battles here imo, and this doesn't feel like a high priority target. Let companies be the weird inhuman things that they are.
Read a novel! They are great, I promise. Then when you read other stuff, maybe you won't feel so angry?
I've picked up reading again over the last year or so! Maybe, if anything, that is why I feel so angry. Writing and reading are how we communicate thoughts and ideas between people, humans, at scale. A grand fantasy novel evokes a thirst for adventure, a romance evokes a yearning for true love.
What makes me angry, is to use the feelings we associate with this process and disingenuously pretend that there is a human that wants to tell me something, just for it to be generated drivel.
Don't get me wrong, I don't mind reading AI content, but it should read like this: "Our AI agent 'hacked' (found unexposed API endpoints) x or y company, we asked it to summarize and here's what it said:" - now I know I am about to read generated content, and I can decide myself if I want to engage with it or not. Do you ever notice how nobody that uses AI writing does this? If using AI to produce creative media, including art, music, videos, and writing, is so innocuous, why do all the "AI creatives" so desperately want to hide it from you? Because they don't want you to know that it's generated. Their literal goal is to pretend to have a deeper understanding, a better outlook, on a given topic, than they actually have. I think it is sad for them to feel the need to do this, and sad for me to have to use my limited lifespan discerning it. That is why I am angry.
Anyway, there's no need to "closely parse each sentence construction" at all to identify this post is fully AI generated. It's about as clear as they come. If you have trouble identifying that, well, in the short term you're probably at a disadvantage. In the long term, if AI does ever become able to fully mimic human expression, it won't matter anyway, I guess.
ps: FWIW, I agree with you that of all places, some random AI company with an AI generated website reporting on their AI pentesting with AI is the least surprising thing - the entire company is slop, and it's very easy to see that. My initial post was more of a projection at the dozens of posts I've read from personal blogs in recent weeks where I had to carefully decide if someone's writing that they publish under their own name actually contains original thought or not.
Ah well I guess you are on the right side of this either way! No need to even explain. It seems that people really really do care, and its wrong to say maybe its ok that they don't have to in this case. I guess I get it, I am generally more wrong the right anyway, and yes, at the very least, I am clearly in some way sub literate and uncritical as a reader, who can't tell the difference anyway. Not really the guy to be giving his opinion here. I will go find some slop to enjoy while the adults figure out the important stuff! Thanks for teaching me the lesson here.
A vibe? It’s completely obvious AI slop with no attempt to make it legible. They didn’t even prompt out the emdashes. For such a cool finding this is extremely disappointing.
> Not exactly the word on the street in my experience.
Depends on the street you're on. Are you on Main Street or Wall Street?
If you're hiring them to help with software for solving a business problem that will help you deliver value to your customers, they're probably just like anyone else.
If you're hiring them to help with software for figuring out how to break down your company for scrap, or which South African officials to bribe, well, that's a different matter.
My take*: McKinsey hiring largely selects for staying calm under pressure and presenting a confident demeanor to clients. Verbal fluency with decision-making frameworks goes a long way. Having strong analytical skills seemed essential; hopefully the bar for "sufficiently analytical" has raised along with general data science skills in industry.
I don't view them as top-tier experts in their own right, whether it be statistics or technology, but they have a knack for corporate maneuvering. I often question their overall value beyond the usual "hire the big guns to legitimize a change" mentality. Maybe a useful tradeoff? I'd rather see herd-like adoption of current trends than widespread corporate ignorance and insularity.**
A huge selling point for M&Co is kind of a self-fulfulling prophecy based on the access they get. This gives them a positive feedback loop to find the juiciest and most profitable areas to focus on.
For those who know more, how do my takes compare?
* I interviewed with them over 15 years ago, know people who have worked there, and I pay attention to their reports from time to time.
** Of course, I'd rather see a third way: cross-pollination between organizations to build strong internal expertise and use model-based decision making for nuanced long-term decisions... but that's just crazy talk.
> Having strong analytical skills seemed essential
and
> they have a knack for corporate maneuvering
One way to view this is that the above combination of skills is both rare and very useful. That means it's expensive. So instead of hiring someone like that at "full rate" and keeping them around, you can "borrow" them from McK to solve a problem your regular crew can't (or isn't able to) for various reasons.
Plus, as one manager of mine said many years ago:
"We use consultants b/c they are both easy to hire AND easy to fire"
No, they don't have world class technology teams, they hire contractors to do all the tech stuff, their expertise is in management, yes that's world class.
Is it though? Managing teams to not torpedo your company with stupid stuff like this is kinda core to “good management.” The evidence would indicate they’re not very good at that either.
It’s a self fulfilling prophecy. They’re extremely expensive so they must be good so they must be worth it. And because at that level measurement is extremely subjective it’s mainly about the vibes.
My thinking is a bit different here: Seniors, even mediocre ones, already learned a lot of hard lessons by doing things pre-LLMs, even pre-SO. Those skills are valuable and I don't know how to train them into juniors.
I find it easier to get a reasonably smart senior to use AI in a good way, than to train a junior in what thinking to do, and what to outsource, learning basics about good design, robustness and risk analysis. The tools aren't the problem per se, it's more about how people use them. Bit of a slippery slope.
That's just my anecdotal experience from not a whole lot of data though. I think the industry will figure it out once things calm down a bit. Right now, I usually make the bet to get one senior rather than two juniors. Quite different to my strategy from a few years ago.
That's the right move. If a word changes its colloquial meaning, better drop it and find a new one. Happens all the time. From stuff like "agile" in a software development context (pretty meaningless at this point, can mean anything from the original definition to the systematic micro management it got to be commonly associated with), to previously neutral words that became offensive (because they were commonly used as such).
No individual holds power over connotations. Language just evolves.
Absolutely. I'm pro emotions :) Just also good to realise what battles are lost.
I do sometimes rebelliously use words in their original connotation along with an unnecessarily lengthy explanation. Never anything that's now an insult, of course, those I just stay away from and am not mad about either.
I guess the chain of reasoning would be: AI for art is bad -> Writing is art -> Translation is writing.
Personally, I do appreciate good localisation, Nintendo usually does a pretty impressive job there. I play games in their original language as long as I actually speak that language, so I don't have too many touch points with translations though.
1. Check frequency (between every single time and spot checks).
2. Check thoroughness (between antagonistic in-depth vs high level).
I'd agree that, if you're towards the end of both dimensions, the system is not generating any value.
A lot of folks are taking calculated (or I guess in some cases, reckless) risks right now, by moving one or both of those dimensions. I'd argue that in many situations, the risk is small and worth it. In many others, not so much.
We'll see how it goes, I suppose.
reply