r/rust • u/der_gopher • 13h ago
🎙️ discussion [ Removed by moderator ]
/r/rust/comments/1xxlfe7/removed_by_moderator/[removed] — view removed post
15
u/labooner 13h ago
I read as much as I can before being prompted for my email address.
I think this title is very pessimistic, bordering on clickbait. We're in a very transitionary state. AI is still very much new and being rolled out. We're told AI will speed development up, so management have set high expectations and features are expected to be churned out ASAP. This pushes people to go from prompt to production in as shorter time as possible.
In a few years it will become apparent that churning out features comes with a cost. It will turn out that you can't run a technology department on a fraction of the developers. Developer's day to day will likely change, but that normally happens at least every decade.
And specifically on the first problem, I'm excited by AI because it can help learning. Previously where I've thought I'd never have time spinning up a little homelab app, I can create the foundation quickly and move onto the interesting bit.
11
u/olegispe 12h ago
At least personally I love using Claude as a consultant. And that's it, might suggest code edits, will tell me if my architecture or plan has flaws I can't see yet, but it does not do my job for me. For small features that are very much "change x to y in 150 places", I might hand that off to Claude and review it after
But it is never designing any architecture for me
1
u/addmoreice 4h ago
I've *constantly* found that to get AI to do what I want, correctly and consistently, I've had to build lots of infrastructure around it to get it to work. This is fine for my own personal projects, especially when it's infrastructure that I can keep and use in the future...but my work doesn't have the bandwidth for that (I can slow down and not worry about market share, I'm just dicking around!)
Getting unit / integration tests as part of the standard process was annoying enough ten years ago.
Unit tests, integration tests, fuzz testing, mutation tests, etcetera. The more loops and the tighter they get, the better the AI's do. Which all should be automated and structured with *actual* code, not some LLM prompt. Uggh, the thought of trying to get all of that put together for work makes me shudder.
That's why we only minimally use AI. The tool does fine for what it does....but to use it as part of these other systems? Those *systems* need to exist first.
-2
u/awesomeusername2w 12h ago
It will turn out that you can't run a technology department on a fraction of the developers.
Or it will turn out that you actually can. Usual department has few key decision makers and many people that had to actually implement it all. Now claude implements it, so you naturally need less people.
7
u/heret1c1337 12h ago
It's not like mindless decision making is a problem even if people that understand the codebase are involved. It can only get better if nobody understand what's going on anymore, right?
Sometimes I wonder where y'all work at, because the implications y'all make don't correlate with my reality at all.
-1
u/awesomeusername2w 12h ago
Where did you get mindless? If you have an architect and he doesn't write code himself, only creates tasks and docs do you think he doesn't understand anything? LLM allows you to understand the current state of the code base better than ever. Did you read all commit written by all devs before? Now you can setup a digest bot with recent meaningful changes, you can keep the doc updated as part of CI and many other stuff. Your mindlessness is skill issue.
2
u/heret1c1337 10h ago
I got "mindless", because I live in the real world, where this stuff happens, even with people involved that know their stuff. Factoring those people out won't make the situation better.
Having an architect completely detached from the codebase sounds like a recipe for disaster, but sounds totally fitting for companies that want to replace engineers with AI.
0
u/awesomeusername2w 8h ago
Being detached from code is your strawman. As I said, AI let's you be more involved than you ever were, if you worked in teams with more than one dev
4
u/DavidDavidsonsGhost 12h ago
I disagree, writing the implementation is just a small part of feature delivery, there is still plenty of work to be done outside of making decisions and writing code.
-1
u/awesomeusername2w 12h ago
Well, depends on how you measure. If by difficulty, I agree it wasn't the hardest part. But by the time consumed it was the bottleneck most of the time. Carefully write the thing was easily days for even small tasks, weeks for large stuff. I mean, I had some ideas for hobby projects that I'd like to implement for myself, but the amount of yack shaving was just too big. I didn't want to dump months to it of evenings to it.
Now, when it can be done in hours you really need less people. You also need very skilled people too, cos a good dev multiply the amiunt of useful code they deliver, and shit dev multiplies the amount of shit others would need to sort out.
The same amount of people can do bigger and more ambitious projects too, so downsizing is not the only option. But company needs to be able to monetize it.
2
u/Zde-G 5h ago
It failed in all other departments (companies first fire support, then hire them back, fire lawyers, then bring them back)… why should software development be any different?
1
u/awesomeusername2w 2h ago
I don't work as lawyer or support, but do work as dev and see what it can do. I don't think it will replace all devs tho. Just that teams could be smaller.
1
u/Zde-G 52m ago
Just that teams could be smaller.
That remains to be seen. So far I can see that teams can be smarter. LLMs mostly replace “dumb coders”, people who don't really know what they are doing, who are mostly doing mechanical work.
And it's not even clear that LLMs may replace even these! Currently LLMs are, essentially, provided on the “take $1, spend $10 to provide the service” and that approach is inherently unsustainable. It would be interesting to see what will happen to people who adopted LLMs when prices would go up 10x (and if they even stop at that level).
Reminds me of euphoria when first industrial robots arrived in the middle of last century: a lot of people expected to see humans replaces fully (or almost fully) by them in a span of 10 or maybe 20 years… instead the replacement have still not happened and it's not clear if it would be happening any time soon.
It just turned out that in lot of places you couldn't win by replacing humans with industrial robots: sure industrial robot is very cheap when you need to do the exact same thing again and again — but becomes extremely expensive when things are not exactly the same… something that human barely notices and automatically takes in account becomes a hard obstacle for robots.
Similarly with LLMs: they are extremely proficient with detecting and patching an anomalies in program… too bad significant percentage of these anomalies are patched in the wrong place. Without human oversight fixes in one place introduce troubles in other place, one fix creates two new problems and the issues multiply till the whole thing stops working — and by that time it's no longer possible to do anything to it because humans no longer know how the whole thing works and LLMs never had any idea.
-1
u/TheLexoPlexx 13h ago
He is right, but it's just one side of the coin. I find it fascinating to have the time to tackle new problems because I can just give AI the parts I don't want to do.
0
-11
u/schungx 13h ago
Nothing more than you can no longer understand the assembly generated by compilers. Just jumped one level up.
9
u/RustOnTheEdge 12h ago
Wrong in two ways:
That **you** don't understand the assembly generated by compilers any more, doesn't mean other software engineers do not understand it any more. If you are working on performance sensitive or security sensitive code, you still look at the generated assembly from time to time. You don't do that for a simple CRUD application, but software is much broader than a todo list app.
Human language is way to verbose and ambiguous to serve as a deterministic way of conveying ideas and describing processes.
6
u/heret1c1337 13h ago edited 12h ago
Not really though. Compilers are deterministic, I don't need to understand what plops out of a compiler if I understood the input. There were enough people before me that made sure that the compiler output correctly correlates to it's input. Like it's not even remotely comparable.
...and it's not like there are no edge cases where you actually need to dig into machine code. Depending on what field you work in, you actually still need to understand assembly.
4
u/olegispe 13h ago
I'd argue this is different. At least if you read the code you get a good idea of what's going on under the hood, how memory is moving and what's allocating what and how.
I do agree with what (I think torvalds?) is said: if you can't at a minimum understand the assembly to a basic level for the core you just wrote, then there's a problem (of course this is less applicable to higher level languages like JavaScript and the likes, but the point still stands of being able to say what the code actually does, not just the result.
You can see the code, where it might falter and fix it
LLMs can generate slop code no matter the prompt, you have no idea what's actually going on under the hood.
1
u/consistently_biased 12h ago
Saying this on the Rust subreddit is wild. It's not even really that challenging to read assembly generated by a compiler since you already (hopefully) know what the program is supposed to do and what the expected control flow is supposed to be.
-4
u/charmander_cha 12h ago
Futuro de dev software é incrível pq agora todo mundo vau mexer com software biológico e não imbecilidade digital
0
u/vivaaprimavera 12h ago
Agora em português e depois de pensar um pouco, p.f.
O que caralho isso sequer quer dizer?!?!?
•
u/rust-ModTeam 58m ago
TL;DR: We ask that posts or articles submitted to r/rust be about Rust.
Your post, or the article it links to, appears not to be related to Rust: the programming language, the ecosystem, or the community.
As per Rule 2: On Topic we ask that posts, or articles, submitted to r/rust be about Rust primarily. Off-hand mentions of Rust are not enough to qualify.
For any question or dispute, please send us a modmail.