Hacker News new | past | comments | ask | show | jobs | submit
The arcane technical problems aspect of the job has always been changing; LLMs are just a continuation of the trend.

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.

Bullish on AI in the long to medium term but that doesn’t change the fact that it’s displacing junior level jobs now.

Several students I have been trying to help enter the field are facing greater barriers than I have ever seen. Not just leetcode but dozens of interviewing rounds. The problems that they are asked also feel increasingly hard and it seems like interviewers are using AI during the interview while forbidding the interviewee from leveraging any external aids.

We are really burning the next class of developers with the current interview process

> Not just leetcode but dozens of interviewing rounds.

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!

This is a classic fallacy: that interview should look the same as the job. There is no reason[1] your evaluation pipeline has to necessarily resemble the task you are hiring for. You could test people on random cognitive tasks and predict their job performance.

[1]: Purely technical. There may be social reasons or legal consequences like "disparate impact" theories coming at you.

loading story #50570389
loading story #50571792
loading story #50578842
> This is a classic fallacy: that interview should look the same as the job. There is no reason[1] your evaluation pipeline has to necessarily resemble the task you are hiring for.

Well then. If the "classic fallacy" is that job interviews should reflect the actual job, then what does it really matter what we do? Let's just have a big pub quiz. That measures "intelligence", too.

> You could test people on random cognitive tasks and predict their job performance.

Show me a single piece of evidence that memorizing code golf answers from a book is a valid proxy for intelligence, and we'll talk.

(Hint: You'll have better luck convincing me that it's a stealth way of discriminating against older, more experienced applicants who are further from undergrad and less willing to re-memorize Cracking the Coding Interview for the 150th time. Because it actually is.)

In any case, I do not understand this...Stockholm syndrome...that some programmers seem to have for the idiotic interview system.

loading story #50570567
loading story #50570288
loading story #50571547
As someone who's spent too much time grinding leetcode: leetcode is very effective in filtering for people who are willing to put in 50-100 hours prepping a cognitive skill only used in interviews. People who have the time to spare to do the prep and are willing to do a bullshit task for the chance to work at the company. People who are desperate for the pay or prestige, and will likely not rock the boat too hard because they worked hard for the job.

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?

I used something akin to leetcode in my days as a hiring manager and would not give up on it as a tool. It's not the final rank, but it filters before the interview. If the code is perfect there is not much to talk about other than probing whether you wrote it yourself, but since perfect code doesn't exist it gives us a good basis on discussion during the interview of things that do matter on the job. If the code is poor or nonexistent then I can dismiss (maybe sometimes wrongly) the candidate and focus on more promising ones. Of course it is not great for candidates having to do a whole lot and becomes more meaningless when the answer can be vibe-coded but it does still help imho.
loading story #50575231
I don't dispute that it's an effective filter. That is pretty much the only thing it is good at: winnowing a population of applicants down when you don't care about the false-negative rate.

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.

loading story #50572121
Reading and understanding code? Or architecture? Reading code seems to be a very local concern, something that could be swapped out at will, sometimes with a whole new language and ecosystem.
I don't know, but if you don't write the code anymore, and you don't understand the code anymore -- at least to the extent of being able to quickly read and fix it -- then you certainly are not necessary.

So maybe we should try testing for that skill. This is not a hard thing to do, and there are many, many functional responsibilities and traits that a professional developer requires, which go beyond this.

Here are but a few, off the top of my head: spoken communication, written communication, time management, organization, focus, creativity, system design (aka architecture, as you suggest), planning.

It's always been painfully idiotic that we've used code golf for interviews, but the rapid advance of code robots has thrown it into sharp relief.

It was always stupid to do leetcode interviews
> The game is all about reading and understanding code now.

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).

>> The game is all about reading and understanding code now

My colleagues use the LLM to do that...

{"deleted":true,"id":50569740,"parent":50569263,"time":1795144715,"type":"comment"}
Reading and understanding code is not it either.
I have 20+ years of experience, and even I can't psychologically handle the current interview process. I think people underestimate how much of the interview process is basically a form of "high stress memory testing".
I've heard an idea that hiring for juniors is more like hiring for quants now: you care less about coding skill and more about general aptitude / intelligence.

Unfortunately that means we may see more of these brain teaser / gauntlet style interviews.

Even passionate devs are getting affected. Earlier in India, Engineering colleges used to push students towards IT from other streams pointing out that IT jobs are lucrative. But today people are warned about joining IT jobs expecting it to be a scam.
As a mid level dev who knows I can competently do the job I’m having the same problem :(

Interviews are so hard

expectations for juniors will change over time, ands university curricula for software engineering degrees with it
This is just because companies realized that the kids are both unnecessary and desperate. As AI gets better, the effects will move up the stack.

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.

loading story #50568526
loading story #50570071
Going from asm to C is a different mode of thinking, but a cerebral challenge nonetheless. The transition we're in includes a substantial disengagement of thought. For those of us who like thinking, this is something to mourn.
If you're ambitious enough, there is still plenty to think about. Design, tradeoffs, what to measure, how to express your goals, what you value and want to spend more time going deep on, what counts as good enough, etc. A lot of decisions but they are of the sort where you also need to be given enough agency and decision by your company. The type of job where you're given a spec and you just code it up is indeed going away.

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

AI makes it possible to disengage from thinking, much more than past technologies did. You can prompt it with "yes, keep going" and just accept whatever it spits out. However, you'll still get better results if you are also thinking, and challenging it when it makes bad assumptions.

If you like thinking, you can keep thinking. AI can't stop you from doing that unless you let it.

I feel that some, I’ve also been able to take on just a huge scope of work and deliver satisfactory results, which is interesting in its own way.

Been able to finally remove a really painful and bad ORM from a legacy codebase.

> The transition we're in includes a substantial disengagement of thought

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.

Really? I find the thinking is very different but I'm still keeping very busy. It's like never-ending PR review cycles.
Do you mind helping me understand a couple of things about your perspective?

> 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 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.

I'm not the person you're responding to, but I think that you're searching for a correlation that does not exist. There is a universe of nuance in why someone might believe that LLMs cause the death of thought that has nothing to do with their ego. Perhaps they've seen it directly affect engineers on their teams. Perhaps they have themselves experienced the phenomenon. Perhaps they've read the numerous studies that have been published on the subject.

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.

disclaimer: Not the OP.

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.

I spent years of my early career being the guy who could make websites look bubbly with custom border graphics stuffed into <table> layouts.

border-radius could have knocked me out of the game, but I decided to keep going. And I'm glad I did.

OMG wonder how many of us remember/experienced those times.. still remember using Java applets to do some interactive stuff and replaced that with Ajax when it was a thing! You are a hero web dev if you write 100 lines of Javascript.
I remember how frustrating it felt that website standards no longer mandated tables for layouts and we had to learn div layers. Not to mention the semantic web or the switch of dynamic content away from flash…

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.

The switch from table-based layouts to divs & CSS happened over 20 years ago, and I still don't really get the value of it. Tables gave an intuitive control over page layout that worked in every browser and maintained structure even without styling. Divs required obtuse CSS float and clear rules and useless nested elements to achieve the same designs, and it didn't even work everywhere consistently. At the time it seemed like change for the sake of change, and 20 years later that space is still a mess.
Mobile layout came along
The point is "semantics" which actually means "the word table is only allowed to be used around numeric data, and you can't ever say italic or bold, you have to say emphasis or strong emphasis, but they're allowed as long as they're wrapped in a style attribute for some reason"

4/5

> I’m building complex software in months in a home lab that would have required millions in investment just five years ago.

Have you been able to translate that into a steady income?

It never does. And the software wila probably rot on the vine
In what world does this need to be the point?
loading story #50580301
I love this comment.

SWEs who oppose AI seem to forget that they are paid to solve problems, not write code.

Most SWE who "oppose AI" in my experience, don't oppose AI but oppose its how its being adapted or used. All gas no brakes. You can't really say "lets think about it a bit" without becoming AI denier/opposer or whatever.

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.

loading story #50568506
Everyone is paid to solve problems. If the things that make you stand out at solving problems compared to the average worker is writing code, this no longer being a moat is probably not good for your bargaining power.
loading story #50568232
I actually think a wide majority of SWEs, pre-AI, were in fact primarily paid to write code.

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.

loading story #50568801
Many SWEs will not be paid to solve problems anymore due to AI. The ones that remain might be better equipped for the task, although I don't expect interests to align on doing a better job instead of a cheaper one.
There's room for nuance there. I am well aware that the goal is to solve problems, but I actively enjoy the process of designing a program and writing the code.

Sure, maybe I can more effectively and efficiently solve problems by driving an LLM instead, but that's not a job I enjoy, or even care to do professionally.

loading story #50568030
loading story #50568925
SWEs also often forget that most of the software they create was designed to take jobs away from other people in other departments.
loading story #50567054
loading story #50574027
loading story #50567087
loading story #50568771
loading story #50568324
I'm an swe who opposes AI. I don't think we should be spending so much non-renewable sources of energy on AI. These energy sources are taking from our future.
loading story #50569441
loading story #50567003
loading story #50566689
loading story #50569400
Most of the SWEs I see opposing AI, are opposing it because it doesn't solve the problem. It creates patches that introduce more problems, faster, than if they just did it themselves.
I’m paid to be a meat proxy because our problems are trivial. The only thing i offer is writing the prompts that say “implement this” and “you overcomplicated x, make it simpler” occasionally including the way I want it fixed. Important steps in the process and skill and experience still help not pushing slop but I’m not really “solving problems” anymore.
loading story #50568326
SWEs aren't paid to solve problems (most of the time). They are paid because they are a necessary evil sitting between product owners and revenue. It doesn't actually matter that much if problems are solved. Their goal is to increase revenue, and there is not a linear correlation between solving problems and making revenue. Business leaders would absolutely love it if they could take a dump and have enough people buy their shit and eat it while not having to pay for the SWEs that they see as middle-men. If SWEs were paid merely to solve problems, the world would be a much different place. Corporate software engineering in the 2020s is as much about solving problems as advertising is about communicating the merits of a product.
loading story #50568530
I don't mind solving problems with AI. I'm worried about getting fired because they think they can do the job without me entirely.
SWEs where paid to solve problems by writing code.

Solving problems is not distinctive characteristic of a software engineer, doing it by writing code was.

loading story #50568241
We certainly solved the problem of companies having to hire as many of us or pay us as well.
Some people resent that the problems they used to solve were technical, but overnight, turned into managerial.
People who write comments like this forget that the product AI is selling is automated problem solving. In fact, generalized superhuman problem solving is the only way to justify their valuation.

Your comment is stating a belief that Anthropic will fail as a business.

If only. AI pilled SWEs seem to have not noticed that the only problem "building agents nobody needs" is solving is how to satisfy an investor with FOMO.

I never thought I'd miss the days when executives used to rabbit on about customer obsession but the new fashion of AI psychosis is worse in just about every way.

I hate this comment.

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.

born just in time to watch the singular thing i enjoy in life get automated away. I guess i get to be like every other person now and hate my job.
If you only liked the “writing code” part of software engineer, then maybe software engineering just isn’t the right thing for you. Luckily now is also the best time ever to explore alternative career paths! One of the amazing things about AI is how it’s lowering the barrier of entry into new fields.

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.

I enjoyed getting to solve problems elegantly and I still believe, even if it is old fashioned, that writing and understanding good code is essential to building the abstractions for and design of a good product. Except for maybe things like webdev, where looks good ~= is good, I feel like humans writing code is still the best way to do things, but I feel like I am in a growing minority and might just need to drop the field and become a welder or whatever.

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.

> If you only liked the “writing code” part of software engineer, then maybe software engineering just isn’t the right thing for you.

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.

I pretty much agree with the part about wrestling with the code. I'm not opposed to ai, but when I use it I use it as another opponent to wrestle against. Not as something to pump out code. AI has a place in software engineering, but I really think that, justifed or not, the way people think of and use AI at the moment is both less fun for me and detrimental to creating a good product as a whole.

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.

I appreciate both of your sentiment that we’re losing the human craftsmanship and connection to the code. I got into writing software because I like you also appreciate clean abstractions and puzzling out the best way to get the job done. I find your use of the phrase “wrestling with the code” particularly notable, because it’s struggle that leads us to understanding.

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.

>singular thing i enjoy in life

If coding was it, you have a more serious problem than AI

The person you replied that to spoke for themselves, I still want to add to this from my perspective: I find this to be quite judgemental and also not a reply in good faith. Regarding the latter: To me it's kind of clear that the statement is made with a certain hyperbole. To blame someone for not dissociating the work they do from their existence, in a somewhat cynic acceptance of the equating of work and labour, and that in a way, where the formulaic way the statement is put forward being suggestive of a common sense of normative agreement, reminds of the "discourse" along the lines of the commentsection in feed. And to me that's not exactly high minded and as legit as you trying to make it sound. Someone conceiving of what they do for a big, if not the biggest, part of time in this life as a profession and not just another job, is in my perception considered as an ideal (you might not share it and that's fine). To do as I preach here: I see a point in pointing out that it might be reasonable to address the misery that the hyperbole implies, with a different lever then trying to find a solution to the potential vanishing of said profession, since at this point in time, it's fair to at least consider the possibility, that fading away might indeed be its fate. Decided to articulate my sentiment, just to give backing to the person behind the anonymity of this platform, in the face of the sort of automatic discoursivity (as I perceive it, might also just be you..) that that arises from the (un-)culture a commentsection seems to evoke habitually sometimes.

edited some typos

What can I say, I liked my job.

(I'm excluding trivial, hedonistic things from what I enjoy)

> The real goal, however, will always be to solve real-world problems. Engineering consists of whatever gets you there most effectively.

Love this statement, 100% agree.

me also remembers when c++ was thought slow, so we were doing a mixture of C and assembly. it took my friends years to agree to java, then it took him 15 more to understand JS works better for him. happily it took him only 2 years (of convincing) that he should try LLMs and he's not so stubborn anymore :D
...and safely. Engineering has strong and rightful tradition in safety. Perhaps it is many times not as crucial as in the medical profession, but it is very important for engineers to understand and be able to mitigate risks that are associated with whatever they are building. You don't want your bridges to collapse or planes to fall out of the sky afterall.
It's not like engineering wouldn't do some heavy lifting in the domain of medicine.. Would you trust a machine learning system with producing a platform for robotically assisted laparoscopic surgery? What about running the whole process of developing medication (including pre-clinical safety testing?)(latter depending on whether you see pharmacology and biochemical engineering as belonging to the domain of engineering ofc). Funny thing on the side: Met a person once who was tasked with avoiding injuries through brown ice, by having a planes internal it system keep track of where they are and anticipate pressure on the system that might necessitate.. releasing that planes pressure mid-air, lol.
loading story #50572137
>I'm old enough to remember . . .

yep

Every higher level brought worse craftsmanship but more products. Nobody programs like Mel, they don't need to make Blackjack run on 2k drum memory but the same lack of mindset makes PC video games 300GB big.

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

I'm old enough to call you on your bullshit.

The best you can find is people claiming that it would reduce the amount of assembly people write, which was true. They also predicted programmers would lose their low level understanding of the machine. That was also true. They didn't predict anything about making human thought non-viable economically. And not one C compiler vendor said their product could cause human extinction.

If AI predictions have the same level of truth as C compiler predictions, then the doomers are right.

So what, specifically, are you calling them on?
I can't speak for them, however:

   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

The points of significant difference between Ye Olde Days and now is the numbers (absolute and proportional) of people affected, the speed with which they are affected, and the availability of related and meaningful work into which they can transition.

AI does not help stopping wars, ending poverty, solving climate wars.