>If you build your platform well, then you can execute fast, but also safe.
this is extremely true, but it seems less and less like anyone wants to invest in a solid platform and just wants to jump to executing fast and unsafe. and then pretends that ai can definitely do both when the experience is quite a bit different.
I have seen at least one example develop in real time. You typically spent years building before you had a platform, then lack the enthusiasm from senior leadership to invest the next 12-18 months with no new features and hard to quantify - maybe no - returns. Then you get displaced by newcomers who are "platform native"; what this really means is their engineering misteps haven't been discovered yet, or even if they guessed correctly the world has turned and made their previously correct solution now a failing one. And now we have something called "AI-native" that is going to solve this once and for all with some sort of magic, and you can't lead these companies unless you truly believe in the magic.
“ You typically spent years building before you had a platform, then lack the enthusiasm from senior leadership to invest the next 12-18 months with no new features and hard to quantify - maybe no - returns.” —> this is failure from the team and especially people who should do product management job on that team.
none of these types of pieces of content focus on what was created for users, its always about how sky high their "shipping" metrics are (PRs merged, LoC, etc). it makes it extremely hard for me to care, as they all boil down to "im a dev who made some loops on loops on loops that writes a lot of code and spends a lot of tokens."
i will say, at least this article says "we merge 5x more and our revert rate has stayed the same." so thats at least a metric i can start to respect
Any good product leader will tell you, sometimes not building something is actually good for the customer. Slower dev cycles have you the ability to take time with decisions and make adjustments. The obsession with shipping more code is making things worse for users and I would argue, damages the company in the long run.
Eveyone has a backlog. What happens when you clear it in a month? Do you suddenly have better ideas about what you want to build? Do you suddenly have better intuitive designs? Do you have more users or the same users using the product twice as much? In most cases, the answer is no.
AI gives you the speed to execute when you need to, but knowing what to build and how will still remain a bottleneck.
Now the real question is "is the revert rate the same because you still have the same process, or do you fix-forward more often now, so your revert-rate is because of higher-severity incidents?"
I mean we (huge tech company with ~2000 devs) literally never actually revert anything, in my 2 years here I have quite literally never reverted a commit. We have a staging/release cycle that means nothing ever needs a revert, you just fix issues in followup commits on trunk
This is another one of the infinite meaningless metrics that AI cash burners love to use without context
When that happens we revert immediately. But to be fair, this kind of commits have to be looked at in detail, and you often need the CI export because those yaml files are a pain to write...
well, i did go check out the company spawn from the article. its certainly interesting how hands off their process is and how much they ship, but holy shit the games were fucking horrible. there was a direct WoW ripoff (right down to the assets) that was unplayable, a racing simulator where my controls stopped working 10 second in, and some sort of RPG that i started and just never loaded. so i will take what they are saying with the heaviest possible grain of salt.
Yes exactly this is my standard for everything now. You can spend an unbelievable amount of tokens doing all kinds of things that are interesting as processes in their own right.
at the end of it: is anything of value delivered to customers? the company might say "well users make the games with AI, we just serve them and host the multiplayer." okay, but again, what value was created? they brag about being one of anthropic's top customers; congrats you are handing VC money to anthropic. why should i care? theres no answer for why anyone should care, because to them the system and clout is the product, the product doesnt actually matter.
at least thats my read on it. i dont know how else to understand whats going on here.
>The problem for me is that it's really hard to project what this industry is going to look like 6 months from now, let alone 6 years.
i keep thinking how crazy it is we went from ChatGPT releasing in 2022 to multi-trillion IPOs 4 years later. the industry still hasn't agreed on how to generally use anything. crazy times ahead.
interstingly i think what you are talking about is pretty apt, but not the way you are framing it. knitting and sewing were impactful things in their time; clothing has been something humans need for a long time and more skilled craftsmen were able to produce hgiher quality garments. new techniques increased durability, wearability, comfort, etc. machines commoditized that and made it mich faster to produce garments, so turned these into hobbies and the odd artisan fpcused and made new improvements, but not as often as before.
programming will likely be the same. fewer people who care to be craftsmen, more hobbyist, a few artisans who really dig deep and make new patterns (we still dont see AI sampling out of distribution).
>reduction of the job to a hobby takes that away from them.
this is your personal feeling. they never had anything in the first place, just that the market was valuing a certain skill for what it could output. the perspective you are posting is purely a construct.
Sure it is a construct (it's how I feel at least).
I didn't mean to say sewing and knitting weren't impactful - on the contrary, they are analogous to programming: they were impactful but now they're basically hobbies. Maybe there are more developments left in the clothing making process - not sure.
i dont meant to come across as too harsh, but that is something that you will have to figure out. if companies are less inclined to give salaries for technical skills, then its on us to figure out how our current skill sets become marketable.
even the job of freelance engineer is customer relation. how good are you at extracting product requirements? understanding a clients workflows? these take relational skills and are often what freelancers are paid for, beyond the ability to produce code.
this is so accurate it hurts. the amount of my coworkers who just outright have handed any and all thinking over to the computer is staggering. its not just senior either, plenty of devs at the lead and staff level are producing complete garbage that has to be rolled back within an hour of deploy because it is extremely broken, no one verified, and it passed automated checks.
there are several features over the last few months that were obviously made and deployed and no one even launched the dev server and tried a single thing to verify if it was right. just "pull my ticket, do my ticket, push my ticket. i am a developer."
Managers can be even worse. I’ve seen an entire roadmap mostly AI generated. Director+ across the company approving based on it having the right keywords, without nuance or detail.
I’ve seen monthly and quarterly executing results AI generated with plainly wrong factual information.
Yeah, it's not actually really about coding, it's about thinking. Anyone with any software experience knows the job is 90% thinking and 10% typing. At first I thought AI agents were just a faster keyboard, but no, they think for you too. For many people it's going to be very difficult to force themselves to think when they have a magic thinking machine that makes it look they thought it through.
That and the shear volume. Since you're not writing it yourself you have to figure out what it's doing if you want to be able to review it, internalize and follow how it's changing the model that the software defines. This is doable but it takes time.
Time unfortunately that you are simply not given because the whole point is to work faster so expectations of velocity have of course increased.
So you end up having to get a fuzzy idea of a given changeset, look at it a bit and evaluate quickly if it's a good change or a bad one and click it through, and on to the next thing.
At the size of PRs being whole features and doing this 5x faster than before, all you've got left as a senior is your Spidey sense. As a junior.. no idea how they cope.
We'd all love to still spend that 90% thinking time, but it used to be justified by necessity of getting the job done. Now, it's just not a luxury that is afforded.
What can ya do.. I'm slowly learning to be the best bot herder I can be, but it certainly feels like a change in skillsets. I definitely only feel like I'm able to do a good job due to enough experience and building and growing software projects over time to have an idea of what kind of decisions might bite us down the road, as well as to know what maybe can't be known but is just worth a risk. Without that kind of intuition I think I'd feel like I was really shooting blind.
several people on my team cannot even reason with decisions their code made, why architecture is a certain way, etc. without consulting their agent. its the thinking that is falling off, i dont care about the code nearly as much as the critical thinking part.
In general, it's bizarre that people look at problems this systemic and conclude that they are primarily a failing happening at the level of individual contributors. This organizational rot didn't even start with LLMs, though it's certainly been accelerated by them
myopic systems are one thing. developers and product leaders outright refusing to even click on pages and test features before they go to production is worse than their orgs simply being bad. many developers i work with can barely even reason with decisions anymore without consulting the agent. it is worse than simply saying the orgs are bad.
It's a feedback loop. I've fallen into something close to it (Thought not on the level of just not testing things before I ship them) myself once or twice under pressure. If there are deadlines that get tighter and tighter and execs and managers make credible threats about them and every checkpoint takes days, and every time you look for feedback people are doing PR reviews with AI and saying "IDK ask claude" and giving you LLM output in response to your questions then you're going against the grain by having standards in a way that could threaten your job security. If you happen to have the kind of power that lets you push back successfully in your organization, or the kind of organization that will actually take pushback seriously and not just label you a problem for it, I encourage you to be the change you want to see in the world. I think a lot of people don't meaningfully have that option. I have already found that out the hard way once. This tech is not unique in having modes of usage that are lazy, addictive, or sloppy. The difference here is that the culture from the top down in a staggering number of organizations is creating active pressure to use it that way
I think the success of expanded offshoots (OSRS, TurtleWow, Ascension, etc.) showed there is plenty of demand for games that add new features to older, slower, and more sociable games. many features in wow forever are lifted directly from some of these offshoots. blizzard leaning into things like sd models, no flying mounts shows this is beyond just nostalgia bait (something wow classic has been poked for) and indicates that these older iterations that had less streamlined experiences can still have a lot of juice if brought in new directions.
only on the surface, plenty of places have moved out of the big tech ecosystem to models hosted at smaller providers or even self hosted. its not the majority of work but is growing.
this is extremely true, but it seems less and less like anyone wants to invest in a solid platform and just wants to jump to executing fast and unsafe. and then pretends that ai can definitely do both when the experience is quite a bit different.