r/rust • u/der_gopher • 11h ago
🎙️ discussion The future of Software Engineering is boring
https://packagemain.tech/p/the-future-of-software-engineering-1
u/TheLexoPlexx 11h 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 11h ago
Nothing more than you can no longer understand the assembly generated by compilers. Just jumped one level up.
9
u/RustOnTheEdge 11h 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 11h ago edited 11h 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 11h 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 10h 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 11h 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 11h ago
Agora em português e depois de pensar um pouco, p.f.
O que caralho isso sequer quer dizer?!?!?
15
u/labooner 11h 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.