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.
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
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!
[1]: Purely technical. There may be social reasons or legal consequences like "disparate impact" theories coming at you.
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.
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?
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.
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.
I wish you were correct. The trend is that nobody reads code anymore, AI writes it and people rubberstamp it with barely a glance (if even that, some companies might have AI rubberstamp it and off it goes into production).
My colleagues use the LLM to do that...
Unfortunately that means we may see more of these brain teaser / gauntlet style interviews.
Interviews are so hard
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.
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
If you like thinking, you can keep thinking. AI can't stop you from doing that unless you let it.
Been able to finally remove a really painful and bad ORM from a legacy codebase.
Not really, the problem is just changing. Just like C allowed developers to leverage a standard library and a checked type system to create software, AI is allowing developers to leverage english and verifiable specifications to create software. We're all still developing software per a set of requirements at the end of the day.
The varied implementations will always exist and the job is both picking the right requirements to work on, and delivering in a way consistent with its goals.
> 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.
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.
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.
border-radius could have knocked me out of the game, but I decided to keep going. And I'm glad I did.
I’m excited about what this next progression entails. I’m building complex software in months in a home lab that would have required millions in investment just five years ago. In five years I don’t think any of us can say for certain what the industry will look like.
4/5
Have you been able to translate that into a steady income?
SWEs who oppose AI seem to forget that they are paid to solve problems, not write code.
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.
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.
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.
Solving problems is not distinctive characteristic of a software engineer, doing it by writing code was.
Your comment is stating a belief that Anthropic will fail as a business.
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.
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.
FWIW I love not having to spend so much time writing code. I get to focus on solving problems for end users, which is way more fun and rewarding IMO.
It wasn't so much coding that I loved, although I do love that, but being able to build and understand something far greater than myself, and the puzzle of trying to find the right abstractions and tools to make something beautiful.
Boy am I getting tired of reading this sentence.
You make it sound like the only thing that's gone away is the physical act of entering characters -- completely ignoring the fact that working through the problem and wrestling with the code (which included, among other things, typing it) were one and the same. Removing the "writing code" part and expecting the other parts to remain is just as sensible as believing that you can remove a swimmer from the water and expect them to keep their physique.
"Writing code" was one of the most important _mediums_ through which we practiced _deep thought_ about programs. It wasn't just typing.
> FWIW I love not having to spend so much time writing code...
Sounds like maybe software engineering isn't for you? Or rather, wasn't? You're lucky that the "one thing" you don't like about your career was removed. Try and approach those of us who are in the opposite situation with a bit more tact and compassion than "Luckily now is also the best time ever to explore alternative career paths!" What an absurd, tone-deaf thing to say.
There have been many times recently where, by choosing not to have ai generate code that at first glance seemed like it would be repetitive and boring, I have developed much better and more elegant abstractions for what I was trying to do because by working through the code and wrestling with the problem I found a better way to do it.
However, I don’t believe (and never really did believe) that writing code is the only means to understanding how to build good programs. I think best in prose and pictures, so writing requirements docs and thinking through abstractions with component diagrams has been my preferred way to work for years. Maybe I am the lucky one…
Apologies for causing any upset, I really do not wish to cause ill feelings. I want to see our field of software engineering flourish, and if that means trading a screwdriver for a chisel I’m all for it.
If coding was it, you have a more serious problem than AI
edited some typos
(I'm excluding trivial, hedonistic things from what I enjoy)
Love this statement, 100% agree.
yep
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
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.
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.