Remix.run Logo
▲ marsten a day ago

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.

▲SomaticPirate a day ago | parent | next [-]

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

▲timr 21 hours ago | parent | next [-]

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

▲tgma 20 hours ago | parent | next [-]

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.

▲mlyle 18 hours ago | parent | next [-]

Sure, random cognitive tasks are correlates of technical job performance.

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 instead of picking something with positive correlation.

There are also tall people who are not great basketball players, and vice versa. If you can't do anything but measure height, maybe you should pick for your team that way... but if you aren't so restricted there's surely better ways to go.

▲tkamat29 17 hours ago | parent | next [-]

Why would you want to hone in on finding "good programmers" though? Programming is not the end-all be-all skill of being a good software engineer, this was true even before AI but is even more true now.

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.

▲timr 17 hours ago | parent | next [-]

> It gauges problem solving ability and pattern recognition, which are essential to any job, and particularly useful for software engineers.

Proof of claim required. 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.

There's an entire test-prep industry surrounding this interview method. Any undergrad will tell you that the way you pass leetcode interviews is to "grind". 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 a test of superficially relevant trivia is what you do. Even better if the trivia can be validated by computer!

Setting aside the fact that almost no companies actually had this problem outside of FAANG, thanks to AI, the approach has gone from "somewhat relevant" to "completely irrelevant" within a couple of years. It's time to take it out back and shoot it.

▲01CPMD3174 14 hours ago | parent | prev | next [-]

Leetcode is popular because it gives hiring teams an objective 1)getting people to self select out of the process and 2)shortlisting the people who do opt-in.

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.

▲filipdobro 16 hours ago | parent | prev | next [-]

Leetcode interviewing is popular because it barely requires any effort by the interviewer. It is a small, localized knowledge check of your DSA skills. No other profession requires you to invest this much time into the interviewing process. How about we look at past achievements, contributions and certifications, like in any other field?

▲TeMPOraL 14 hours ago | parent [-]

> How about we look at past achievements, contributions and certifications, like in any other field?

In other fields, those things aren't nearly as meaningless and easy to game as they are in ours.

▲filipdobro 10 hours ago | parent [-]

I don't agree with that. No mechanic shop will test if you actually know how to change the brakes of a car. They have to gauge it from the interview process without doing the actual work.

▲mlyle 5 hours ago | parent [-]

The mechanic shop will figure out you don't know what you're doing really, really quickly though. Whereas when we hire someone it's often much longer before we get quality feedback.

▲jjav 14 hours ago | parent | prev [-]

> Leetcode is popular because:

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.

▲tgma 14 hours ago | parent | prev [-]

Weeding out smart non-programmers is quite easy. Obvious by their resume and their non-coding interviews. I bet in an unlikely scenario that you fail to detect that, you probably have a pretty good hire who'll learn in a heartbeat.

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.

▲miroljub 14 hours ago | parent [-]

It's not. In 99,99% of programming jobs you will never have to implement a linked list. And yet, interviewers pretend it's important to be able to write it on the blackboard.

▲tgma 13 hours ago | parent [-]

Not the point. If you have way more applicants than roles and you are paying well, given the choice between a programmer who cannot implement a linked list [really?] and one who can, you would hire the one who has that ability, even if all they do all day is to stare at Claude Code.

▲montag 15 hours ago | parent | prev | next [-]

Leetcode is and has always been a conveniently disguised IQ test.

▲tptacek 6 hours ago | parent | next [-]

People love saying this, but it doesn't make any sense. There are software firms that, within the past 15 years, broadly screened all candidates with actual IQ tests. There's no reason to disguise them at all. The reason nobody in the industry does this is that we all know what a debacle it would be to screen primarily on IQ tests rather than "can people do the job effectively".

▲menaerus 14 hours ago | parent | prev | next [-]

It takes some IQ to solve leetcode problems but better performance of human A in comparison to human B does not say anything about their absolute IQ capabilities. It's a conveniently disguised test for attracting highly motivated individuals with average or more than average IQ and nothing else.

▲JustFinishedBSG 8 hours ago | parent | prev | next [-]

It's an absolutely terrible intelligence test.

It's basically just a grinded leetcode test.

▲oreally 6 hours ago | parent | prev [-]

[flagged]

▲oreally 6 hours ago | parent | prev | next [-]

Wrong.

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.

▲timr 19 hours ago | parent | prev | next [-]

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

▲boorang 18 hours ago | parent | next [-]

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

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.

▲timr 17 hours ago | parent [-]

I think it's a common story for anyone who has been around a while: you have a career (possibly even working for big, famous names) develop a long resume of accomplishments, and some dinky startup with a staff of teenagers rejects you via email because you didn't solve a leetcode hard problem while singing and dancing on zoom.

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.

▲tgma 19 hours ago | parent | prev [-]

Obvious strawman: is "coin flipping tournament" a "random cognitive task?"

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.

▲timr 19 hours ago | parent | next [-]

Yes, I changed it to a better metaphor before you wrote your comment. I had originally written "pub quiz", then changed it to "coin flipping contest" to emphasize the stupidity of the task, then changed it back, anticipating the criticism. The argument does not change -- the claim that testing coding trivia is a test of intelligence is a bald assertion.

Please use your intelligence to see the argument I am making, instead of nitpicking the example.

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

No, it isn't. Disparate impact is. Any test that has a disparate impact on a protected class is de facto illegal, but there's case law surrounding IQ tests.

By the way...ironically enough, Griggs v. Duke Power established that any intelligence test must have relevance to the job responsibilities, which sort of blows a hole in your entire theory of the case that this is a "classic fallacy".

https://en.wikipedia.org/wiki/Griggs_v._Duke_Power_Co.

▲kelipso 17 hours ago | parent [-]

> the claim that testing coding trivia is a test of intelligence is a bald assertion

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

▲timr 17 hours ago | parent [-]

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

▲tptacek 18 hours ago | parent | prev [-]

Not only is it not practically illegal, as the sibling commenter notes, but several household-name corporations openly IQ test candidates. General cognitive testing is presumptively lawful in white collar employment.

▲tgma 18 hours ago | parent [-]

Your pivot from "IQ test" in your first sentence to "general cognitive testing" in second is the whole point.

Leetcode is just one step away from that (and much more litigation-proof).

▲tptacek 18 hours ago | parent [-]

IQ tests are general cognitive tests. If your entire argument is that IQ tests are fine so long as you call them something else, you're not really saying anything.

Leetcode is not a general cognitive test, obviously.

▲tgma 18 hours ago | parent [-]

IQ tests are general cognitive tests. The opposite is not necessarily true.

The whole point of the multibillion dollar test industry is to fudge a "noisy" IQ[ish] test and make it look like it won't have disparate impact (validation "studied") and buy you some ass-covering ability.

> Leetcode...

"one step away"

▲tptacek 18 hours ago | parent [-]

Leetcode is a domain-specific test. It is the opposite thing to a general cognitive test. The entire point of IQ is the positive manifold: the notion that general cognitive tests are all monitoring the same latent variable.

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.

▲tgma 17 hours ago | parent | next [-]

[flagged]

▲ 17 hours ago | parent | prev [-]
[deleted]
▲Mawr 15 hours ago | parent | prev [-]

> This is a classic fallacy: that interview should look the same as the job.

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 "generic" test actually selects for ~all traits you want while also rejecting ~all traits you don't. I assure you, the chances of you having a good enough model of reality to do this are laughable. Pure arrogance.

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

I've seen someone suggesting that since a lot of programmers like playing Factorio, why not interview people by having them play Factorio? Ah, because then you're selecting for Factorio players. Do you have a good model of what makes a good Factorio player? Hell, do you have a good model of what makes a good performer at your job? You absolutely do not. Why select for Factorio players when you can select for your-job players?

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 — you get what you test for.

▲tgma 15 hours ago | parent [-]

> ...you get what you test for.

Multiple trillion dollar companies has not been that bad.

▲JackMorgan 11 hours ago | parent | prev | next [-]

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?

▲dingdongditchme 16 hours ago | parent | prev | next [-]

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.

▲blurjp 9 hours ago | parent | next [-]

[flagged]

▲timr 16 hours ago | parent | prev [-]

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.

▲dingdongditchme 14 hours ago | parent [-]

Isn't that the whole point of the process reduce the candidate pool to 1? Both cv and coding challenge open up quite different discussion. I am not only interested in the applicants past but also in the way he approaches problems (even if they are somewhat trite and not representative). More important to me is a third aspect for which we never really had a good test and that is "enthusiasm" for the job.

▲threatofrain 20 hours ago | parent | prev | next [-]

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.

▲timr 18 hours ago | parent [-]

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.

▲cortesoft 19 hours ago | parent | prev | next [-]

It was always stupid to do leetcode interviews

▲jjav 14 hours ago | parent | prev | next [-]

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

▲Betelbuddy 14 hours ago | parent | prev | next [-]

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

My colleagues use the LLM to do that...

▲ 20 hours ago | parent | prev | next [-]
[deleted]
▲Sateeshm 20 hours ago | parent | prev [-]

Reading and understanding code is not it either.

▲boorang 19 hours ago | parent | prev | next [-]

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

▲zdc1 21 hours ago | parent | prev | next [-]

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.

▲tesnorindian 18 hours ago | parent | prev | next [-]

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.

▲corrinavirus123 18 hours ago | parent | prev | next [-]

As a mid level dev who knows I can competently do the job I’m having the same problem :(

Interviews are so hard

▲8note a day ago | parent | prev | next [-]

expectations for juniors will change over time, ands university curricula for software engineering degrees with it

▲0c3ca83 a day ago | parent | prev [-]

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.

▲atherton94027 a day ago | parent | next [-]

Or more likely, the demand for seniors increases as managers realizes they cut off the supply of junior engineers

▲bonoboTP a day ago | parent | next [-]

A junior is unlikely to become a senior in your company so that argument doesn't bite. We are not 30-40 years ago when people stayed at one place for a decade or even their whole careers.

▲komali2 21 hours ago | parent [-]

> when people stayed at one place for a decade or even their whole careers.

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.

▲tezzer 21 hours ago | parent [-]

I'm going on 11 years at a robotics entity (minus a 2 year flyer at a FAANG for better lunches and stock) because I really love the work. I interview elsewhere a couple times a year to practice talking about myself and see if the grass is really greener, but if you like what you do and you're good at it, stopping the churn is pretty refreshing.

▲bonoboTP 18 hours ago | parent [-]

I hope you never complain about fake job postings with no real intention to hire, given that you do fake applications with no real intention to get hired.

▲com 17 hours ago | parent [-]

It is up to the interviews and interviewers to convince good candidates to join. Especially those who are in work and satisfied with their current position.

Nothing fake about these applicants, they’re just hard to convince.

▲0c3ca83 20 hours ago | parent | prev [-]

That sounds like some good copium.

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 reality is that staying in a job and shipping what the managers ask for takes less skill.

The question is how long it will take management to notice and decide to do the next round of layoffs.

▲akbarian 17 hours ago | parent [-]

Good, then we need less managers as they become dead weight. And what do we need you for?An agent can do your job soon aswell.

▲0c3ca83 14 hours ago | parent [-]

If AI works out as the AI companies predict, human thought is dead weight.

This is not a good thing.

▲tgma 19 hours ago | parent | prev [-]

I think a lot of what's attributed to AI re juniors (and everything else) is really the confounding effect of ZIRP ending. BigTech headcount growth stalled before LLM. A key point is that a "junior" engineer was really an apprentice. The decade before that, the big employers basically understood that they have to hire from universities and train employees themselves 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?

▲ultrarunner a day ago | parent | prev | next [-]

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.

▲bonoboTP 21 hours ago | parent | next [-]

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

▲lantry a day ago | parent | prev | next [-]

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.

▲NegativeLatency 19 hours ago | parent | prev | next [-]

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.

▲derangedHorse 19 hours ago | parent | prev | next [-]

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

▲StilesCrisis a day ago | parent | prev | next [-]

Really? I find the thinking is very different but I'm still keeping very busy. It's like never-ending PR review cycles.

▲hirvi74 20 hours ago | parent | prev [-]

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.

▲byronturncoat 18 hours ago | parent | next [-]

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.

▲hirvi74 29 minutes ago | parent [-]

> I think that you're searching for a correlation that does not exist.

I cannot provide evidence in favor or against my conjecture, so you very well may be correct.

> Perhaps they've read the numerous studies that have been published on the subject.

I feel it is necessary to push back on this point a bit. I will read any research you are willing to share, but from the studies I have happened to read, the "death of thought" would be a hyperbolic mischaracterization of observations. Most studies I can remember reading tend to measure performance on small, narrow sets of tasks. For clarification, what do you believe "death of thought" means? If you mean an atrophy in a particular skill being linked to outsourcing the skill to LLMs, then I am more inclined to agree with you. In other words, I do not disagree that using LLMs for any and all programming is linked to the atrophy of one's ability to program, but I would be more suspicious of claims that suggest that such usage of LLMs is linked to one's ability to think critically in many or most domains.

> Just because someone doesn't believe the same as you, it doesn't mean that they've got a fragile or damaged ego.

I am well aware. However, I never shared my opinions on whether I believe thought is dying or not, so I am not sure what disagreement you believe the OP and I have. I was merely sharing an observation that I have noticed amongst people I consider to be highly intelligent within my social circles. In hindsight, I can understand how the wording of some of my questions my be interpreted as subtly sharing a stance. Some people have a way with words, while others like me often struggle. My apologies.

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

Of course. That is true of any limited resource be it time, money, health, or what have you. Those that find themselves in such a situation have both my sympathy and empathy.

▲MiiMe19 18 hours ago | parent | prev [-]

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.

▲alexose a day ago | parent | prev | next [-]

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.

▲murukesh_s a day ago | parent | next [-]

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.

▲riddlemethat a day ago | parent | prev [-]

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.

▲alxmdev a day ago | parent | next [-]

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.

▲proxyscore 19 hours ago | parent | next [-]

Mobile layout came along

▲mitxela a day ago | parent | prev [-]

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

▲jimbokun a day ago | parent | prev [-]

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

▲sylos a day ago | parent | next [-]

It never does. And the software wila probably rot on the vine

▲blackqueeriroh 20 hours ago | parent | prev [-]

In what world does this need to be the point?

▲jimbokun 4 hours ago | parent [-]

In a world where people need to pay rent or their mortgage.

▲fomoz a day ago | parent | prev | next [-]

I love this comment.

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

▲truncate a day ago | parent | next [-]

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.

▲stinkbeetle a day ago | parent [-]

> You can't really say "lets think about it a bit" without becoming AI denier/opposer or whatever.

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.

▲truncate a day ago | parent | next [-]

>> You want other people to stop using productive tools?

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.

▲stinkbeetle a day ago | parent [-]

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

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?

▲lanstin a day ago | parent | prev | next [-]

You can go out and take a walk around the block/quad/building still. And come back knowing the exact prompt to use to find the true explanation for some puzzling data anomaly/code behavior/failure mode.

▲jimbokun a day ago | parent | prev | next [-]

> What does "lets think about it a bit" even mean though?

Don't push code no human has read into production.

▲stinkbeetle a day ago | parent [-]

Well I asked the OP, but appreciate your opinion and contribution too.

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

▲jimbokun 4 hours ago | parent [-]

Both.

▲wholinator2 a day ago | parent | prev | next [-]

Surely those aren't the only two options though? 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.

▲stinkbeetle 21 hours ago | parent [-]

> Surely those aren't the only two options though?

(EDIT) I didn't mean to imply those as only two options, just points of a spectrum.

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

▲Tanjreeve 17 hours ago | parent | prev [-]

I think ops point is the tools are irrelevant. What comes out is the only thing that matters. Making grandiose assumptions about the arc of history is the job of pundits and linkedin influencers.

▲dfdydx a day ago | parent | prev | next [-]

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.

▲stavros a day ago | parent [-]

The things that make me stand out at solving problems is that I can effectively convince machines to solve problems at massive scales.

▲rayiner a day ago | parent | next [-]

Okay, but what about all the guys whose marketable skill was just being able to connect database A to data sink B? Maybe these folks are underrepresented on HN. But there’s a lot of people who work on this sort of software.

▲Tanjreeve 17 hours ago | parent | next [-]

To me this makes AI sound more and more like the cloud. There was a lot of generic busywork before clouds got big too. But ETL at the level "lift and shift data" has been a solved problem for a decade or so now. But picking up commodity work has always been low effort high risk in career terms.

▲stavros a day ago | parent | prev | next [-]

Yeah, there are tons of those people, and I'm afraid they're going to go the way of the weavers after the loom was invented. I don't think there's a way to put that genie back in the bottle, sadly...

▲sylos a day ago | parent | next [-]

Everyone is now a member of the weaving business. AI exists to solve wages.

▲larodi a day ago | parent | prev [-]

in this regard we've been all wearing AI-generated textile for 200+ years now. come to think about it, humanity somehow survived, and it was so profitable a business for millennia, that people fought wars over its detail...

▲thmoonbus a day ago | parent | prev [-]

Do you know how many people “that sort of software” displaced just a few decades ago? Probably a lot…

▲dfdydx 15 hours ago | parent | prev | next [-]

I’d wager a lot of people not from software engineering will be just as good or better than software engineers for that, if only because most problems in business are business problems: Joe from accounting with a solid understanding of accounting and passable prompting might be better at solving accounting problems with AI than John the dev with limited accounting understanding but great effectiveness at pointing the AI towards wrong problems.

▲weatherlite 18 hours ago | parent | prev | next [-]

Yeah A.I is pretty good at that

▲jimbokun a day ago | parent | prev | next [-]

Now everyone can.

▲cluckindan a day ago | parent | prev [-]

I know the incantations to summon the daemon and bend it to my will.

▲dfdydx 15 hours ago | parent [-]

There are a lot more people able to do that than there were able to code.

▲bootwoot a day ago | parent | prev | next [-]

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.

▲marcus_holmes a day ago | parent [-]

This. The JIRA mills where folks log in, say "no blockers" in a half-hour standup, fix an endless stream of tickets, then log off and go do what they actually want to do. That's over, thankfully.

▲debugnik a day ago | parent | prev | next [-]

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.

▲kelnos a day ago | parent | prev | next [-]

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.

▲gojiberries a day ago | parent | next [-]

System design has always been the most important and interesting part of software development. Now you can do that at a scale never seen before, it’s awesome.

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.

▲detourdog a day ago | parent | next [-]

The question is how much software needs to be that scaleable? Besides graphics presentation most human problems wouldn’t scale past an 8 bit computer.

▲bluecheese452 a day ago | parent | prev [-]

No it hasn’t.

▲marcus_holmes a day ago | parent | next [-]

There used to be whole rooms of clerks doing double-entry book-keeping at every bank branch.

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.

▲somenameforme a day ago | parent | next [-]

Computers [1] themselves are perhaps the best example. Digital computers were so completely effective at obsoleting human computers that I think most don't even realize this used to be a profession, though it's quite obvious if you think about it. When even just relatively basic calculations would have taken so much time, nobody would have ever been able to get anything done if they were having to constantly do all the 'computing' themselves.

I suspect programming will be similarly forgotten in the future when any program can be concocted trivially and efficiently by description alone.

[1] - https://en.wikipedia.org/wiki/Computer_(occupation)

▲marcus_holmes 21 hours ago | parent [-]

Well, we'll still have folks hobby-coding, because some of us enjoy doing that.

Much like potters used to be a profession that was needed in every community, and now they're "ceramic artists"

▲bluecheese452 10 hours ago | parent | prev [-]

Was replying to the first part.

▲wholinator2 a day ago | parent | prev [-]

It's amazing how people tend to view their personal experience as the norm. Even down to interests.

▲tempest_ a day ago | parent | prev [-]

That can be interesting but LLMs can do system design fine. Sure it can make crap but it doesn't take 10 years of experience to learn the 50 or some prompt variations to get it to sort things out. As time goes on those will be baked into the harness.

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.

▲threetonesun a day ago | parent | prev | next [-]

SWEs also often forget that most of the software they create was designed to take jobs away from other people in other departments.

▲cheesewhistle a day ago | parent | next [-]

The frame often is positioned to include yourself and your own interests at the center of it.

▲pydry a day ago | parent | prev | next [-]

When a pawn on a chessboard takes a piece is do you blame the pawn or the chess player?

Software devs were guilty of wanting one of the few middle class jobs left. Nobody enters the profession cackling evilly about how many jobs they will take.

▲gojiberries a day ago | parent | next [-]

> Nobody enters the profession cackling evilly about how many jobs they will take.

Capital has historically and enthusiastically done exactly that.

▲MatekCopatek a day ago | parent [-]

The parent comment isnt trying t9 deny that, they're just saying the employer should be held accountable more than the worker.

▲somenameforme a day ago | parent [-]

You think the employer just signed up to the evil club before starting his business? People start businesses because they have a neat idea or because they hope to make a better life for themselves. No different than a worker except in the path taken.

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.

▲Timwi 21 hours ago | parent [-]

> You think the employer just signed up to the evil club before starting his business?

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.

▲somenameforme 21 hours ago | parent [-]

This doesn't even make any coherent sense. I have a bunch of apple trees in my back yard. I hire a a few guys to go harvest them and then sell them to a bakery which eventually turns them into apple pies, who in the world is getting exploited?

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. some employer trying to undercut somebody's pay or whatever.

▲arximboldi 20 hours ago | parent | next [-]

can the people that harvest the apple trees afford a house with a backyard large enough for a bunch of apple trees? perhaps exploitation has too overreaching connotations, but there is an inherent imbalance of power in the relationship that leads to systemic inequalities.

▲tarsierscripter 19 hours ago | parent | next [-]

Without ownership of property you just have a commons, where everyone picks all the apples off the trees, and then someone comes along with an axe and cuts the trees down for firewood, and then there's no more apples or apple pie for anyone.

▲somenameforme 17 hours ago | parent | prev [-]

You're making a lot of assumptions about the owner that often don't really pan out. For example I have less than zero love for the Waltons but Walmart is just such a great example. Their gross profit margin is about 24%. That's how much they profit on each item sold. But then after you factor in their operating costs, labor in particular, it's down to 3%.

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.

▲Timon3 11 hours ago | parent [-]

I think it's telling that you're pointing at Walmart's margin without pointing out 1) what percentage of the operating costs are down to labor, and 2) how much wages could be raised using those 3%.

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

▲somenameforme 9 hours ago | parent [-]

I'm not saying their percent of labor costs because it's not public information. It's buried in operating expenses, but it's going to be the majority of their costs, by a wide margin. Fortunately your other question is much easier to answer. 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.

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

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.

▲Timon3 9 hours ago | parent [-]

> I'm not saying their percent of labor costs because it's not public information. It's buried in operating expenses, but it's going to be the majority of their costs, by a wide margin.

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?

▲somenameforme 8 hours ago | parent [-]

60% of your operating expenses being labor is pretty typical for a labor heavy industry, and WalMart's kind of the epitome of labor heavy with some 2.1 million workers. Their most recent reported operating expense was $148billion. If we assume 50% of that's labor that'd imply an average labor cost per employee of 148,000 * 0.5 / 2.1 = $35k. That's likely a significant lowball figure so the typical 60%+ is a reasonable ballpark.

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.

I think people just don't intuit how huge the world is and so how bizarre things get at scale. If you could earn just $1 from every person on Earth you'd be a multi billionaire. Even if you just limit yourself to Europe and the US, you'd be a billionaire. This sounds absurd, but it's true. It's because our intuition is just worthless for sufficiently big numbers.

▲pydry 15 hours ago | parent | prev [-]

>have a bunch of apple trees in my back yard. I hire a a few guys to go harvest them and then sell them to a bakery which eventually turns them into apple pies, who in the world is getting exploited?

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.

▲somenameforme 11 hours ago | parent | next [-]

You've yet to explain how or why anybody is being exploited, and instead are just engaging in circular logic-> 'employment is exploitation' -> 'how is this employment exploiting anybody?' -> 'because employment is exploitation.'

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.

▲pydry 7 hours ago | parent [-]

unequal land ownership is what made employment exploitative in that example.

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.

▲badpun 10 hours ago | parent | prev [-]

Take two people. One saved for 30 years and bought a small piece of land. The other one partied for 30 years, and always spent his entire surplus and ends up with no capital. It's true that now the saver can "exploit" whoever rents from him, but at the cost of previously exploiting himself during the previous 30 years to build capital.

▲danhodgins 9 hours ago | parent [-]

Third guy had a silver spoon, didn't have to work to build capital, and spent the next 30 years partying with the other guy.

▲badpun 8 hours ago | parent [-]

That's an issue with inheritance, not capitalism.

▲threetonesun a day ago | parent | prev [-]

Some did. Many pled willful ignorance because computers were fun to tinker with. Given some of the terms outlined in this IPO I feel like anyone who made a lot of money today did so cackling.

▲dzonga 11 hours ago | parent | prev | next [-]

in my 30ish years of existence I haven't seen software take away people's jobs. transform yeah but take way jobs ?

unless when combined with robots.

▲andersonpico a day ago | parent | prev | next [-]

I've always said that software developers are the perfect middle class for capital: they never fight for their own interests and find it fun to put down their peers as a pastime. Even then, capital came gunning for them and then what did they do? Beg "HARDER, I'M NOT LIKE THE OTHER WORKERS". It's incredible really.

▲georgemcbay a day ago | parent | prev [-]

> SWEs also often forget that most of the software they create was designed to take jobs away from other people in other departments.

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.

▲Peaches4Rent a day ago | parent | prev | next [-]

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.

▲nl 21 hours ago | parent | next [-]

I'm very pro-AI but I also think we should be using this opportunity for energy transition.

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.

▲AgentME a day ago | parent | prev | next [-]

A developer's energy use from AI is generally tiny compared to their energy use from driving or eating meat.

▲mcv a day ago | parent | next [-]

Those are also things we should do less, but they're more ingrained and it's a lot harder to get people to stop doing that. Requiring green energy for all those data centers seems a lot more feasible, and would still help a lot.

▲bobsomers a day ago | parent | prev | next [-]

An individual's use is low, but when everyone's use is concentrated in a few communities it absolutely destroys those communities for the people that live there.

▲adwn 16 hours ago | parent | next [-]

That sounds like hyperbole to me. Which communities have been "absolutely destroyed" by an AI data center? I take "absolutely destroyed" to imply "literally unlivable", so if a community isn't literally unlivable, it can't have been absolutely destroyed.

▲AlphaCerium 12 hours ago | parent [-]

There's a lot of misinformation about data centers, and they're absolutely not "stealing our water", but operators frequently pollute water supplies through negligence, and the constant drone of generator noise is literally unliveable I would say. Claude found these articles for me with only a cursory search, so take them with a grain of salt, but there are real cases of them being a blight on communities. https://fieldreport.caes.uga.edu/publications/B1600/how-data... https://www.forbes.com/sites/victoriaforster/2026/07/09/meta... https://www.wftv.com/news/i-literally-just/UU6AMKIYRM6JLBTX7...

▲ a day ago | parent | prev [-]
[deleted]
▲vips7L a day ago | parent | prev [-]

What aboutism. You should stop eating meat too.

▲AgentME a day ago | parent [-]

I've skipped a few burgers this year. That will have made a bigger difference in my energy footprint than me using AI or not.

▲anonreplier a day ago | parent | next [-]

have you tho

▲vips7L a day ago | parent | prev [-]

Great now never eat a burger again and lmk.

▲preg_match a day ago | parent | prev | next [-]

The energy used by AI is, frankly, negligible. The water too. It’s a rounding error as compared to agriculture and manufacturing. The water use of all AI data centers combined doesn’t even reach the change in water usage over the past year for agriculture. Never mind the base usage, which is orders of magnitude greater.

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.

▲scott_weber an hour ago | parent | next [-]

For now. Atm all compute is like 1% of global energy usage. Until hyper scalers want to 100x their energy spend, which they'll might need to get AGI (to get a step change in capability for along scaling law lines, you need both 10x model size and 10x training data, 100x as much computation. They probably want at least 2 more step changes, so even assuming they 100x efficiency again, there's another 100x that needs raw compute hence energy). Then we're doubling global energy usage.

▲whiplash451 a day ago | parent | prev [-]

AI is a rounding error next to steel, cement, chemicals and food but calling its energy usage negligible is wrong in two ways: (1) it’s one of the fastest-growing sources of demand, and grid planning is driven by growth, not by share (2) it's highly concentrated -- in places like Ireland or Northern Virginia, data centres already use a double-digit share of local electricity.

▲CamperBob2 21 hours ago | parent | prev [-]

Success at developing AI will save more energy than you can imagine. Half the cars on the road won't need to be there, if nothing else.

Edit: never mind what you don't want to see happen: what do you want to see happen?

▲platevoltage 19 hours ago | parent | next [-]

Half the cars on the road already don't need to be there. We put more resources into bootleg taxicabs and driverless vehicles than a functioning transit system.

▲defrost 21 hours ago | parent | prev [-]

That's the upside of broadscale destruction of livelihoods, sure.

▲shakna a day ago | parent | prev | next [-]

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.

▲denkmoon a day ago | parent | prev | next [-]

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.

▲hirvi74 a day ago | parent [-]

You are solving the problem of someone else having to do that exact task.

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.

▲elcritch a day ago | parent | next [-]

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

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.

▲denkmoon 19 hours ago | parent | prev [-]

While I agree with what you’re saying and see the logic of it, it’s not exactly satisfying :/

▲ravenstine a day ago | parent | prev | next [-]

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.

▲dmz73 a day ago | parent [-]

Every single person, every product, every single "cost centre", everything is the necessary evil between "owners" and revenue. We should just optimize it all away and let "owners" print their money to infinity since that is the only thing they value and there is no need for anyone else to stand in their way by reducing their revenue. Of course, their money will be worthless but why is that a problem, they have it all! On the other hand, if you take the view that "economy" and therefore companies and products exist to help people then value != money. SWEs as they exist now already belong to 2 groups - "code shovellers" and problem solvers - same as any profession. LLMs can be used to shovel more code or help solve problems, most people will just shovel code (just look at python or javascript ecosystems) and few will continue to solve problems. Once LLMs can shovel code well enough then they will replace all other "code shovellers" but LLMs will never be able to solve problems, at least not on the same level as people. But I am sure that will not stop "owners" from thinking they can so every profession will be obsolete. Then there are two alternatives - everyone becomes a slave or we enter "Star Trek" style universe. I know which alternative is more likely (remember "Star Trek" is fiction).

▲Timwi 21 hours ago | parent [-]

> remember "Star Trek" is fiction

But so are all the cyber enslavement stories.

▲8n4vidtmkvmk 18 hours ago | parent | prev | next [-]

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.

▲croes a day ago | parent | prev | next [-]

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.

▲ravenstine a day ago | parent [-]

"Solving problems" is a meaningless thing to say, and seems to be the next evolution of "full-stack engineer". It's a result of dissolving what used to be a specialty with its own subspecialties. Make the role of an engineer as generic as possible so they become interchangeable, easier to replace, and eliminated when possible.

Plenty of software engineers are paid to not solve problems. Some are, but I would say that most are paid to do the thing. Orgs beyond the startup phase don't actually like problem solving because it introduces risk of instability. Just doing the thing isn't the same thing as solving problems. Business leaders would be very happy if they could eliminate the human from the doing the thing step, and not all of us can simply become the problem solvers because that's infeasible.

▲pesus a day ago | parent | prev | next [-]

We certainly solved the problem of companies having to hire as many of us or pay us as well.

▲vkou a day ago | parent | prev | next [-]

Some people resent that the problems they used to solve were technical, but overnight, turned into managerial.

▲0c3ca83 a day ago | parent | prev | next [-]

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.

▲pydry a day ago | parent | prev | next [-]

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.

▲rewgs 18 hours ago | parent | prev [-]

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.

▲MiiMe19 19 hours ago | parent | prev | next [-]

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.

▲gmassman 18 hours ago | parent | next [-]

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.

▲MiiMe19 18 hours ago | parent | next [-]

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.

▲rewgs 18 hours ago | parent | prev [-]

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

▲MiiMe19 18 hours ago | parent [-]

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.

▲gmassman 8 hours ago | parent [-]

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.

▲RAWGOD 18 hours ago | parent | prev [-]

>singular thing i enjoy in life

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

▲NonHyloMorph 16 hours ago | parent | next [-]

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

▲MiiMe19 18 hours ago | parent | prev [-]

What can I say, I liked my job.

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

▲gdorsi a day ago | parent | prev | next [-]

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

▲larodi a day ago | parent | prev | next [-]

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

▲dingdongditchme 16 hours ago | parent | prev | next [-]

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

▲NonHyloMorph 15 hours ago | parent [-]

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.

▲dingdongditchme 14 hours ago | parent [-]

I don't know what brown ice is. Sounds interesting though. When I talk of engineering, software engineering is only a small subdomain but yes medical devices are notorious for their... let's call it tongue in cheek "safety moat" ;-)

▲Pokepokalypse 19 hours ago | parent | prev | next [-]

>I'm old enough to remember . . .

yep

▲mitxela a day ago | parent | prev | next [-]

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

▲0c3ca83 a day ago | parent | prev | next [-]

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.

▲AnimalMuppet a day ago | parent [-]

So what, specifically, are you calling them on?

▲defrost a day ago | parent [-]

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.

▲complex_pi a day ago | parent | prev [-]

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