SWEs who oppose AI seem to forget that they are paid to solve problems, not write code.
Moreover, big picture, software is getting built anyway. It’s not like if you don’t use AI then that energy use is gone. You need devs no matter what.
Some countries are making laws about renewables requirements for datacenters. Generally they are structured as "gas is allowed as a backup but there are big fines if it is used more than X days a year", and then let the market decide what mix of solar + wind + batteries wins.
The US should do this too.
Capital has historically and enthusiastically done exactly that.
The reality is humanity itself pushes forward in a way that often steamrolls those who don't keep up. Nobody's driving the steamroller intentionally, yet it invariably inches forward nonetheless.
Yes, and you've even explained why:
> People start businesses [...] because they hope to make a better life for themselves.
Not for anyone else — for themselves. They do this by exploiting others.
People can be exploitative, but there's nothing inherent about it any position or another. Taking money for labor you intentionally half ass is no less exploitative than e.g. trying to coerce an employee into doing something they shouldn't be expected to do.
So the Walton's money printing button comes from taking 3 pennies from each dollar, but at a very high volume. If Walmart wanted to e.g. significantly raise the wages they pay, they'd have to substantially increase the prices on everything sold. The balance of higher wages for some but higher costs for all would almost certainly be a significant net-loss for the lower half of society.
And this issue is even more pervasive at smaller shops. Making ends meet is even harder for small business owners. The idea that somebody's just printing money because they own a business is unrealistic. Well it's kind of true for tech businesses, but I suspect we're going to see that change in the future - though that's another topic altogether.
Like, just because the Walmart owners own a company in a low-margin high-volume sector, they're suddenly entitled to the 3% profit, while the employees often need government assistance to keep themselves afloat...?
I'm not arguing that WalMart is socially motivated but that margins in non-tech businesses are not at all like most people think. They're slim with massive sounding outcomes (like $21 billion a year in profit) coming exclusively from scale. Redistribute that back to the employees to the point of self destruction and it's certainly a substantial amount, but far below the level many seem to think, on these topics.
The irony is that it's the companies that people think are 'generous' that are hoarding massive amounts of $$$. Apple makes something close to a million dollars in profit per employee, so they could afford to literally buy every single one of their employees a new Ferrari, every single year, and still be rolling in profit. But these sort of insane tech margins are not normal. More controversially, I think they're also not sustainable in the longrun - and the longrun just got a whole lot closer with LLMs.
So that would be what, 60-70%? IMO that's wildly unrealistic, I'd need to see actual evidence to believe they are so far off the norm.
> WalMart's 3% profit margin is about $21 billion. Coincidentally they also have 2.1 million employees. So the math works out perfectly - a one-time raise of about $10k per year per employee, at which point the business would be unprofitable and no longer sustainable.
How is a company that's breaking even no longer sustainable?
The reason that breakeven companies aren't sustainable is because there's variance in most things, certainly including sales. WalMart's net profit margin varies from around 1% to 3%, so they're currently at a 'high'. Cut that down by 3% and you literally don't have enough money to pay your employees next year when you swing low. Let alone little niceties like performance incentives, raises, etc.
No matter how cute you try to make it sound, when one person owns the land and the other person works it in exchange for pay it's the person working it who is exploited.
Some people like to hand wave the question of who owns land and why they own it away but control of that wealth is always rooted in historic violence.
You can take away any and all land. Imagine somebody thinks a public park is in nasty shape, so they hire a few guys to go help them clean it up. Is that still exploiting people? This all just makes no coherent sense whatsoever.
capitalism is founded on the divide between those who work for a living and those who own for a living.
governments pay people to clean parks. it's not something a private citizen would typically ever do.
Often maybe, but not always.
Avoiding displacing human labor that doesn't want to be displaced is always something I've thought about before any job I've taken.
No putting clankers before humans, no grifts, scams, pushing ads, gambling or incentivizing other forms of addictive behavior.
Fairly simple rules to live by, though it does mean there are entire major companies (and entire market categories of companies) I could never work for in good conscience.
I do find the fact that AI is disrupting us software developers first and foremost seems karmically fitting in general.
unless when combined with robots.
That is why I think AI is more of a service than a tool.
I am not sure what real problem my barber is solving. I am physically capable of using scissors and clippers and learning how to cut my own hair. But at the end of the day, I rather just pay someone trustworthy to do it instead.
The money I pay is worth it for me to not have to deal with any of the previously mentioned tasks.
That's a great point. It's easy to forget. I can also make food at home, but often prefer going out for convenience, skill, etc.
Most people don't do this for the love of the game.
Large corporations needed java code as a means to an end and an army of workers needed a paycheck. That dynamic is coming to an end.
Solving problems is not distinctive characteristic of a software engineer, doing it by writing code was.
That being said, software (written by hand) has replaced many craftsmen. It’s a bit hypocritical to bemoan AI taking away our need to write code line by line. It’s what we’ve been doing to others since the first computer started computing.
There used to be "typing pools", whole floors of mostly women who typed handwritten and dictated notes up into actual documents that could be filed and distributed.
I heard this week that there used to be seven draughtsmen per architect, and now there's one draughtsperson per seven architects.
So, yes, software has completely replaced entire careers. We can't really grumble when it's our turn.
I suspect programming will be similarly forgotten in the future when any program can be concocted trivially and efficiently by description alone.
Much like potters used to be a profession that was needed in every community, and now they're "ceramic artists"
People on hacker news like to think they are Picasso but the reality is 50% as good in 5% of the time has always been better from the business perspective.
But so are all the cyber enslavement stories.
We make aggressive decisions, based on overly optimistic bet on "AI will fix it" mindset. I think it should be more towards, given what we have now and may put in little bit of optimism around AI how can go forward without completely dismissing decades of engineering principles we developed. If AI really goes 10x better than what it is now, then we can just build stuff much faster then anyway, but it didn't we made something reliable today as well something we can keep building on 5/10 years from now.
What does "lets think about it a bit" even mean though? You want other people to stop using productive tools? Or you want to be able to opt out of using productive tools without an employer worrying about it? There always seems to be either a shifting of burden to others, or a denial that AI tools increase productivity.
People can think about AI and use AI with all gas and no brakes. Or you can opt out of using AI for as long as you like to think about things.
Don't push code no human has read into production.
> Don't push code no human has read into production.
So you don't want to do that in your production environments? Or do you want others to not do that in their production environments?
I don't understand the question. I didn't give two options.
> What if "let's think about it a bit" is about your coworkers going head first into a design that you know will fail, and then maybe let's think about how we can do a better design before we lock in a shit one. The AI does build _exactly_ what you ask, whether it's a smart choice or not. Surely you can just automate that choice to the AI as well, why not? "Think about all the ways to design this and pick the best". But possibly we are being led blind into a tar pit. So maybe, just maybe, we can spend a seconds of our lives to try to involve our human domain knowledge and hard won expertise at this job and its systems to guide the AI in a more productive route. Or is this scenario really just about slowing down everyone around you because you're secretely an indignant, neolithic, asshole.
Having different perspectives and advocating for what you think works best, how to use tools, how to approach problems, has always been a thing and always will be. People where I work have a lot of different ways of using AI and share ideas and techniques, for example. Telling someone to not do what they have found to work with things like "let's think about it a bit" doesn't work though, that's not collaborative, you don't just tell others to stop and think, you have to actually do some thinking yourself and come up with constructive ideas. Doomsaying or vaguely handwaving at how bad things might be doesn't work either. It's like telling farmers they shouldn't sow their crops because you're concerned the gods might be angry and smite the village so they should stop and think about it a bit.
The reality is that AI is a very productive tool and it is never going to be stopped now. Bad things could come of using AI, bad things could come of not using AI, a bad thing could happen when you walk down the street tomorrow. A lot of people are scared by it, but really just saying things like "let's think about it a bit" betrays the lack of thought that has gone in to understanding why other people use it and how people react to that kind of thing in general. Not really surprising OP has seen a bit of apathy or hostility to their message.
This is the EXACTLY the kind of BS you get. No, not asking you to stop using those tools. Its not 0 or 1 thing. Its not a choice between "all gas no brake" and "I wont use AI". But maybe, just maybe, think a little about what you are producing, instead of just being a ENTER PRESSING entity. The amount of spaghetti that is being generated is not just an issue from the perspective "oh the code looks horrible to read", but also fundamentally how we build complicated systems, and it becomes bandages over bandages that just sucks and potentially fragile.
The alternative is don't go all gas, work strategically thinking a bit longer term like we always had in past, and maybe you loose little velocity in short term, but you are likely better off in long term.
AI is always ready to implement something, or generate code, and make decisions, and it will do whatever you ask it to do. However, to make right decisions you need to understand the problem/context etc etc. And that was always significant portion of work, and you can be little faster with that with AI, but I think that part is still kind of slow but we as industry are in denial about that, and just not doing that part that well anymore.
No, THIS is exactly the kind of BS you get. All that and you didn't answer the question at all. What exactly do you want?
> But maybe, just maybe, think a little about what you are producing, instead of just being a ENTER PRESSING entity. The amount of spaghetti that is being generated is not just an issue from the perspective "oh the code looks horrible to read", but also fundamentally how we build complicated systems, and it becomes bandages over bandages that just sucks and potentially fragile.
Yep, people do think about it. Don't you? Do you not like how others think about it, or do you not like the conclusions they reach? Would you rather they do something differently? Without the BS, let's hear it. What do you want?
Your comment is stating a belief that Anthropic will fail as a business.
AI-pilled folks seem to forget that SWEs are paid to develop _software_, which last time I checked was made from code.
No one merely "solves problems" in a vacuum. You have to engage with a domain, a medium, and the tools of both.
Love this statement, 100% agree.
Though, there's a competing effect: as AI gets better, the amount of skill drops. Maybe the demand for seniors will turn into demand for juniors as AI improves at architecture, and the work shifts towards manual testing.
It sounds like you, like me and probably a lot of us here, are in startup world, but even here I would say the average career is something like four or five years. Most of my peers outside of startup world have worked at the same company the last decade.
I think we're probably the exception still.
Nothing fake about these applicants, they’re just hard to convince.
I'm already remotely prompting Claude through the "senior engineers" where I work. I'm not saying anything, but the company would probably be better off without them. The level of disconnect with the code has effectively turned them into dead weight. They'd be better off replacing them with manual testers.
The question is how long it will take management to notice and decide to do the next round of layoffs.
This is not a good thing.
BigTech headcount growth stalled before LLM. The decade before that, the big employers basically understood that they have to hire from universities and train employees to get to their hiring targets. No one expected the out-of-college junior eng to be net productive in the first year or two. The problem is if you don't need to grow the headcount beyond what the market can already supply you in mid-senior engineers, why do you need to pay for their training?
I cannot believe that companies are still using leetcode. That's just complete idiocy. The game is all about reading and understanding code now. Anyone who is still conducting timed code trivia examinations has completely lost the plot.
Stop cargo-culting your interview process, and use your brains!
So maybe we should try testing for that skill. This is not a hard thing to do.
To be fair, the puzzle problem technical interview itself was always a cargo cult, mimicking Google's process since 2004 at least.
[1] https://www.npr.org/2004/09/14/3916173/google-entices-job-se...
Let's just have a coin flipping tournament.
I do not understand this...Stockholm syndrome...that some programmers seem to have for the idiotic interview system.
There is a century of data and studies that suggest cognitive ability is positively correlated across tasks. Conducting IQ tests for hiring is practically illegal in the US. Leetcode is the closest you get to an IQ test without tripping some laws.
I think you have to let this one go. SAT, LSAT, GRE, ASVAB all correlate well with IQ scores. Leetcode should too, after the interviewee does a few weeks of practice (just like all those other tests).
I mean, you're just making stuff up, but ok.
Leetcode is just one step away from that.
Leetcode is not a general cognitive test, obviously.
> Leetcode is not a general cognitive test, obviously.
What? How's this related to the argument.
If you're saying, like, the Wonderlic test is fine but IQ testing isn't, all you're saying is that the "IQ brand" is problematic. That's wrong, but also it's not saying anything interesting. Call it whatever you want, it's the same business premise.
If you're saying that Leetcode is, like the Wonderlic, a direct proxy for IQ, that's just clearly false.
I hadn't actually thought about it this way, but it makes sense. I'm in my early 50s and hella experienced and talented (if i do say so myself), but I refuse to do any interviews that require me to do any more preparation than researching the company I'm applying to.
It's obviously absurd, and while I almost understand it for a company that doesn't know you, you'll get hit with this stuff when you've been referred internally, by people you worked with in the past.
But there's plenty of people with high intelligence and problem solving that aren't good programmers, so we probably want to try to hone in on that a little bit.
Leetcode is popular because:
1. It gauges problem solving ability and pattern recognition, which are essential to any job, and particularly useful for software engineers.
2. It is language agnostic - most jobs would rather have a strong engineer that doesn't know their particular language/tech stack than a weak engineer that is familiar with the stack.
3. It has objective evaluation criteria (correctness + time/space complexity).
It's certainly not perfect, but I have yet to see an alternative that accomplishes all of the above. The one thing I can see potentially complementing it is the new style of AI-assisted assessment where you are dropped into an unknown codebase, and asked to make fixes/features that are assisted by an AI agent. This solves the language-agnostic issue with pre-AI versions of these interviews, where you had to have memorized specific tech stack features or language syntax in order to accomplish the task. Now AI can take care of that stuff, and the interviewee can focus on the problem solving aspect.
Proof of claim absolutely required here. Leetcode primarily measure's someone's ability to memorize leetcode problems, and secondarily measures their ability to vomit this knowledge up in a stressful situation.
Seriously. There's an entire test-prep industry here. You'd have to be oblivious to not realize that the system has been gamed to hell and back.
Since you are just asserting things, I will assert a simpler explanation: the primary reason Leetcode is popular is because it is cheap. If you have the problem that you have too many applicants and don't want to spend money interviewing them all, you have to come up with an efficient filter that doesn't violate hiring laws.
You don't particularly care if the false negative rate is high, so test of irrelevant trivia is what you do.
In other fields, those things aren't nearly as meaningless and easy to game as they are in ours.
I’m sure the companies know that Leetcode is not a great indicator for likelihood to succeed in the role. If they had a perfect information about people, then would stop interviewing at all and just take the best people who applied.
They don’t have perfect information. The information is highly asymmetric. The companies are just trying to not be efficient and not get burned.
It sucks for candidates. But it makes sense for companies when they thousands of applicants they know effectively nothing about.
Well, no. It rewards ability (and free time) to repeatedly work through problems and memorize the solutions. And it rewards acting skills so you can perform like you're discovering solutions on the fly, that you've actually memorized.
That's all it does.
What you really want to weed out, at least at top-tier companies who can afford to be more selective, is people who have a resume, but are not that great at fundamentals. Most loud complaints seem to be of this nature: guy had N years of experience at previous company/is author of popular software, but couldn't get through basic linked list/recursion/BFS--as if this is not an acceptable bare minimum expectation of a professional in the field.
Often people are too polite to say it out loud, but realistically, that is exactly when it is working as intended.
I think I'm gonna get a stroke reading this. The classic fallacy is the nonsense you're spouting — that there's anything besides the job itself that is relevant to it. You're hiring people for x, so the only thing you care about is their ability to do x. This is obvious.
The perfect test is just hiring someone on the spot and seeing how they perform. We don't do this because it's expensive but obviously it would be the perfect test, measuring exactly what you're hiring for, by definition.
So then any test that goes further and further away from that ideal becomes worse and worse at predicting job performance. The trick is figuring out a good enough test that's still reasonably quick and cheap to do.
Deliberately going out of your way to test your canditates for something unrelated to the job is insanely stupid.
It's essentially just arrogance. Arrogantly asserting that you know for sure your particular random test (Leetcode) is a "random cogintive task" and that it actually is relevant to the particular job.
Again, easiest to see by thinking of the opposite example to before — the worst test possible would of course be something completely unrelated, so idk, having a chef play ping-pong. I'm sure you could convincingly argue it tests something, but why in the world would you not just have him make a dish, since you know, that's what you're hiring him to do? (it's not actually by the way, now that's a classic fallacy — that the job is the mechanical subset of it and not the job as a whole. Soft skills, anyone? sigh).
Another common example of this utter arrogance is thinking that a candidate's performance during a highly stressful, unnatural, and artificial classic interview grilling environment is indicative of their perfomance in the every day feeling-secure-in-their-job state of mind. Oh, look, this fool I'm basically abusing from my position of power is stammering and squirming, must mean he's a good-for-nothing loser! Hah, another fraud found!
So sure, keep putting people in as much stress as possible and asking them how many golf balls fit in an airplane. BTW, I walk out of such interviews immediately. Have fun with your new Leetcode grinder performative actor hires though.
Multiple trillion dollar companies has not been that bad.
It's basically just a grinded leetcode test.
IQ tests ability to learn on the spot, yet leetcode so widely disseminated that people prep for it, defeating the purpose of the IQ test.
Psychologists have said the proper high signal interview has always been a small representative piece of what people are going to be doing in the real job. But nooo, techs seem to be special and well paid enough to invalidate these vast stretches of research right?
Literal psychologists have done the research on this: A good, predictive interview is a small representative test of what people do in the normal job. Only us techbros seem arrogant enough to want to be the exception to decades of research.
The argument that you can use the the artifact of the coding challenge as a starting point for further discussion is perhaps true, but it's like saying that you can use an applicant's resume as a starting point for discussion, once you've filtered out everyone who failed a keyword search.
I wish you were correct. The trend is that nobody reads code anymore, AI writes it and people rubberstamp it with barely a glance (if even that, some companies might have AI rubberstamp it and off it goes into production).
My colleagues use the LLM to do that...
Leetcode could be replaced by learning a made up language, memorizing a huge list of numbers, or reciting an epic poem.
The Leetcode game is mostly memorizing pre-existing solutions and then practicing applying them to lots of variations of the same problem.
The real filter is psychological: will you jump through hoops even when they don't make sense?
Unfortunately that means we may see more of these brain teaser / gauntlet style interviews.
Interviews are so hard
border-radius could have knocked me out of the game, but I decided to keep going. And I'm glad I did.
I’m excited about what this next progression entails. I’m building complex software in months in a home lab that would have required millions in investment just five years ago. In five years I don’t think any of us can say for certain what the industry will look like.
4/5
Have you been able to translate that into a steady income?
compiled languages like C were bemoaned by people because their skill at crafting assembly by hand was suddenly less important.
doesn't ring a bell from the time I went through that transition; people used C and FORTRAN and happily dropped back into handcrafted assembler as needed, and applauded the fully assembler works of some, etc - but nobody (in my recollection, was seriously bemoaning compilers and calling for a return to 100% assembler). similarly with people who were brilliant with arithmetic, or symbolic manipulation, or manual drafting/lettering.
My mother was a computer, she didn't pine for the days of rows of meat computers; I took drafting as part of engineering and worked to assist and eventually replace drafting rooms for cartography- that was a slow rotation out and perhaps had the greatest impact of all the things listed- but people weren't exactly clawing to have their ink stain jobs back.Symbolic manipulation is an interesting one - I recall a general distrust of Monster Group proofs so large they involved software generation and checkers ... but things are still advancing through that same distrust with lean and so on. What I did see is "symbol manipulators" diving into creating automated symbolic algebra suites such as Cayley (now Magma) and still using them today to crack Quantum encryption candidates, etc.
ie. It comes over a bit hyperbolic
If you like thinking, you can keep thinking. AI can't stop you from doing that unless you let it.
Maybe at some point AI will do this better too, and at some point they will just mind read you as to what you're trying to build so you don't even have to be able to verbalize it any more, but we are far from thatm
> The transition we're in includes a substantial disengagement of thought.
While I think you are more correct than not, a cheeky part of me cannot help but think that humanity might be better served if some thoughts were never engaged with in the first place.
1.) I apologize if this is a rather blunt question, but how much of your identity is based on your own perceived (and perhaps exemplified/actualized) intelligence?
I have had a fortunate enough life to have befriended many people who I consider to be far more intelligent than myself. Of these many individuals that I remain in contact with, I have noticed the ones that are the most adamantly opposed to the LLM frenzy, the "death of thought", etc. are the ones that have the strongest attachment/most pride in their own intelligence. I suppose it is a rational reaction, but I think LLMs are revealing hurting a lot of people's egos.
> For those of us who like thinking, this is something to mourn.2.) That statement is what I am most curious about. Do you mind elaborating on what thought there is to mourn? What exactly is being taken away from you? I hope I am not about to come off as condescending, but what is actually preventing you from engaging in deep thought? One is not compelled to use AI outside of their own volition. Even in instances of employer mandates, one is not forced to use AI outside of their occupation.
1. I feel like I have a decent amount of my identity tied up in being "smart". I have always enjoyed learning, have been good at solving problems, and have been able to get out of some pretty difficult circumstances that were definitely slanted against me in terms of being able to find a stable and high paying job through a combination of luck, being born decently smart, and hard work.
2. For my entire life I have been able to work towards or have a job where my purpose is to solve interesting problems and get paid well for it. I have been lucky enough to be in a position where I could paid to sit down and build solutions, understanding every intricate detail of what I made. And now, it seems like the entire industry is just throwing this away. Why engage with deep thought when everyone around is thoroughly convinced that the act of thinking is "last gen" or "going out of style"? If everyone else is wrong, that doesn't change the pressure to just stop thinking and ship 50 commits a day of unread slop. If everyone else is right, why bother thinking? I am just going to lose my job and be stuck doing menial labor until the AGI builds robots that can do my job. Either way I am unhappy. And sure, I do not need to use AI outside of work, but that does not change the existential dread of having the next 30-40 years of my career turned into something that I absolutely hate.
Overall, we have effectively built a machine or a widespread perception of a machine that rewards not thinking and not taking responsibility. Why bother trying to accomplish anything if a machine can do it better than you. I value solving problems, I value understanding, and I value working hard, and at least for me I feel that I may have to start mourning the fact that you used to be able to get paid to do all three. On the bright side, if anyone my age is poised to, by the stupid credentialism of our society, stay in the job market after this, it is me. So either I make a decent amount of money and escape the permanent underclass or all of society is cooked, in which case at least I won't be judged.
Just because someone doesn't believe the same as you, it doesn't mean that they've got a fragile or damaged ego. I, personally, think that people who don't see the death of thought are delusional, and it's got nothing to do with ego.
When someone spends 40 hours per week doing a thing, having the ability, motivation, and pleasure in solving problems they enjoy can and is being taken away. Yes, one can engage in "deep thought" in personal time, if you've got time for that with children, responsibilities, and other leisure activities. Not everyone has time to engage in deep thought enough in free time to compensate for the loss in the workplace.
Been able to finally remove a really painful and bad ORM from a legacy codebase.
Not really, the problem is just changing. Just like C allowed developers to leverage a standard library and a checked type system to create software, AI is allowing developers to leverage english and verifiable specifications to create software. We're all still developing software per a set of requirements at the end of the day.
The varied implementations will always exist and the job is both picking the right requirements to work on, and delivering in a way consistent with its goals.
They're still relevant sometimes. ffmpeg core encode/decode routines are written in multiple different assembly languages. These very same LLMs run on highly optimized code on purpose-designed hardware (!) with plenty of symbolic manipulation to find the optimal execution routines.
3/5
yep
If coding was it, you have a more serious problem than AI
(I'm excluding trivial, hedonistic things from what I enjoy)
FWIW I love not having to spend so much time writing code. I get to focus on solving problems for end users, which is way more fun and rewarding IMO.
It wasn't so much coding that I loved, although I do love that, but being able to build and understand something far greater than myself, and the puzzle of trying to find the right abstractions and tools to make something beautiful.
Boy am I getting tired of reading this sentence.
You make it sound like the only thing that's gone away is the physical act of entering characters -- completely ignoring the fact that working through the problem and wrestling with the code (which included, among other things, typing it) were one and the same. Removing the "writing code" part and expecting the other parts to remain is just as sensible as believing that you can remove a swimmer from the water and expect them to keep their physique.
"Writing code" was one of the most important _mediums_ through which we practiced _deep thought_ about programs. It wasn't just typing.
> FWIW I love not having to spend so much time writing code...
Sounds like maybe software engineering isn't for you? Or rather, wasn't? You're lucky that the "one thing" you don't like about your career was removed. Try and approach those of us who are in the opposite situation with a bit more tact and compassion than "Luckily now is also the best time ever to explore alternative career paths!" What an absurd, tone-deaf thing to say.
There have been many times recently where, by choosing not to have ai generate code that at first glance seemed like it would be repetitive and boring, I have developed much better and more elegant abstractions for what I was trying to do because by working through the code and wrestling with the problem I found a better way to do it.
However, I don’t believe (and never really did believe) that writing code is the only means to understanding how to build good programs. I think best in prose and pictures, so writing requirements docs and thinking through abstractions with component diagrams has been my preferred way to work for years. Maybe I am the lucky one…
Apologies for causing any upset, I really do not wish to cause ill feelings. I want to see our field of software engineering flourish, and if that means trading a screwdriver for a chisel I’m all for it.
I'm old enough to remember when compiled languages like C were bemoaned by people because their skill at crafting assembly by hand was suddenly less important. Or similarly with people who were brilliant with arithmetic, or symbolic manipulation, or manual drafting/lettering. These skills were all paramount at one time, and it's natural that the people who excelled at them will feel a sense of loss.
The real goal, however, will always be to solve real-world problems. Engineering consists of whatever gets you there most effectively.