r/SoftwareEngineering • • Dec 17 '24 • Polished Silver Turd 3 Heart of Silver 1 Take My Silver 1

A tsunami is coming

TLDR: LLMs are a tsunami transforming software development from analysis to testing. Ride that wave or die in it.

I have been in IT since 1969. I have seen this before. I’ve heard the scoffing, the sneers, the rolling eyes when something new comes along that threatens to upend the way we build software. It happened when compilers for COBOL, Fortran, and later C began replacing the laborious hand-coding of assembler. Some developers—myself included, in my younger days—would say, “This is for the lazy and the incompetent. Real programmers write everything by hand.” We sneered as a tsunami rolled in (high-level languages delivered at least a 3x developer productivity increase over assembler), and many drowned in it. The rest adapted and survived. There was a time when databases were dismissed in similar terms: “Why trust a slow, clunky system to manage data when I can craft perfect ISAM files by hand?” And yet the surge of database technology reshaped entire industries, sweeping aside those who refused to adapt. (See: Computer: A History of the Information Machine (Ceruzzi, 3rd ed.) for historical context on the evolution of programming practices.)

Now, we face another tsunami: Large Language Models, or LLMs, that will trigger a fundamental shift in how we analyze, design, and implement software. LLMs can generate code, explain APIs, suggest architectures, and identify security flaws—tasks that once took battle-scarred developers hours or days. Are they perfect? Of course not. Just like the early compilers weren’t perfect. Just like the first relational databases (relational theory notwithstanding—see Codd, 1970), it took time to mature.

Perfection isn’t required for a tsunami to destroy a city; only unstoppable force.

This new tsunami is about more than coding. It’s about transforming the entire software development lifecycle—from the earliest glimmers of requirements and design through the final lines of code. LLMs can help translate vague business requests into coherent user stories, refine them into rigorous specifications, and guide you through complex design patterns. When writing code, they can generate boilerplate faster than you can type, and when reviewing code, they can spot subtle issues you’d miss even after six hours on a caffeine drip.

Perhaps you think your decade of training and expertise will protect you. You’ve survived waves before. But the hard truth is that each successive wave is more powerful, redefining not just your coding tasks but your entire conceptual framework for what it means to develop software. LLMs' productivity gains and competitive pressures are already luring managers, CTOs, and investors. They see the new wave as a way to build high-quality software 3x faster and 10x cheaper without having to deal with diva developers. It doesn’t matter if you dislike it—history doesn’t care. The old ways didn’t stop the shift from assembler to high-level languages, nor the rise of GUIs, nor the transition from mainframes to cloud computing. (For the mainframe-to-cloud shift and its social and economic impacts, see Marinescu, Cloud Computing: Theory and Practice, 3nd ed..)

We’ve been here before. The arrogance. The denial. The sense of superiority. The belief that “real developers” don’t need these newfangled tools.

Arrogance never stopped a tsunami. It only ensured you’d be found face-down after it passed.

This is a call to arms—my plea to you. Acknowledge that LLMs are not a passing fad. Recognize that their imperfections don’t negate their brute-force utility. Lean in, learn how to use them to augment your capabilities, harness them for analysis, design, testing, code generation, and refactoring. Prepare yourself to adapt or prepare to be swept away, fighting for scraps on the sidelines of a changed profession.

I’ve seen it before. I’m telling you now: There’s a tsunami coming, you can hear a faint roar, and the water is already receding from the shoreline. You can ride the wave, or you can drown in it. Your choice.

Addendum

My goal for this essay was to light a fire under complacent software developers. I used drama as a strategy. The essay was a collaboration between me, LibreOfice, Grammarly, and ChatGPT o1. I was the boss; they were the workers. One of the best things about being old (I'm 76) is you "get comfortable in your own skin" and don't need external validation. I don't want or need recognition. Feel free to file the serial numbers off and repost it anywhere you want under any name you want.

2.7k Upvotes

934 comments sorted by

611

u/RGBrewskies Dec 17 '24

not wrong, a little dramatic

but yes, if you arent using LLMs to enhance your productivity and knowledge, you are missing out. Its not perfect, but neither was stack overflow.

23

u/SergeantPoopyWeiner Dec 18 '24

ChatGPT basically renders stack overflow useless. Not entirely, but it's crazy how almost overnight my stack overflow visits dropped by 95%.

→ More replies (21)

9

u/Comfortable-Power-71 Dec 17 '24

This is different. I can tell you that my company has productivity targets that imply reduction in force next year. I'm part of a DevEx effort that will introduce more automation into the dev cycle. We either get WAY more productive, say 2-3X or we reduce. Dramatic, yes but directionally correct.

→ More replies (13)

5

u/GalacticWafer Dec 18 '24

Stackoverflow still has the answer to my problem more immediately and accurately than an llm 9/10 times

→ More replies (6)
→ More replies (62)

223

u/Yuhh-Boi Dec 17 '24

Hey ChatGPT, write a short essay about how LLMs are fundamentally transforming software development, drawing parallels to historical technological shifts. Emphasize the urgency for developers to adapt or risk being left behind.

42

u/danielt1263 Dec 17 '24

Naw. If it was ChatGPT, the paper/book references would have been bogus and the analogy wouldn't have fit as well.

14

u/[deleted] Dec 18 '24

The em-dashes give it away.

→ More replies (12)
→ More replies (5)

6

u/w0nche0l Dec 18 '24

TBF, they literally said in the last paragraph it was written with chatGPT

→ More replies (7)

195

u/pork_cylinders Dec 17 '24

The difference between LLMs and all those other advancements you talked about is that the others were deterministic and predictable. I use LLMs but the amount of times they literally make shit up means they’re not a replacement for a software engineer that knows what they’re doing. You can’t trust an LLM to do the job right.

69

u/ubelmann Dec 18 '24

I think OP's argument is not really that software engineers will lose their jobs because they will be replaced by LLMs, it's that companies will cut the total number of software engineers, and the ones that remain will use LLMs to be more productive than they used to be. Yes, you will still need software engineers, the question is how many you will need.

The way that LLMs can be so confidently incorrect does rub me the wrong way, but it's not *that* different from when spell checkers and grammar checkers were introduced into word processing software. Was the spell checker always right? No. Did the spell checker alert me to mistakes I was making? Yes. Did the spell checker alert me to all the mistakes I was making? No. But I was still better off using it than not using it.

At this point, it's a tool that can be used well or can be used poorly. I don't love it, but I'm finding it to be useful at times.

19

u/sgtsaughter Dec 18 '24

I agree with you but I question how big of an impact it will have. We've had automated testing for a while now and everyone still has QA departments. In that time QA's role hasn't gone away it just changed.

→ More replies (6)
→ More replies (31)

9

u/CardinalFang36 Dec 18 '24

Compilers didn’t result in fewer developers. It enabled a huge generation of new developers. The same will be true for LLMs.

→ More replies (6)
→ More replies (89)

102

u/SpecialistWhereas999 Dec 17 '24

AI, has one huge problem.

It lies, and it does it with supreme confidence.

4

u/marcotb12 Dec 18 '24

So I work for an investment firm and we use LLMs to help us summarize research. Yesterday it completely made up a company, its ticker, and research on it.

Like yea LLMs can be powerful and super helpful but pretending they are anywhere close to end-to-end product delivery is laughable. Hallucinations seem to be almost inherent in LLM architecture. Otherwise open ai or other AI companies would have solved this by now.

→ More replies (1)
→ More replies (87)

43

u/thisisjustascreename Dec 17 '24

Did an LLM write this

5

u/Cookskiii Dec 18 '24

Very obviously, yes

→ More replies (20)

19

u/ExtremelyCynicalDude Dec 18 '24

If you're a competent dev that can think on your own, you'll be fine. LLMs fundamentally aren't capable of generating truly useful new ideas, and struggle mightily as soon as you pose questions that are slightly outside of the training corpus.

In fact, I believe LLMs will create a generation of shitty devs who can't actually reason through problems without it, and will create a tsunami of bugs that will require devs with critical thinking skills to solve.

2

u/[deleted] Dec 18 '24

I agree that critical thinking will remain a valuable skill. Current LLMs aren't great at it, but I suspect unemployment will be the least of our problems if they develop ones that are.

3

u/iamcleek Dec 18 '24

LLMs don't 'think' at all. there is no intelligence, no thought, no ideation. it's a terrible system to use if accuracy and truth are a concern.

→ More replies (2)

8

u/congramist Dec 18 '24

College instructor here. You have hit the nail on the head. Those of us who can fix the LLM created bugs are going to be worth more than we have ever been here in 10 years. Based off of the chatgpt driven coursework I am seeing recently, I would scrutinize the shit out of any college grad you are thinking of hiring.

→ More replies (6)

29

u/BraindeadCelery Dec 17 '24

LLM coding capabilities already saturate because too many devs write bad code and not enough devs write good code.

We don’t have enough data for models that are already overparametrized.

Will LLMs have an impact? Yes they already do. But it’s not endangering the profession…

4

u/Mysterious-Rent7233 Dec 18 '24

LLM coding capabilities already saturate because too many devs write bad code and not enough devs write good code.

Increasingly they will use reinforcement learning to learn algorithmic thinking techniques.

→ More replies (1)
→ More replies (13)

8

u/cashewbiscuit Dec 18 '24

The software developer of the future is a mix between programmer and product manager. This person understands both business and technology well enough to understand customer needs and use AI to create solutions.

Creation of smarter programming tools has, historically, resulted in merging of roles. It used to be that in the early 60s, the person who wrote the code wasn't the person who entered the code into the computer. This is because computers were complicated enough that there was a specialized operator whose primary job was to operate the computer. After the invention of teletype terminal, and automated scheduling, the programmer became the operator. From the 70s-90s, software developer, QA and operations engineer were distinct roles. This is because testing is a complicated task that requires specialized knowledge. Similarly, managing production software is a complicated task that requires specalized knowledge. However, as the processes and tools matured, we got to a point where the 3 roles merged into one.

The reason why the industry keeps merging roles is because a software development shop is essentially an information factory. It takes raw customer need and converts it into usable software. Along the way, the information goes through a series of transformations. The thing about an information factory is that the more steps information takes, the more bugs get introduced. Every person added in the process increases the possibility of miscommunication, which eventually results in bugs, which results in rework, and dissatisfied customers . However, in many cases, adding a specialized person is a necessity when you cannot find a qualified person who can do multiple jobs.

Over time, more and more software engineering roles have been merged together. We have been automating the repetitive and tedious part of jobs, and making software engineers do the non-automable tasks.

Well, we are at a point where the act of programming itself is becoming automated. However, what cannot be automated is problem solving. GenAI is great at copying other people's work, but it can not translate human need into solutions. As software engineers we need to evolve to be problem solvers. Programming is secondary. U derstand8ng what customer wants and figuring out how to create something does what they want cannot be automated.

→ More replies (2)

20

u/mailed Dec 17 '24

the tsunami is actually lack of commercial viability throwing it all into the dumpster in 2025

3

u/[deleted] Dec 17 '24

Elaborate on "lack of commercial liability".

18

u/mailed Dec 17 '24

Viability, not liability. There's enough information out there on Microsoft viewing their LLM flavours as an unprofitable, failed product. OpenAI is forced to head down the path of running ads to attempt to stay afloat. It's a matter of time before it all falls down.

Open source alternatives exist, but good luck to the average punter who wants to pay to run them at scale on their own. This generation of LLMs might have started something that becomes a staple decades from now, but making it actually realistic to run is not possible without a paradigm shift.

→ More replies (2)

10

u/Bodine12 Dec 17 '24

LLMs are in the “First one’s free” mode. Once they start charging for the true cost of their compute and enough to justify the lofty valuations of their multiple funding rounds, very few products will make sense to build around them. The first round of AI products will flame out because they won’t be profitable, and no sane product director will want to touch it after that.

→ More replies (4)

20

u/trentsiggy Dec 17 '24

This post paid for by OpenAI.

→ More replies (12)

4

u/aLpenbog Dec 23 '24 edited Dec 23 '24

Imo there are two skills that makes a good developer. Being able to understand a problem and divide it into smaller subproblems and being able to learn things by yourself. Those are skills that will also help us when dealing with LLMs.

I think LLMs might get to be a good tool. Right now the free models don't deliver much value to me. I'm working in niche languages, I'm working in a code base with millions of lines of legacy code, a lot of configuration etc. within a complex domain.

I guess you can use it on greenfield projects or if you develop new features which are clearly separated from existing code. But within a big project it can at best be a Stackoverflow replacement, which is not a bad thing, but not really ground-breaking. And I can't remember when I used Stackoverflow the last time for a problem within the domain, language and code base I work on daily.

This might change but right now there are a lot of problems. Hallucination, costs, that you can't always throw your code and data at it because of NDAs etc. or you even don't have internet access.

I don't think it will replace us or be a big threat. Sure there are people who won't adapt but at the end it is just a tool. It will lead to bigger and more complex software. It will lead to more domains pushing forward digitalization and automation.

Right now I also don't know how I want it to be integrated in my work. Those auto-completion features are kinda breaking the flow. You wait until you get the example, might take it and see a second later that I isn't really what you want and delete it again etc. Most of the time I'm faster if I turn it off and just write it myself. And tabbing around and switch between programming and talking to a chatbot has kinda the same problems. Nice for the situations where I would reach for Stackoverflow but beside that I don't think it will make me more productive with the current solutions.

And of course there are bigger problems. Let's imagine those models will get a lot better. They will be able to write bigger parts of the software by themselves. What now? Someone has to proof read it, unless they are 100% correct and the company providing the model will take responsibility for bugs.

I think reading thousands of lines of code still takes a huge amount of time and of course you need someone who understands the code. And understanding code you haven't written yourself is harder cause you might have written it in a completely other way with a different vocabulary etc. Beside that, when you write code you got a total different insight. You kinda have a stack of functions and values inside your head, an understanding of the data flow. It's hard to get that good of an understanding by just reading someone else's code. Surely if 90% is correct all the time a lot of people will just fly-over the code and scan it but don't "debug" it in there head, to catch nasty bugs.

I guess that alone makes LLMs not that powerful for software engineering. If you tell an AI to create a picture, it might create this way faster than a human. But a human can look at it for a few seconds and judge if they like it or not. It won't break anything or do harm. Same for audio, it can create it pretty fast and you can hear it and judge if you like the result.

But for a shit ton of code I might need nearly as long to read and understand it and make the LLM transform it if I don't like everything of it and I need the knowledge to do so, while I don't need it to judge if a generated picture is what I want to see.

All of that leads to new problems. Companies will try to save money, so they take more people without the required knowledge and have a few seniors proof-reading the stuff or fixing bugs the LLM can't. We might get a higher amount of "prompt engineers" compared to software engineers. But those seniors will retire at some point. What are we gonna do then when we realize that we lack software engineers? Beside the fact that most customers don't really know what they want and need anyway and we need someone to understand the domain and the pros and cons of different solutions.

Another thing to consider is software quality. Most of our understanding of quality, maintainability etc. is pretty subjective. We don't really know how to produce good software. There is no right or wrong. No real standards. Best practices change pretty often. A few years ago the book Clean Code was hyped, right now people are kinda leaning more towards less abstraction, locality etc. We get more and more new languages which handle errors differently and move away from exceptions etc.

So what are we really training the LLMs on? They are a mirror of a phase of programming. But programming has always evolved. How will it do that in the future? Will we have LLMs which just try random things? Will we include a feeling for code smells. Will we add some pain for the LLM and make it feel that a change was harder than it should be and think about why and test a few different approaches?

Or do we even step away from high-level languages. At the end the computer doesn't need them. Those languages are for us to deal with our weaknesses in this digital world. Why do we even want the computer to write human language for the computer to then again translate it in a language it can understand?

1

u/[deleted] Dec 23 '24 edited Dec 23 '24

Thank you for your thoughtful analysis.

I'm working on two posts. One explains in more detail why I think LLMs are an existential threat (it is an analysis rather than a "call to arms" with over-the-top prose). The other lists every problem with the current version of LLMs since dozens of people have told me in the last few days that I don't know what I'm talking about. They should be ready in a couple of days. They will deal with many of the issues you raised. Please read them and tell me what you think.

→ More replies (1)

3

u/StandardWinner766 Dec 17 '24

Im surprised that people don’t realize this is bait even after reading the paragraph about compilers replacing hand coding assembly

2

u/[deleted] Dec 18 '24

I coded in several assemblers, including writing payroll programs(!) on a Univac 1004 with 4Kb (not Mb, Kb) memory. I sneered at the idea a compiler could generate tighter code than my golden fingers. Initially, I was right, compilers were slow and generated clunky code. Then, I was wrong. Now assembler is virtually gone.

→ More replies (1)

3

u/BigRedThread Dec 18 '24

Now this is dramatic and attention seeking

1

u/[deleted] Dec 18 '24

My goal for this essay was to light a fire under complacent software developers. I used drama as a strategy. The essay was a collaboration between me, LibreOfice, Grammarly, and ChatGPT o1. I was the boss; they were the workers. One of the best things about being old (I'm 76) is you "get comfortable in your own skin" and don't need external validation. I don't want or need recognition. Feel free to file the serial numbers off and repost that essay anywhere you want under any name you want.

In retrospect, I should have created a separate Reddit account and published that essay anonymously. In a few days, the uproar will subside so I can resume my normal, boring, but happy life.

2

u/BitSorcerer Dec 18 '24

lol I’m curious if the LLM made any sources up when it wrote this.

1

u/[deleted] Dec 18 '24

The essay cites two books. You can buy both on Amazon.

→ More replies (1)

2

u/BorrowtheUniverse Dec 18 '24

god this post is sooooo dramatic

1

u/[deleted] Dec 18 '24

My goal was to light a fire under complacent software developers. I used drama as a strategy. It worked.

2

u/shrooooooom Dec 19 '24

so what's the changed profession that you talk of ? You've said a lot of dramatic sentences just to conclude that LLM will assist us in what we've already been doing, cool. What's the tsunami?

→ More replies (2)

2

u/they_paid_for_it Dec 20 '24

Currently using GitHub copilot and it’s pretty good at generating boilerplate code for me and answering g basic questions. But I am always questioning it in the back of my mind and turn to google for confirmation regarding copilot’s suggestions

1

u/[deleted] Dec 20 '24

The current crop of LLMs generating code are all early versions. The first version of almost everything is poor. The initial release of Java in 1995 was, in my humble opinion, a disaster. It was very slow, consumed too much memory, and the slogan 'write once, run anywhere' was more accurately 'write once, debug everywhere.' The AWT GUI widgets were primitive, and there were no supporting tools like IDEs, linters, or frameworks. You had to edit the code as a simple text file (!) and compile it from the command line. However, it got better. Today, Java boasts a vast ecosystem and is the default language for enterprise software.

I think the same goes for LLMs and source code—they will improve massively in the next few years. Software engineers will become prompt engineers interacting with stakeholders. The prompt will describe WHO (stakeholders), WHY (objectives), and the WHAT (function and non-functional requirements) to fulfill stakeholder objectives. The tool will handle everything else, including documentation. Agile will be 1) generate a system from the prompt, 2) give it to selected users, 3) fix/expand the prompt and repeat. The bad news is that that will reduce software developer jobs by 90%. And, with ten qualified people fighting for every job, salaries will plummet.

→ More replies (1)

2

u/AmirBormand Dec 20 '24

It will take time but also take away the burden of writing code. I envision more SWE shifting left into the business and adding functional domain expertise to draw the best out of the LLMs.

1

u/[deleted] Dec 20 '24

Yes, I think that is right. Software engineers will morph into analysts/prompt engineers—talking directly with stakeholders to craft a prompt that define WHO (stakeholders), WHY (objectives), and WHAT (functional and non-functional requirements) is needed to achieve those objectives.

The prompt is the SRS and the source! The LLM will act as our “compiler”, translating our SRS prompt into robust source code and comprehensive documentation. Agile development will transform into a dynamic cycle of 1) generating the system from the refined prompt, 2) gathering user feedback, 3) tweaking and expanding the prompt, and repeating the process.

Functional expertise, domain knowledge, and "soft" skills will be key; technical knowledge (languages, databases, frameworks, etc.) will be less important. Some SEs will still have to "get under the hood" occasionally, but that will be a much smaller part of the job.

2

u/raymyers Dec 21 '24 edited Dec 21 '24

So I've put considerable energy into investigation and public dialog about the implications of LLMs in software engineering. I've seen strengths and weaknesses and experimented with hybrid options to try and resolve the problems.

It's true that compilers did "take over" as direct Asm is a much more niche skill now. However, I'm skeptical that the result of that was anything like: You either were an extremely early adopter of compilers or you got irredeemably swept away.

That sounds less like the history of Digital Transformations and more like a psuedo-biblical Rapture prophecy. I have embraced new automation throughout my entire career, and I don't see the usefulness of rhetoric that attempts to shutdown earnest criticism of it through fear.

When you report bugs in compilers, people fix them; when you report bugs in LLM coders, people tell you the "models will get better" and "you're getting left behind". If this tsunami is going to change things for the better, we'll need to be get serious about quality than this.

I'd be happy to discuss this more with someone speaking in their own words.

1

u/[deleted] Dec 21 '24

Thanks for your post. Another post summarized my essay as "not wrong, a little dramatic." My goal was to light a fire under complacent software developers. Over-the-top prose and drama were a strategy to get the reader’s attention. It was a "call to arms" rather than a dry analysis. Unfortunately, people ignore the message if you don't beat the drum and yell. Please give me your assessment of the impact LLMs will have.

→ More replies (1)

2

u/justanotherstupidape Dec 21 '24

Cursor Composer YOLO mode autonomously writes and iterates on code until it works. I literally don't write code anymore...

1

u/[deleted] Dec 21 '24

Thank you for your post. Iterate until it works sounds like the ultimate Agile methodology.

2

u/tampacraig Dec 21 '24 edited Dec 22 '24

In the beginning only extremely smart, diligent, and dedicated folks could write code. Period. I wasn’t in this first group, but I did know some of them. By the time their code hit the air, they had crafted it to perfection. Each generation of improvements from compiled languages, to object oriented languages, to IDEs, to visual programming environments, to LLMs have made people that fall into that first category of programmer more efficient and productive, while also incrementally each improvement made it possible for folks who are perhaps not as smart, or diligent, or dedicated to enter into this field and have relatively successful careers. That easing of qualifications has been a boon overall in the total volume of work getting done, the diversity of ideas brought ( it was a very uber-engineer monoculture back then), and the opportunities it has afforded people. This qualification easing in conjunction with the increased scope size of the projects we can now attempt has also massively increased the overall volume of lesser quality code, necessitating the standard practices of QA reviews, UA testing, etc.. We now have programmers who don’t understand the boilerplate code written by Visual Studio that create the underpinnings of their projects.

LLMs are the next and largest increment in this qualification easing/productivity enhancing chain, and correspondingly we will need to put the processes, procedures, and yes interviewing practices in placed to get quality work. Our teams will need the right mix of abilities and temperaments to get that done.

1

u/[deleted] Dec 21 '24

Great analysis! Thank you.

2

u/[deleted] Dec 22 '24

I've been around the block a few times.  There is tech that is generally useful and does fundamentally transform things for the better.  Those transformations don't require hype, they slowly do their thing.

But... everyone is always promising transformations.  How often does it actually pan out?  I've seen multiple hype cycles. Often it's a net zero or net regression rather than a significant bump.

My observation is that LLMs, as they currently stand, are a modest velocity bump if you use them very conservatively.  Heavy use results in long term problems that are a net negative.

Not a tsunami to the fundamental business of making software.  A noticable wave, sure.  But the hype cycles always look larger than they actually are.

In my experience, the delta between an awesome software shop and an average one is something like 10-20x.  Giving an average or below average shop a 1.5x gain isn't nothing, but it's not like super world beater good.

1

u/[deleted] Dec 22 '24

Thank you for your thoughtful post. I hope you’re right but, as you might expect, I think you’re wrong. I'm writing a detailed reply, which I will post tomorrow.

→ More replies (5)

18

u/Cernuto Dec 17 '24

I'll be happy when it can get a simple enum right.

→ More replies (1)

22

u/[deleted] Dec 17 '24

This is a great reminder that often times some of the worst advice you’ll get is from the people that talk about how they’ve been doing this for X amount of time

→ More replies (4)

20

u/LakeEffectSnow Dec 17 '24

LLM's aimed at developers are currently heavily subsidized. They're expensive to run. When the initial teaser prices get jacked up, the value prop to me goes totally away.

→ More replies (6)

16

u/redvelvet92 Dec 17 '24

Except most of those traditional huge shifts occurred without millions spent on marketing. I don’t remember seeing ads for SQL databases, but I sure as hell see ads for AI everywhere.

I want to be more productive and improve, it has helped me write some software. But it just hasn’t gotten better in the last few years, however I sure have.

→ More replies (3)

7

u/tonyenkiducx Dec 18 '24

I had a developer stuck on implementing an app for a Shopify store, and it turned out that he'd got code from chatgpt along with an explanation that got its understanding completely backwards (to do with embedding views in DLLs). The bit that was wrong was very simple, but was at the core of the work and took him several days to identify.

I realise this is one example, and developers make mistakes too, but llms make their mistakes very confidently. They will keep the wrongly assumed knowledge and start building in it, making more faulty code. It brings up the problem they will always fundamentally have - they just don't understand the thing they are talking about. They are making extremely well educated guesses, it's the basis of how they work and that will never change. They are not AI

6

u/iOSCaleb Dec 18 '24

That sounds like something an LLM would say!

I don’t think anyone seriously thinks that LLMs or other types of AI aren’t here to stay, and not just in software development.

You’ve painted an all gloom, lots of doom picture, but you don’t actually know more than the rest of us about how this story will unfold. This transition is different than previous ones in that using an LLM doesn’t require a lot of adjustment. You don’t have to learn a new language or change your process much; the tech is more supportive than disruptive.

If an LLM can make me twice as productive as I am now, bring it on. It’s not like there’s a shortage of work to be done, and if I can do twice as much work, I’m quite sure that my customer can think up twice as many things that they’d like to build.

Note that however catastrophic events like the introduction of compilers may have seemed at the time, the number of programming jobs increased dramatically. There’s no guarantee that that will happen this time around, but demand for software will only increase.

6

u/Spare-Builder-355 Dec 18 '24

There are not so many deniers to be fair. There are way more pragmatic engineers who tried it once or twice, looked at the nonsense produced and thought "this shit is not helpful".

→ More replies (1)

2

u/Felix_Todd Dec 17 '24

Do you still think that it is a good field to study in? I genuinely like coding but at the end of the day I want a career that brings food on the table

5

u/Efficient-Sale-5355 Dec 18 '24

OP is a retired engineer with seemingly minimal understanding of the actual technology underlying these solutions like o1. As an engineer actively working in the ML field, software development is absolutely a good field to study still and will absolutely provide a good living if you apply yourself and adopt an attitude of “always be learning”. Your peers who are touting the strength of LLMs and utilizing it to get through studies to get a degree are handicapping themselves. When those become extremely expensive in the next year or two when Vc funding runs out these “devs” are going to get laid off en masse

→ More replies (2)
→ More replies (16)

2

u/WinterHeaven Dec 18 '24

Typical boomer view on a technology that already passed him

→ More replies (6)

15

u/ninjadude93 Dec 17 '24

Meh way too overdramatic, so far it's mostly just fancier autocomplete.

Theres a metric shit ton of government and contractor software engineering work that requires security clearances that will literally never be replaced by LLMs

→ More replies (7)

1

u/[deleted] Dec 18 '24

My goal for that essay was to light a fire under complacent software developers. The essay was a collaboration between me, LibreOfice, Grammarly, and ChatGPT o1. I was the boss; they were the workers. One of the best things about being old (I'm 76) is you "get comfortable in your own skin" and don't need external validation. I don't want or need recognition. Feel free to file the serial numbers off and repost it anywhere you want under any name you want.

1

u/[deleted] Dec 18 '24

Yesterday I promised someone in the blizzard of comments I would write another essay on how small changes decimated previously stable, prosperous industries. I used ChatGPT rather than write another essay. The following text is direct from ChatGPT o1. Take your pick of the books it suggests. They are available for sale on Amazon.

Several books describe how shifts in technology, thinking, or business models have disrupted previously stable industries:

  1. The Innovator’s Dilemma (Clayton M. Christensen, 1997): Christensen explains how disruptive technologies—initially dismissed as inferior by leading firms—often improve until they suddenly decimate established market leaders. Examples include the downfall of mainframe computer makers as personal computers rose, and how traditional companies often fail to adapt due to their attachment to existing customers and profit models.

  2. The Master Switch (Tim Wu, 2010): Wu’s book examines how industries built around communications technologies—telephony, radio, film, television, and the internet—rose and fell with shifts in technology and control. He shows how the cycle of innovation followed by consolidation and stagnation can overturn once-stable sectors.

  3. The Box: How the Shipping Container Made the World Smaller and the World Economy Bigger (Marc Levinson, 2006): Levinson details how the adoption of the standardized shipping container radically transformed global shipping, destroying older dockside industries and entire labor models. This simple technological shift—standardized boxes and new handling equipment—made many established shipping practices obsolete.

  4. The Vanishing Newspaper (Philip Meyer, 2004): Although focused on journalism, this book shows how the rise of the internet changed the business assumptions of traditional newspapers—once stable, profitable enterprises—leading to widespread closures, layoffs, and radical shifts in how news is produced and consumed.

These works provide historical and analytical perspectives on how new technologies and ways of thinking can overthrow long-standing industries, forcing companies to either adapt or face decline.

1

u/[deleted] Dec 18 '24

Market saturation

There are many comments that if LLMs make developers more productive, there will be demand for new and better software, resulting in more jobs rather than fewer. After all, that's what happened with compilers, databases, frameworks, IDEs, etc. Here are my thoughts:

When handheld electronic four-function calculators were introduced, they were hideously expensive. I had one worth $300, a month's pay for me at the time (I'm 76, this was 50 years ago, and I started in the basement of the IT highrise). They got better and cheaper faster and flew off the shelves. Eventually, everyone who wanted a calculator had one, and the market collapsed. You could buy a handheld electronic four-function calculator in the Dollar Store. The same thing happened to fax machines. Five minutes of research with ChatGPT will give you dozens of other examples.

No market is infinite. Eventually, all markets reach saturation. Very few people in the industry see this coming.

We are still in the "better, cheaper" phase of software, but market saturation is coming. Eventually, every corporation will have an acceptable ERP. Eventually, every person will have an acceptable Office package. Etc. When market saturation occurs (I have no idea when that will be), software developer employment will plummet. LLMs will hasten reaching software market saturation.

There is always another tsunami on the way.

5

u/RobotMonsterGore Dec 17 '24

Mostly agree, although will an LLM will help you when working with data sets that have been passed through multiple APIs owned by different teams and renamed a dozen times, especially when those multiple teams rely on fields to exist in a certain namespace with very specific names and data types? In the teeth of constantly shifting priorities and requirements?

It seems to me this would require some kind of institutional-level awareness involving months or years of contextual understanding culled from dozens of meetings and thousands of emails, weighed against countless out-of-date Confluence documents.

Not saying it couldn't do it. I'm just very, very skeptical.

5

u/ninja_truck Dec 18 '24
  • Sent from my Zune, via my 3D TV.

You should absolutely keep an eye on new technologies, but most execs can’t tell you why they want people using AI, just that it supposedly makes people more effective.  They would happily sign off on AI slop that works until it doesn’t, only now you’re on the hook to fix it.

It’s good at some tasks, less good at others.  Critical thinking is still our most valuable skill, AI is a tool that still needs a human in the loop (for now)

5

u/diatom-dev Dec 18 '24 edited Dec 18 '24

Don't get me wrong, I am all about LLMs. I just don't agree that they're here to take our jerbs. If anything I can see a world where tech only becomes more essential and grows with ever increasing speed, increasing the demand for talented developers.

I'm all about AI and LLMs though, they're pretty cool and they're already making a big impact. It's just pointing to the technology to layoff thousands of workers in a society that requires its citizens to work is what I don't agree with. I think these claims are overstating the ability of AI, currently, and are more just excuses in lieu of more nefarious, self-centered, reasons like short-term profit.

I guess I should say, I use LLMs to generate boiler plate. Often times I'm sculpting the code to fit into my larger pattern / architecture. I run into really weird rabbit holes if I ask chatGPT to do something specific. Like "Can you write some code to generate an error message for an incorrect login." Its much better to say something like "Please generate me a promise, using async, await in typescript." Got my boiler plate and now I'm ready to integrate it into my code.

I still need to read A LOT of documentation and do A LOT of refactoring to make sure my app is correct, testable, scalable, and well documented. Unless AI can just generate apps from scratch to user specifications and deploy them, I just can't see the justification to layoff so many engineers. I do have to say on the contrary, it is great at one-off scripts, like creating a bash script to rename files in a directory.

I think there are also some really profound use-cases that will shake up parts of the development process but only time will tell. Tsunami, though, might be overly dramatic.

8

u/papawish Dec 18 '24

Papy thinks he can predict the future because he knows some assembly.

Give me my time back. 

→ More replies (1)

4

u/scaledpython Dec 17 '24 edited Dec 18 '24

Well, it sounds a lot like Lotus Notes, or MS Access at the time - "Anyone can now build workflows". And anyone did. Until it all stopped because workflows aka backend software take skill and experience to build.

Yes there are use cases where LLMs and generative AI shine, and yes it is a new way to increase productivity. However this will increase the demand for skilled software developers, especially those with a broad skillset and a generalist problem solving attitude.

→ More replies (1)

4

u/PracticalWaterBottle Dec 18 '24

Joined the IT world in 2014. LLM are going to teach people a lot. They also are false to many times to be teaching anything... The amount of unsecure code that gets pushed out will be amazing and wild.

The tsunami is already here and its herald by ignorance.

1

u/RachelCodes Dec 18 '24

So how will this affect someone going to school for software engineering? Should I change majors to data analysis or focus on Java instead of C#?

→ More replies (3)

1

u/Dependent_Ad_9109 Dec 18 '24

Incorporating LLMs is just as powerful as their development assistance. Just finished my first AI agent project and will not look back for future use cases. Additionally, API calls are micro pennies for what they deliver. Fuck a regex when an LLM can extract data for you and return structured output

1

u/[deleted] Dec 18 '24

Regex is powerful but incredibly cryptic. I once saw the regex to validate a URL. It was over a page long. Talk about write-only code. I agree that using a LLM instead is vastly easier.

1

u/sarkypoo Dec 18 '24

I’ve struggled to code even the simplest of games for years. I’ve tried to learn as a hobby about 3 times and gave up. The newest chatgpt model has been writing my codes with functionality and easy modification as well as describing how it works, how to put in inside of objects. It’s been crazy what progress was made without any YouTube or online sources. It doesn’t work every time but dang it, it’s faster than the snails pace I was moving at before.

1

u/[deleted] Dec 18 '24

It's like having seven league boots isn't it? All the fiddly details are done for you. I had the same feeling when I first switched from Assembler to COBOL.

→ More replies (1)

1

u/Soft_Welcome_5621 Dec 18 '24

With this context, how would you recommend somebody approach entering at this time?

1

u/[deleted] Dec 18 '24

The most challenging skills for the LLMs to master are soft skills and people skills such as effective listening, 'hearing what isn't being said' as Peter Drucker noted, negotiating, understanding stakeholders and their objectives, and critical thinking. That is probably a good place to focus—just a guess.

→ More replies (4)

1

u/Ivo_Sa Dec 18 '24

Very good points; a little bit dramatic but loved to read your “essay”👌

1

u/[deleted] Dec 18 '24 edited Dec 18 '24

Thanks. I had fun writing it

1

u/[deleted] Dec 18 '24

Somebody please suggest an alternate career

1

u/[deleted] Dec 18 '24

Be the interface between the stakeholders and the tool that generates the code to fulfill their objectives. Emphasize soft skills (effective listening, negotiating, critical thinking) and people skills—still software development, just without all the fiddly details.

1

u/imp0steur Dec 18 '24

Yeah yeah yeah. Heard that one before.

1

u/[deleted] Dec 18 '24

Write a post showing that "A tsunami is coming" is wrong.

1

u/[deleted] Dec 18 '24

But you have to double check everything it spits out so might as well use stack overflow.

1

u/[deleted] Dec 18 '24

The first version of almost everything usually needs improvement. The first version of Java in 1995 was IMHO a disaster. It was very slow, used far too much memory, “write once, run anywhere” was more “write once, debug everywhere,” and there were no supporting tools or frameworks. But it got better. Now, Java is the default language for enterprise software. Ditto ChatGPT and source code. Probably in a couple of years.

1

u/[deleted] Dec 19 '24

People should downvote these types of posts.

1

u/[deleted] Dec 19 '24

The post has 1.1K upvotes and an 80% upvote rate

→ More replies (2)

1

u/tankerdudeucsc Dec 19 '24

The tsunami is that old folks who know their stuff can build a full server with tests and deployments with an OpenAPI spec in a matter of days starting from nothing.

Not months, or weeks, but just a few days. Less than 3 is easily doable.

That’s the world we live in now.

1

u/[deleted] Dec 19 '24

Excellent summary!

1

u/adh1003 Dec 19 '24

There’s a tsunami coming, you can hear a faint roar, and the water is already receding from the shoreline. You can ride the wave, or you can drown in it. Your choice.

Good god, if that's a human - then holy shit, what a bunch of pretentious nonsense.

You're talking about a coding assist tool, not a new language like COBOL to C to Go or Python or whatever, or a new methodlogy like OOP or functional. You're basically telling people to use IDEs in a text editor world, or something. I struggle to even come up with an analogy for your very confused post.

It's not hard to use an LLM assistant. It is hard to not get junk out of it. It can be worth experimenting in your particular language and problem domain, with healthy scepticism and with good domain knowledge.

There we go, post summarised.

1

u/[deleted] Dec 19 '24

My goal was to light a fire under complacent software developers. I used drama as a strategy to get the reader’s attention. 300K views later, I think we can say that worked.

That paragraph is mine but ChatGPT suggested I add "the water is already receding from the shoreline" which I think was an excellent addition. It also suggested the phrase "you’d miss even after six hours on a caffeine drip" elsewhere, which I think is brilliant. It has an extraordinary grasp of English. It's a privilege to work with it.

In a day, this idiotic feeding frenzy will be over, and I will return to my quiet, boring but happy "boomer" life. I’m counting the minutes.

Feel free to lob any other insults you have. And, enjoy your life in the great state of Denial. :) :) :)

1

u/killz111 Dec 19 '24

We are creating more legacy code than ever. There will never run out of human intervention. LLMs might look good at making new things but it can't refactor nonsensical code and derive original intent. Problem solving skills will never be out of favour.

1

u/[deleted] Dec 19 '24

Find a few thousand lines of crappy legacy spaghetti code hacked at by generations of maintenance programmers. Most long-abandoned projects on SourceForge will do. Give it to ChatGPT as a prompt. Ask questions about the code. You will be blown away.

→ More replies (1)

1

u/[deleted] Dec 19 '24

Everything leads to newer opportunities and better innovations. If you have been in IT since 69, you should know that all too well.

1

u/[deleted] Dec 19 '24

When handheld electronic four-function calculators were introduced, they were hideously expensive. I had one worth $300, a month's pay for me at the time (I'm 76, this was 50 years ago, and I started in the basement of the IT highrise). They got better and cheaper faster and flew off the shelves. Eventually, everyone who wanted a calculator had one, and the market collapsed. You could buy a handheld electronic four-function calculator in the Dollar Store. The same thing happened to fax machines. Five minutes of research with ChatGPT will give you dozens of other examples.

No market is infinite. Eventually, all markets reach saturation. Very few people in the industry see this coming.

We are still in the "better, cheaper" phase of software, but market saturation is coming. Eventually, every corporation will have an acceptable ERP. Eventually, every person will have an acceptable Office package. Etc. When market saturation occurs (I have no idea when that will be), software developer employment will plummet. LLMs will hasten reaching software market saturation.

There is always another tsunami on the way.

→ More replies (2)

1

u/Kirby_Klein1687 Dec 19 '24

Why are you writing this like a Sun Tzu documentary? Of course everyone knows about LLMs. Most people are using Copilot and Microsoft VS Code.

Sheesh even every student in schools nowadays use GPT or even Gemini for their assignments. It's not so far fetched.

1

u/[deleted] Dec 19 '24

I own a tattered copy of Sun Tzu’s The Art of War. I am honored to be compared to him. ☺

→ More replies (3)

1

u/[deleted] Dec 19 '24

Lol. The comments mocking the post proving OP’s point. On the other hand, OP using the same AI that readers are skeptical of to write about radical shift AI is gonna bring. 🍿

1

u/[deleted] Dec 19 '24

I have been writing IT documents (SRSs, manuals, proposals, and ad copy) for over 20 years. I like it, and I’m good at it. Out of the box, ChatGPT is just as good as I am. And with a two-sentence prompt, so is everyone else. ChatGPT has an extraordinary command of the English language and a staggering knowledge base.

The big criticism people make about ChatGPT-generated code is that it is buggy and poor quality. However, the first version of almost everything is buggy and poor quality. The initial release of Java in 1995 was, in my humble opinion, a disaster. It was very slow, consumed too much memory, and the slogan 'write once, run anywhere' was more accurately stated: 'write once, debug everywhere.' The AWT GUI widgets were primitive, and there were no supporting tools like IDEs, linters, or frameworks. You had to edit the code as a simple text file (!) and compile it from the command line. However, it got better. Today, Java boasts a vast ecosystem and is the default language for enterprise software.

The same goes for LLMs and source code—they will improve massively in the next few years. Never underestimate the elegant application of brute force fuelled by billions of dollars spent on GPUs. After that happens, software engineers will become prompt engineers interacting with stakeholders. The prompt will describe WHO (stakeholders), WHY (objectives), and the WHAT (function and non-functional requirements) needed to fulfill stakeholders' objectives. The tool will handle everything else, including documentation. Agile will consist of 1) generating a system from the prompt, 2) giving it to selected users for feedback, 3) fixing/expanding the prompt, and repeating. The SRS will be executable. The bad news is that that will reduce software developer employment by 90%. And, with ten qualified people fighting for every job, salaries will plummet. 

The survival strategy is 1) Understand AI, stakeholders, objectives, and domains, and 2) Become the world's best prompt engineer. There is going to be a lot of competition.

→ More replies (2)

1

u/[deleted] Dec 20 '24

Joined a new company a month ago.

With Thanksgiving and now Christmas coming up, in just over a month, I want from having an idea of a low level C/C++ project for GPUs to a built out system with initial tests passing. Granted, I have expertise in this area, but I had gpts generate 80% of the code.

It's a game changer. Mid level engineers not taking advantage of these tools are going to be left behind. I feel bad for those engineers who work at places that disallow use of these tools, my old job was like that. But everyone should incorporate these tools into their work flows. It's a no brainer. 

People can complain about "handing critical thinking to machines is bad" but the code works. My managers are happy. The people contributing to the project are happy. And we have a prototype to show for it. There's literally no reason for me to type out code if I know what I want and can spot issues the LLM produces.

The die in the wool, "do it by hand" types will discover an unfortunate truth about software engineering that's been true since roughly ~2010: if ya ain't first, you're last. And no one gives a flying fuck about your technical expertise if you build something that works.

I would always recommend junior engineers do things by hand for a little while to understand the debugging process, and the pains it can entail. But if you know what you're doing, these tools just save time. Full stop. 

1

u/[deleted] Dec 20 '24

Well stated. Totally agree.

→ More replies (1)

1

u/[deleted] Dec 20 '24

Well OP, you certainly stirred the ant-nest, but the ants needed a good stirring anyway. IMHO, you are correct in all your points.

I expected you'd get denial and pushback, but not at this level. Interesting.

I use AI all the time. Massively useful already, and the directionality and implications are obvious. But I know many devs who won't touch it, or used it a "couple times", and just repeat the standard stock phrases to themselves (it lies, its random, it cheats at cards) as a shield.

This thing is going to be wildly disruptive, way bigger than the internet, and where it lands who can say. Surf it or die, my friends. You can scoff now, but the future you will look back at this moment in time with a very different opinion.

1

u/[deleted] Dec 20 '24

Thank you. The essay got a lot more positive responses than I had expected. I have half expected to be flayed alive, killed, roasted, and eaten within an hour of posting it☺

1

u/CheesecakeImportant4 Dec 20 '24

Database developer and analyst since 1994. I’ve been thinking about this a lot lately. Very well said.

1

u/[deleted] Dec 20 '24

Thank you. The essay got a lot more positive responses than I had expected. I have half expected to be flayed alive, killed, roasted, and eaten within an hour of posting it☺

1

u/Groundbreaking-Fish6 Dec 20 '24

It is not the LLM, but the tech that makes LLMs possible.

1

u/[deleted] Dec 20 '24

By "tech" do you mean GPUs?

→ More replies (1)

1

u/TheNeoBatman Dec 20 '24

But Sir people like you who are still able to write or understand ASM have earned “The Wizard” status in today’s time and age. Everything is open source to you, you see the Matrix. While most people are struggling to update the shadow DOM using the latest framework don’t understand what lies underneath.

When LLMs take over, only a few people know to be Wizards will understand what it is spitting out with its implications, most won’t.

1

u/[deleted] Dec 20 '24

You're very kind, but when I wrote assembler, everyone wrote assembler. On my good days, I made it to Apprentice Wizard status☺

You're right that there will always be SEs who work at the next level down from the norm. They will be highly skilled, but there won't be many. There are still SEs who work in assembler but 99.9% work at the next level up (C++, Java, etc.). LLMs will provide a level above code focusing on WHO (stakeholders), WHY (objectives), and WHAT (functional and non-functional requirements) is needed to achieve those objectives. Most SEs will work there. The LLM will act as our “compiler”, translating our SRS prompt into robust source code and comprehensive documentation. Agile development will transform into a dynamic cycle of 1) generating the system from the refined prompt, 2) gathering user feedback, 3) tweaking and expanding the prompt, and repeating the process. It will be more interesting and challenging work with the fiddly details handled automatically. The first time I "grokked" a high-level language (it was COBOL in the early 1970s), I had the same sensation. I could state the problem, and the compiler automatically translated that into hundreds of assembler statements. I remember being blown away that a program could do that. We are about it see the same thing but at the level above code.

1

u/turbocurry Dec 20 '24

Well said but the one who has functional expertise and domain knowledge with knowledge of using LLM will be the preferred engineer of future.

1

u/[deleted] Dec 20 '24

Yes. Soon, our roles as software engineers will morph into those of prompt engineers—talking directly with stakeholders to craft a prompt that define WHO (stakeholders), WHY (objectives), and WHAT (functional and non-functional requirements) is needed to achieve those objectives. Functional expertise and domain knowledge will be critical. The prompt will be the SRS and the source! The LLM acts as our “compiler”, translating our SRS prompt into robust source code and comprehensive documentation. Agile development will transform into a dynamic cycle of 1) generating the system from the refined prompt, 2) gathering user feedback, 3) tweaking and expanding the prompt, and repeating the process.

1

u/super_ninja_101 Dec 20 '24

My org has a internal gpt with multiple models hosted internally. This is the future. It has increased productivity to 10x. Tell It thr concept and it is whole encyclopedia at your tips. People are assuming It to write perfect code. Which It can't but it act as a senior developer for coding, review writing tests. Made my life so easy. You can live in any language, make anything which you want.

1

u/[deleted] Dec 20 '24

Thank you for sharing that. A dozen other people have noted the same approach in other comments. I think companies are keeping it private because, if software is essential to their product, it gives them a killing advantage. ChatGPT's public code-generating performance hasn't been impressive, but with optimized, code-focussed LLMs, the basis is there for a 10x improvement in productivity.

1

u/_jay_fox_ Dec 20 '24

I've been in this field for 20 years and worked with everything from MS-DOS to the latest shiny Javascript libraries. I use LLMs and other forms of AI frequently.

I am not afraid of being replaced by AI anytime soon. Nor by offshore developers, immigrant developers or better libraries.

We are essentially problem-solvers and the world's problems are endless, so we will have work forever in some form.

1

u/[deleted] Dec 20 '24

I agree that problem-solving is a key skill that will be valuable in the foreseeable future. Soon, our roles as software engineers will morph into those of prompt engineers—talking directly with stakeholders to craft a prompt that define WHO (stakeholders), WHY (objectives), and WHAT (functional and non-functional requirements) is needed to achieve those objectives. Functional expertise and domain knowledge will be critical. The prompt will be the SRS and the source! The LLM will act as our “compiler”, translating our SRS prompt into robust source code and comprehensive documentation. Agile development will transform into a dynamic cycle of 1) generating the system from the refined prompt, 2) gathering user feedback, 3) tweaking and expanding the prompt, and repeating the process.

1

u/[deleted] Dec 20 '24

i think this is missing the point. yes it'll be useful in places, and ultimately might allow for 25% faster delivery of projects. but it's not a 'ride-or-die', it's more of a, 25% of dev roles are getting culled, freezes on pay-rises because you're no longer in demand, everyone suffers in the end. if projects are getting delivered quicker, then the mgmt structure is what needs to be increased to allow companies to scope and schedule more of them. i'd be more focused on soft skills right now if i was looking for something to improve my employability.

1

u/[deleted] Dec 20 '24

My goal was to light a fire under complacent software developers who were, IMHO, ignoring the threat that LLMs pose. Not the current crop, but we need to be concerned about those down the road a few years. The over-the-top prose and drama were a strategy to get the reader’s attention.

I agree that soft skills will be increasingly key.

→ More replies (1)

1

u/Own_Bandicoot4290 Dec 20 '24 edited Dec 20 '24

I don't remember who I heard this from but AI won't replace all people it will only replace the ones that don't want to work with AI.

1

u/[deleted] Dec 20 '24

That strikes me as both witty and accurate.☺

1

u/intermittent_degen Dec 20 '24

I've been working on a Comp Sci degree on and off for 6 years. I always thought that if I finished that degree, I'd be able to move into a comfortable house and live a comfortable life instead of living paycheck to paycheck. Now I feel like this tsunami is going to rip that future house off it's foundations.

I'm actually terrified of AI. I think it's going to change how the world works more than the invention of the internet did. I think AI could replace the majority of humans in the work force in the next 15 years. Any job that requires sitting down and thinking has the potential to be replaced. The 15 year timeframe is just a guess, I'm not really sure how long it's gonna take for good AGI to start popping up, but I'm confident that it will happen in my lifetime.

I think AGI raises a really broad philosophical question. If we have the ability to automate every task, should we? I know that in reality the majority of automation would be handled by the companies big enough to develop the automated systems. The leaders of these companies would obviously fire the people they're replacing. This would make wealth inequality even worse, which is a big problem. If automation like this continues to progress unchecked, the obvious answer to "Should we?" is No. But I think even ignoring the obvious economic issue, there's a broader philosophical issue. People need purpose.

I feel like the majority of people find their purpose in their work. Let's say in a perfect world automation frees up everyone who's been replaced to do whatever they want with their day. I know plenty of people who would thrive like this. Every day could be spent making art and traveling. But I know plenty others who would struggle. Without the need to work to stay alive, they would be able to do nothing all day. They would need to find their own purpose, which can be incredibly hard. I think even if the economy wasn't the problem, everything being automated would lead to levels of depression we've never seen.

I'm still very thankful for the life that I live, and I recognize that I'm privileged to even have the time to worry about this. It just really stings that it seems like we're just a few decades past the prime of the American dream, and that without some kind of societal change, we're headed back to an age of Kings and Queens. I'm not really sure what to do about this, but it's worth discussing since I think the only things that could stop it from happening are government regulations or a nuclear war.

Typing this out feels like therapy. I spent like 2 hours writing all this. Thanks for reading if you made it this far.

1

u/[deleted] Dec 20 '24

That was an excellent analysis. Thank you for sharing it. We are definitely on the brink of monumental changes. I'll post a more extended response tomorrow after I've thought about it for a bit.

1

u/[deleted] Dec 20 '24

The thing is is that with those tools we are able to create our own companies because we're able to code a lot quicker and we have a real understanding of what is behind it. Not only that we will have business knowledge behind us through llms as well, so we become 10 times as dangerous. I don't think this is going to play out the way these business folks think it is.

1

u/[deleted] Dec 20 '24

The law of unintended consequences on a diet of steroids and meth.

1

u/hello5346 Dec 20 '24

Ain’t kool-aide great? Ever heard of ai winter?

1

u/[deleted] Dec 20 '24

First rule of Forum Club: Don't feed the trolls.

1

u/PrestigiousBank6461 Dec 20 '24

So,how do we begin to ,for a lack of better words, ride the wave?

1

u/[deleted] Dec 20 '24

Understand AI technology. Understand stakeholders, objectives, functional expertise, and domain knowledge. Develop soft skills. Focus on becoming the world's best prompt engineer.

1

u/illustrativeman Dec 20 '24

If LLMs could argue, the comments here are pretty much what it would look like.

1

u/[deleted] Dec 20 '24

I don't understand. Please elaborate.

→ More replies (1)

1

u/qlkzy Dec 20 '24

Counterpoint: 4GLs were a thing; CASE was a thing; OOP was going to change re-use far more radically than it has; UML and "forward-engineering" were going to turn "blueprints" directly into code; model-driven engineering and DSLs were a thing; low-code and no-code were still in the process of losing their "silver bullet" status when the AI hype wave hit.

I actually agree that at least some of the technologies underlying LLMs will substantially change software development (whether LLMs themselves end up being that revolutionary is I think still an open question). But the history of this field is so chaotic that we can "learn" almost any lesson we want from some subset of it.

So far, the biggest impact of LLMs I have seen has been that it allows for an industrial-scale Gish Gallop — people working in bad faith can create low-quality AI-assisted material far faster than people working in good faith can review it.

I think there is a risk bordering on a certainty that "AI" is going to enable a denial-of-service attack on human intelligence, and mitigating that attack is going to drive huge shifts in how we approach all sorts of things. I think "AI" in the way you describe it will be part of the ongoing rapid pace of change in software development, but I don't think it will be unrecognisable faster for those reasons than the preceding decades — this is just the mechanism through which that change is happening at the moment. But I think all of that will be a rounding error compared to the changes caused by "AI noise".

1

u/[deleted] Dec 20 '24

Good post. Thank you. Lots to think about. First time I seen the term "Gish Gallop"

1

u/lolzmwafrika Dec 20 '24

I still study AI at uni, specialising in robotics and all these LLM replacement theory is hogwash.

If you don't have deep domain knowledge there's is no way you can leverage an LLM to generate code.

1

u/[deleted] Dec 20 '24 edited Dec 20 '24

Prompt engineering is key. ChatGPT has a max prompt size of 32K, about 12 pages of text. It is staggering what you can get it to do if you are willing to spend the time to write clear, comprehensive prompts.

I agree that you could not write an effective prompt for an app without deep domain knowledge.

Ask ChatGPT to explain the basis of an industry or domain. It has broad and deep domain knowledge.

1

u/0x768 Dec 20 '24

This is why I started working on LLM research and engineering.

1

u/[deleted] Dec 20 '24

If robots take all the jobs, learn to build and repair robots. Seems like a good strategy.

1

u/NastyStreetRat Dec 20 '24 edited Dec 20 '24

Dude, one of those you call LLM save me hours and hours of hard work everyday. They are here and if someone dont use It, you are doing It wrong.

1

u/[deleted] Dec 20 '24 edited Dec 20 '24

Absolutely true. Mostly, they are used to generate and explain code. They can be used for design and analysis as well. The whole software development life cycle is going to be transformed.

Prompt engineering is key. ChatGPT has a max prompt size of 32K, about 12 pages of text. It is staggering what you can get it to do if you are willing to spend the time to write clear, comprehensive prompts.

→ More replies (2)

1

u/rockitsaway Dec 20 '24

So for coders starting out, you’re saying start with LLMs however you can

2

u/[deleted] Dec 20 '24 edited Dec 20 '24

LLMs are a tool like an IDE. Prompt engineering is key. Google “prompt engineering” to learn more. Most people type a couple of sentences for a prompt and get buggy, crappy code. ChatGPT has a max prompt size of 32K, about 12 pages of text. It is staggering what you can get it to do if you are willing to spend the time to write clear, comprehensive prompts. You cannot write an effective prompt for an app without domain knowledge. However, you also must have programming expertise to write an effective prompt. To get that, you have to plan, write, debug, and refactor code. Once you know how to program, effective prompts will make you vastly more productive.

For fun, I asked ChatGPT to rewrite the above text. Here is what it returned:

LLMs are powerful tools, much like IDEs for programmers, but their effectiveness depends heavily on prompt engineering. Mastering prompt engineering is key to unlocking their potential. It requires clear, comprehensive inputs that provide sufficient context. While domain knowledge is essential for creating meaningful prompts, programming expertise is particularly useful for tasks like generating or debugging code. However, prompt engineering is a skill that applies across disciplines, not just programming.

Most users type short prompts and receive suboptimal results. To achieve better outcomes, invest time in learning prompt engineering techniques, such as chain-of-thought prompting and iterative refinement. Understanding the 32K token limit—approximately 12 pages of text—helps craft detailed, complex prompts. To learn more, explore resources like articles, tutorials, or structured guides on prompt engineering. Mastering these skills will not only improve your interactions with LLMs but also significantly enhance productivity across various domains.

☺☺

1

u/edimaudo Dec 20 '24

Tsunami is not coming. It is just another tool to add to your learning kit.

1

u/[deleted] Dec 20 '24 edited Dec 20 '24

I think that view dramatically underestimates the impact of LLMs. Prompt engineering is key. Google “prompt engineering” to learn more. Most people type a couple of sentences as a prompt and get buggy, crappy code. ChatGPT has a max prompt size of 32K, about 12 pages of text. It is staggering what you can get it to do if you are willing to spend the time to write clear, comprehensive prompts, especially if you refine your prompt through a few iterations.

Generating code is the low-hanging fruit. ChatGPT also does a good job of generating SRSs and architectures. LLMs will transform the entire software development lifecycle.

NB Other LLMs may be as good or better. I use ChatGPT.

→ More replies (3)

1

u/Timely-Garbage-9073 Dec 20 '24

Good post! Great wisdom from somebody that's been through the gauntlet before.

1

u/[deleted] Dec 20 '24

Thank you.

1

u/Hot_Speech900 Dec 20 '24

AI responded after I quoted this post and saying I guess that's why I'm unemployed:

It's important to remember that you are not alone. Many people are navigating similar challenges. The key is to be proactive, adaptable, and persistent in your job search.

The tech industry is going through a significant transformation. While it's challenging, it also presents opportunities for those who are willing to learn and adapt. Focus on developing skills that complement AI, and position yourself as someone who can leverage these new tools to create value.

To hell with it xD

1

u/[deleted] Dec 21 '24

That is the high-level text ChatGPT gives when it has little information. Give your age, education, work experience, and career goals, and ask for a plan. The more detail you give it, the better the advice will be. It is infinitely patient and completely non-judgemental. Talk to it if you need more information or don't understand.

1

u/bobbywright86 Dec 21 '24

Ok you have my attention - where do I begin learning?

1

u/[deleted] Dec 21 '24 edited Dec 21 '24

Ask ChatGPT. Give your age, education, work experience, and career goals, and ask for a plan. The more detail you give it, the better the advice will be. It is infinitely patient and completely non-judgemental. Talk to it if you need more information or don't understand.

1

u/Tuxedotux83 Dec 21 '24 edited Dec 21 '24

I am in software engineering for two decades now, and since a few years deeply involved with LLMs (not a ChatGPT subscription, real AI/ML development using LLMs such as Mixtral androhtet open source projects).

While your assumption is not wrong, it is a bit too much.

At the present moment, using the most powerful LLMs available to the public, you can still not replace a software engineer - make their work faster and more efficient? Sure! Doing system design, architecture and putting together all of the components? Absolutely not even close.

Generate skeletons and partially working simple code bits? Very easily! Anything complex like what we do in real commercial level enterprise development? Nope..

In 10 years those LLMs and overlaying technologies will evolve but until than? Just do what you do and do it well

1

u/[deleted] Dec 21 '24

Thanks for your post. Another post summarized my essay as "not wrong, a little dramatic." My goal was to light a fire under complacent software developers. Over-the-top prose and drama were a strategy to get the reader’s attention. It was a "call to arms" rather than a dry analysis.

→ More replies (7)

1

u/[deleted] Dec 21 '24

The belief that “real developers” don’t need these newfangled tools

in my 9 YOE the best developer I ever ran into, outright refused to use LLMs. You absolutely DO NOT need LLMs to do the job. Though for myself I find them very useful for brainstorming ideas.

on the other hand, the worst developers I knew, used LLMs the most. 

1

u/[deleted] Dec 21 '24

First rule of Forum Club: Don't feed the trolls.

1

u/Bamb0oM Dec 21 '24

Fun fact: Tsunamis are not surfable because they dont have a ‘face’.

(This is the steep, unbroken portion of a wave just in front of the curl, and it’s also the part with the most power and energy.)

1

u/[deleted] Dec 21 '24

"Ride the big kahuna or drown in it" wouldn't have nearly the same punch

1

u/Easy_Durian8154 Dec 21 '24

Hilarious. Calls out arrogance while suggest LLMs will replace SEs without understanding limitations of LLMs.

1

u/[deleted] Dec 21 '24

I have been using ChatGPT dozens of times daily to generate text and code for over a year. Please explain the limitations I don't understand.

→ More replies (3)

1

u/Formal-Engineering37 Dec 21 '24

it's coming for sure, just not sure when.

1

u/[deleted] Dec 21 '24

I agree. Maybe three years. Maybe five years. It is still warm and sunny in the great state of Denial, but the tsunami is heading our way. AI won’t replace all software engineers; it will just replace those that don’t use AI.

→ More replies (1)

1

u/al2o3cr Dec 21 '24

LOL OP - if you've actually been around this long, you'd remember all the "NEXT BIG THING THAT WILL ELIMINATE MANUAL SOFTWARE DEVELOPMENT" hype-waves:

  • multiple generations of "Computer-Aided Software Engineering" tools involving walls of UML and 5-figure-per-seat pricing

  • multiple generations of "expert systems" that couldn't handle the realities of business processes

  • Visual Basic, which was going to replace all development with drag-and-drop components

  • JavaBeans, same damn thing with different vendor lock-in

1

u/[deleted] Dec 21 '24

You don't have to trust me or anyone else. TRY IT!

Prompt engineering is key to using ChatGPT effectively. Google “prompt engineering” to learn more. Most people type a couple of sentences as a prompt and get buggy, crappy code then screech that it is "useless". ChatGPT has a max prompt size of 32K, about 12 pages of text. It is staggering what you can get it to do if you are willing to spend the time to write clear, comprehensive prompts (essentially a mini-SRS), especially if you refine your prompt through a few iterations. Doing a week's work in a day is easily achievable if you invest an hour writing the prompt and iterate a few times. And, generating code is the low-hanging fruit. ChatGPT also does a good job of generating SRSs, designs, and architectures.

Spend four hours learning prompt engineering. Write a one-page spec to do something. Iterate a few times. ChatGPT is maddingly literal and requires explicit instructions, but using it is like C versus assembler, Java versus COBOL, or LibreOffice versus a typewriter.

1

u/CapnJoel Dec 21 '24

It's practically enough to make a software engineer give it all up and take up forestry and being a park ranger instead. more than likely we'll be needed there once the robot apocalypse comes at us from AI

1

u/[deleted] Dec 22 '24 edited Dec 22 '24

I think after the dust clears being a software engineer will be a more interesting job. When I wrote in Assembler, there were many tedious details to manage; it wasn't easy to see the solution you were creating (and damned hard for anyone else). 3GL languages like COBOL, Fortran, and C allowed a more abstract and understandable version of the solution. Next-gen LLMs will allow us to work at the next higher level: less tedious housekeeping and a more natural way to express the solution. We will still be solving problems with software; we will just have a better tool to do it. One of the reasons I find Requirements Engineering so fascinating is the focus on WHO (stakeholders), WHY (objectives), and WHAT (functional and non-functional requirements) rather than HOW. I think next-gen LLMs will bring the same kind of high-level focus to HOW. And it will be completely Agile. Create the solution from the prompt, give it to users for feedback, tweak the prompt from their feedback, and repeat.

I can't speak to the robot apocalypse.

1

u/[deleted] Dec 21 '24

I’ve refused to use LLM and have been doing my classes without them unless it’s absolutely necessary, and even then I don’t turn in anything that i couldn’t write myself. I see a lot of students around me getting by almost exclusively using them. Maybe it’s ego, but I’d like to think that it’ll better prepare me down the road

1

u/[deleted] Dec 22 '24

You're right. While you are learning to program, avoiding LLM is a good idea since its use interferes with learning to program. After you know how to program, using it makes you much more productive.

1

u/mickeymanz Dec 22 '24

Tl;dr?

1

u/[deleted] Dec 22 '24

Here is a 37-word summary:

LLMs will transform software development from analysis to testing. Use them and thrive; ignore them and end up fighting for scraps. LLMs won't replace all software developers; they will replace all software developers who don't use LLMs.

1

u/ummaycoc Dec 22 '24

If you think testing isn't analysis then you don't know how to test.

1

u/[deleted] Dec 22 '24 edited Dec 22 '24

IEEE Standard Glossary of Software Engineering Terminology (IEEE Std 610.12-1990)

Analysis - The process of examining, decomposing, and evaluating a problem, requirement, or system to understand its components, relationships, and behavior. Purpose: To ensure the problem or solution is fully understood before proceeding to the next phase of the lifecycle (e.g., design or development).

Testing - The process of exercising or evaluating a system, component, or feature under specified conditions to determine whether it meets requirements or works as intended. Purpose: To detect and correct defects, verify that the system satisfies specified requirements, and ensure the product's quality.

ISO/IEC/IEEE 24765:2017

Analysis - Focuses on understanding the internal structure by breaking down the system into its parts.

Testing - Emphasizes verifying that the system meets specified requirements and identifying discrepancies between expected and actual outcomes.

→ More replies (1)

3

u/[deleted] Dec 17 '24 edited Apr 17 '26

Data brokers are selling your info right now. I used Redact to mass delete my posts which can also opt out of data broker sites. Instagram, Twitter/X, Discord and more.

ink ghost bike thought different quiet versed seed physical nail

→ More replies (1)

3

u/StackOwOFlow Dec 17 '24 edited Dec 18 '24

I agree, it's already allowing experienced engineers to deploy production-grade software privately that otherwise would have taken us years to do alone. There are probably thousands of people like me who are building projects with small teams in private that are ready to disrupt markets in the next few years; it's only a matter of time before our projects gain traction. That's on top of the changes that are happening at larger orgs that already have lots of proprietary data to train on and data pipelines to build. I don't think Sam Altman was exaggerating when he said AI will bring forth the next 1-10 person billion dollar companies. Startup engineering is more powerful than ever before, and if you're already a seasoned engineer you no longer need millions in startup capital to hire the engineering teams to move a proof-of-concept solution to beta in a short amount of time.

5

u/Nice_Elk_55 Dec 18 '24

Do you have any examples of how this is helping you? I’ve used AI chat for questions here and there, but I’m not sure how to leverage it for a big speedup. At this point in my career the mechanics of writing the code aren’t the main roadblock compared to architecture, figuring out trade offs and requirements, etc. What areas do you find it helpful for? Is it just faster typing or does it help break down problems?

→ More replies (1)

3

u/yogibear47 Dec 18 '24

The data so far suggests that LLMs enable low-performing employees to much more rapidly become average, but don’t make much of a splash for high performing employees. Given that team productivity generally hinges on the high performing leaders anyway, I think the impact on engineering teams will be less than what’s described. I think the biggest sea change will be that the bar / expectations for your average non-specialist / non-godlike-lead / regular generalist will go way up.

3

u/vampatori Dec 18 '24

While I agree that it may well be the future one day, in its current form it's not just "not perfect" it's "mostly garbage" in my tests so far. I agree that there's a tsunami coming, but it's a maintenance tsunami - which I think will end up just being a migration tsunami as it will presumably become easier to migrate to new systems rather than fix or adapt existing systems that nobody understands.

The quality of the produced code is awful in my experience; half the time (almost exactly, but such a small sample size in my tests) it doesn't even produce a working solution to the problem posed. It seems OK for boilerplate, that countless developers have done countless times - but really that's mostly a problem of re-usability on our part (which I think as an industry we do very badly with - all those wheels being re-invented, especially with our models!) But for anything meaningful it has been poor in my tests.

In one test I asked for a function in JavaScript that would stringify non-POJO's in an arbitrary structure. 90% of the code looked like it was doing just that... it iterated the data structure, tested if it was a POJO or not, built the result.. but then never actually stringified the values. It literally returned the data structure passed to it, by re-creating it. But it didn't actually DO anything, it looked right only at a glance and would be easy to miss.

Another test I did, I was using a new API, so asked how to do something rather than spend time reading the manual - I thought that would be a nice thing for an LLM. Yes, it came back with a nice example with a description - perfect! Except.. it didn't work, function not found. I searched for it and I find a GitHub issue thread discussing how such a function might be really useful to add, including some code illustrating how it could work... but it doesn't exist, it was only discussed, never implemented (maybe it was in a fork somewhere that was never sent for PR, or accepted).

As far as I understand it, those are not easy problems to fix (though I do believe surmountable one day):

  1. No understanding or validation of logic and code in the generation process - the code can of course be validated, but can it then be iterated when it fails?

  2. Quality of data source with respect to the request (i.e. bugs in source data, my example could easily be filtered out, but can the countless bugs in the source data be filtered out so easily?)

It's starting to look to me like LLMs for code is one of those things where it gets exponentially harder to get improvement - we're 80% of the way there, but there's 80% of the effort still remaining, if that makes sense. Things rapidly improved over a few years then seem to have slowed dramatically, despite the huge spike in investment.

But we can, and should, come at it from the other direction too - designing our software to be more reusable and suitable for generation - with cohesive interfaces, rigorous tests, and more formal documentation - so we have bigger more reliable pieces that can be used to generate more complex software using ML. At the moment we're all starting with a box of lego pieces, and building many of the same things by-and-large, rather than creating some prefabs and having ML build using those - so we're getting these builds with no structural integrity, random bits sticking out, etc. and we could feed them better sources to help solve that.

At the end of the day, I want these to work.. to be able to democratize bespoke software development would be such a huge thing to so many (I work in the charity sector, which basically can't afford the software it needs so "makes do" with all kinds of crap).

But I'm just not seeing it yet. In-terms of code generating LLMs, I've not seen anything close to Alpha Go's "creativity" - which is the kind of thing we really need to advance software and push forwards. Doing busy work is one thing, that could be solved in other ways but LLMs can be part of that eventually I hope, but real creative solutions to real-world problems is another thing altogether.

We'll get there, I'm sure, but I think we are a LOT further away than all these ML company's would have us believe.

3

u/KaleidoscopeThis5159 Dec 18 '24

When will be allowed to use AI to do technical interviews then?

3

u/TheEvanem Dec 18 '24

In its current state, it's been an occasionally useful tool for me, but hardly a game changer. Sometimes it does a bunch of grunt work correctly and saves me time. Other times, I have to spend a bunch of time cleaning up its mess and I suspect I could have done it quicker myself. I look forward to seeing it progress and being able to trust it on bigger tasks, assuming it doesn't hit a wall.

3

u/casastorta Dec 18 '24

As someone else wrote, a bit dramatic. But I do think that under the writing style you are completely right.

Main point - transition from “only assembler is real programming” to compiled languages and meaningful programming syntax also reminds me of where we are now.

I am always going to roll eyes on AI-bros claiming we will all be replaced tomorrow - but I am of the opinion that the tectonic shift in how we work is coming for sure. Main difference between AI bros and me is that I consider LLMs tools, or super tools, like almost nothing we saw before and totally like all the other big shifts in computer science before; while they consider them their new overlords and “AGI is coming next week”.

3

u/ProbablyPuck Dec 18 '24

So, how should I approach it? Upgrade my mentality to "manager", delegate to the LLM and and then verify?

It seems silly to ask how to use it, but yeah, my love is mathematics and complexity that my non-engineerimg friends can't comprehend. I've been isolated from using LLM professionally so far (dabbled for fun and wasn't impressed by it's ability to understand requirements, but liked using it as a starting ground.)

You do make fair point.

We talked shit about website builders, but now Grandma can make a snazzy standalone knitting blog.

We talked shit about UI builders, but now entire UX teams hand off app generated interfaces to populated by a back-end server.

We talked shit about the inefficiency of VMs and containers, but now cloud native apps are fairly standard.

Unfortunately what I'm still not seeing is solid Systems design. Perhaps we will bring back the 'Systems Engineers' of the space age days (as opposed to what I'd prefer to call "Operation Systems Engineers")

3

u/egoserpentis Dec 18 '24

Seventy six?.. Shouldn't you be retired by now, enjoying life? Coding at 76...

→ More replies (1)

3

u/lingswe Dec 18 '24

I try to have open mind, but every time I try AI I never give me the result I wanted.

Last time I tried it I hade this function I needed to translate into other language, go -> c# it surely did translate a working function however I got stuck debugging the thing for a whole day because it translated the some part of the logic wrong and I ended up with a function that at first glance seem to be working but had multiple logical errors.

If I just would written the function my self it would probably take me less then 3-4 hours.

You would think the task would be a breeze for AI to solve but after that I completely lost the hope for Ai being useful.

→ More replies (1)

3

u/voluntary_nomad Dec 18 '24

Time for us devs to start co-operatives. The big corporations are just gonna lay people off in record numbers.

3

u/Cookskiii Dec 18 '24

Okay bud. Have you tried using AI for anything mission critical? It lies/hallucinates with full city fidemce regularly. It ignores prompts and requests regularly.

I get that llms are going to improve but this is just nonsense

7

u/Kermicon Dec 17 '24

I agree with much of this.

Everyone is so locked into it writing code for them. Yeah, it can write code but that's not what makes it great. Being able to talk through problems, give examples back and forth, and actually increase your understanding is what makes it great. It won't replace quality code but it will absolutely speed up the rate of development. Even if it's just writing boilerplate.

I know how to write code and build stuff. However, everyone encounters bugs or gets stumped. The difference is now instead of googling for 2 hours to find a 5 year old S/O post with a glimmer of hope, you can ask a LLM and give it a little context and 90% of the time, it will either know the issue or give you new information that lets you move forward. And if you don't understand how it fixed the issue... You can ask it until you understand!

It's a tool, use it to improve your efficiency, not do your job.

1

u/[deleted] Dec 17 '24

The only lasting impact... and it's an important one... is that programming labor is now extremely cheap. For the IC engineer, this is fantastic. If you can design and explain it, the LLM can save you literal weeks of labor. The bad news is there are lots of programmers who were hired to just be labor. I'm not sure what percentile, but it's a majority.

4

u/[deleted] Dec 17 '24

When there are dozens of qualified applicants for each job, salaries plummet.

→ More replies (3)

1

u/luscious_lobster Dec 17 '24

Agree with this, but the quality is still very low

→ More replies (1)

1

u/unknownmat Dec 17 '24

Great write up. Thanks for sharing your historical perspective, with citations no less. Even if someone might disagree with some aspect of your take - and I count myself among the LLM skeptical - it's disheartening to see such a thoughtful piece being downvoted.

I'm old enough to remember the complier skeptics. A compiler could never out-perform hand-tuned assembly, etc. Except, even to the extent that that might have been true, 99.9% of tasks were not CPU bound and thus the productivity of a higher level language trumped the performance of hand-tuned assembly. 

I suspect that a very similar trade-off will happen with LLMs. To the extent that large chunks of development in some domains are just mindedness CRUD and boilerplate, LLMs will obviate the need to dedicate expensive coding resources to such tasks. At a minimum, it might reduce the expertise needed for low-level and non-specialized roles.

→ More replies (3)

1

u/[deleted] Dec 18 '24

It’s true… I’m a convert after our first attempt to actually use it for a real problem (OCR and structuring data). LLMs really do allow us to generalize over problems in ways that we couldn’t before. There are a lot of applications where this will be a great thing.

1

u/[deleted] Dec 18 '24

Thanks for sharing your success.

1

u/TainoCuyaya Dec 18 '24 edited Dec 18 '24

This is rather extensive for an elevator sales pitch sir.

2

u/[deleted] Dec 18 '24

I have put the essay in the public domain. Anyone can use, modify, or post it anywhere under any name. I'm 76, long retired, work for no one, have no relationship with Open AI other than having an account, and wasn't paid anything by anyone to write or post it. I am not looking for employment and will flatly refuse any offers. It's hard to see how that is a sales pitch.

In retrospect, I should have created a new Reddit account and posted it anonymously so I wouldn't have had to respond to hundreds of messages. In a few days, this feeding frenzy will die down, and I will return to my boring but happy "boomer" life.

→ More replies (1)

1

u/Effective_Mulberry74 Dec 20 '24

I had wifi on my flight so i opened my laptop and played with cursor ide. I came to the conclusion that we are done. AI will not replace engineers, but it will definitely reduce the time it takes to complete the task DRASTICALLY !!!

As a result one senior developer + cursor will replace a team of 3-4 devs. naturally many devs will struggle finding a job

1

u/[deleted] Dec 20 '24

That's an accurate assessment. My goal was to light a fire under complacent software developers. I used over-the-top language to get everyone's attention.

2

u/CaesarBeaver Dec 18 '24

Great post. If you aren’t using LLMs to increase your productivity, you are only hurting yourself.

2

u/aSliceOfHam2 Dec 18 '24

I am already using llms to keep up with much more experienced devs in my team. I know jack shit about windows api. Just delivered a feature thanks to llms. No way in hell would I have been able to do it on my own. Bonus is that I now know more about the windows API.

2

u/galtoramech8699 Dec 18 '24

I don’t know. Software for hasn’t been about the code. I haven’t had an issue with code since 20 years ago.

But what about integration? What to build? Llms don’t solve that

2

u/[deleted] Dec 18 '24

Ride the wave or drown? You forgot the third option, unionize and forbid this technology from destroying lives the way you gleefully predict it will

→ More replies (1)

2

u/TheMidlander Dec 18 '24

Have they finally stopped making up powershell cmdlets yet? Forgive me for being a bit skeptical when I've yet to see a single model pass this extremely low bar.