17
u/btdeviant Sep 21 '24
Lmao… devs aren’t going anywhere for a long long long long time. These are my absolute favorite posts.. a demo of someone asking a model to generate html and people like, “OMG ITS OVER FOR DEVS”.
There’s still critical services running in <insert industry> written in COBOL with Mt Everest levels of absurdly complex technical debt that’s been stacked up for decades teetering atop it. There’s millions of small to medium sized companies with half-baked architectural and design patterns held together by hopes and wishes that would turn the best models into the equivalent of a gurgling nematode on benzos…
“Well the LLM could just recreate from scratch!”, you might be thinking. Sure.. yeah, for maybe .00000001% of companies that decided to take the risk and investment to actually see that through. And maybe .001% of those companies actually have their features defined and up to date in such a way that would make an entire re-arch actually viable.
-1
u/IndividualParsnip236 Sep 22 '24
Have you ever fed your entire codebase to an LLM and just asked it certain questions about how to implement x or y? For example, asking an LLM to make an open source contribution to a project?
3
u/btdeviant Sep 22 '24 edited Sep 22 '24
Respectfully, there’s a huge, fundamental difference between a codebase and a repository - I think you're referring to the latter? And by “fed” do you mean finetuned or trained?
Most companies do not operate within a single repository. They have a product or products that span services across multiple repositories, but personally I don't think it matters... Depending on the architecture of the product or project, the contracts between those services can vary on their clarity that is very difficult for an LLM to glean from just looking at the code of a single repo alone. Further, they're being updated constantly... each merge to the primary or release branch has the potential to significantly reduce the quality of the output provided by the model since it's effectively out of date.
For example, in event-based architectures with a lot of async, serverless workloads (each of which could be managed in their own repo), an LLM would simply not be able to provide meaningful output without a tremendous amount of training... and keep in mind, that each update to each service or serverless function, be it a lambda or an sqs topic contract or whatever, would require additional training. It might be able to understand the scope of what's in a particular repo or function, but how that is integrated and works within the overall product would be a challenge given the contextual and compute limits.
Lets use a more more simple example. Lets say a stack, or codebase, has two services managed in two different repositories that has configuration defined using a relational database that has a clean separation of concerns in it's data domain, each service using it's own schema. The code for each service in the head commit is approximately 1 MB.
Without a significant amount of constant training on the services and schemas for every update made, an LLM would abjectly fail to provide meaningful output as it simply would not be able to accurately understand the integrations. Every single commit to head that modified the code would require fine tuning the model.
Given you have 15 years of experience, I think you can see where this is going - for most companies that don't have unlimited budget, this is impractical and extraordinarily expensive.
0
u/IndividualParsnip236 Sep 22 '24 edited Sep 22 '24
I do not agree with much of anything you say nor do I find it makes sense to me. By "feeding it to am LLM" I do not mean training it on the code. I literally mean simply using am entire codebase as input for a service like a conversational AI or the like. There's no reason either that you couldn't just feed all of a company's code, while currently may be expensive, to some AI.
You would not need to train it on your codebase. That would be a very comparatively expensive approach.
I don't think there's anything particularly magical about event-based programming with "lots of async," nor "serverless workloads," nor anything complex about various interoperable code or services which use relational databases.
While it is currently possibly expensive, and maybe some current limitations regarding token size and some other small factors might hold this approach back from currently applying it easily and practically, it is clearly inevitable, in my opinion.
1
u/btdeviant Sep 22 '24
Okay, that's fine for you to not understand and feel compelled to disagree, but that doesn't really change anything. I think there seems to be a conflation of terms that may be causing confusion here. "Event based programming" is not the same as "event based architecture". A "codebase" is not the same as a package or a repository. These basic fundamentals you seem to be confusing and predicting your position from makes me doubt your statement that you have "15 years of experience".
Regardless, can we agree that "codebase" is a general term used to define the sum of all code for a software based product? I think that would be a good place to start.
There's no reason either that you couldn't just feed all of a company's code, while currently may be expensive, to some AI.
Absolutely there is... There's three primary reasons. First being contextual limits, second being change frequency of the code that makes up the codebase, and third being the quality of the contextual data the model would require to be able to understand the changes constantly being made to the code.
I don't think there's anything particularly magical about event-based programming with "lots of async," nor "serverless workloads," nor anything complex about various interoperable code or services which use relational databases.
No one said anything about magical. This is just basic technical complexity from abstraction layers and contract definitions, or lack thereof. If I have two services that each use a relational db with poorly defined or overlapping data domains that are not clearly defined, there's simply no "codebase" you could feed an LLM to provide it with the data it needs provide output with any quality on that. This is a concept decades old in Machine Learning called "garbage in, garbage out".
While I appreciate your passion and sentiments, it seems like you have a lot of opportunities to learn about some of the basics around software engineering, let alone LLMs. Good luck.
0
u/IndividualParsnip236 Sep 22 '24
I'm sorry but I am not buying what you're selling at all.
I hope you have a nice day.
1
u/btdeviant Sep 22 '24
lol I’m just selling reality based off of, you know, actually working professionally in the industry for companies whose products you probably use multiple times a day but okay.
18
12
u/creaturefeature16 Sep 21 '24
Yawn. Sensationalist TikTok level bullshit. Let's downvote and move on.
1
u/MagnaticBull Sep 21 '24
Yes, I just tried it right now. It is weird and nasty, could not even write a simple material chips on a component.
However, the idea is amazing as it is, it keeps feeding itself until the app completes. It tries to ask design level questions and then automatically commits, runs the app, searches the error.
Doesn't work as of now, but very promising. I used Gemini 1.5, may Claude or something else would give better results.
6
u/No_Flounder_1155 Sep 21 '24
now deploy it, scale it to a million users. Add authentication... The list goes on
5
u/Cold-Ad2729 Sep 21 '24
Do you have to be obnoxious to be a developer from now on??
Edit: I’m being facetious. But still, I hate this bullshit
2
3
u/Brave-History-6502 Sep 21 '24
This demonstrates nothing in terms of building something complex and innovative
1
2
1
u/Genbeth Sep 21 '24
now we need an updated version of the old swing tire meme😹about developers and requirements😅😅
1
1
1
u/Dear-Potential-3477 Sep 22 '24
AI is there to help devs not make us history, one man start ups will start being normal
1
u/One_Contribution Sep 22 '24
What you fail to account for is that the very moment LLMs are capable enough to replace all devs, they will also replace the software these devs write, as well as the people that likely would use this software, hope your alternate plans cover that.
1
u/MrWeirdoFace Sep 22 '24
Disagree. Devs have more powerful tool, also previously non-devs become devs.
1
u/johns10davenport Professional Nerd Sep 24 '24
Boo, sensationalist noise. This is the exact kind of content that's hurting our ability to REALLY get the most out of this technology.
1
1
u/Repulsive-Kick-7495 Mar 02 '25
Yeah right!! This is influencer shit 💩. No dev familiar with how complex the requirements can get will make dumb calculator, transcribing app which practically has 2-4 states or FSM claims that devs are history
1
1
u/Z0OMIES Sep 22 '24
Yea I’ve never coded before but managed to build a python API thingo for my job so I can pull reports with a single button click
0
-5
0
Sep 21 '24
[deleted]
0
-8
u/Ok_Abrocona_8914 Sep 21 '24
If there's one thing LLMs are good at is suggesting good features for anything.
0
Sep 21 '24
[deleted]
-5
u/Ok_Abrocona_8914 Sep 21 '24
Random stuff? You realize you can just present your codebase as a starting point and then dev on any stack you want right? And that's today, imagine in 5 years.
2 years ago Devs were untouchable, now they are so insecure they cry online about getting / not getting replaced. Imagine the scenes in 2030.
-2
u/IndividualParsnip236 Sep 22 '24
I keep hearing this argument. I think it's the biggest and most common... I don't know how else to say this, I'm sorry if this is rude, but cope I hear from devs.
Software engineers are NOT paid a lot of money for their ability to make concrete requirements out of abstract requests. They are specifically paid for the amount of labor time invested in the knowledge and technical expertise they can apply, basically. If it weren't so, and the cost of labor power was not proportional to the amount of personal investment to augment the labor power, then it would basically be unskilled labor. Once we acknowledge that, we can identify which areas of augmentation of labor power for a developer are the most time consuming, and learning by experience how to reify or make concrete the abstract ideas of someone with the capital is not a very technical skill and one certainly not limited to the computer science people.
1
Mar 10 '25
[removed] — view removed comment
1
u/AutoModerator Mar 10 '25
Sorry, your submission has been removed due to inadequate account karma.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
0
Sep 22 '24
[removed] — view removed comment
0
u/IndividualParsnip236 Sep 22 '24
I actually encourage you to check out an open source project you like, fees it to some AI, then ask how to create some feature for it
34
u/NextgenAITrading Sep 21 '24
What's gonna happen when there's a bug or more complex requirements?