22 ms·
After all, if we lose the joy in our craft, what exactly are we optimizing for? Solving problems for real people. Isn't the answer here kind of obvious? Our f
by tptacek 2y ago
After all, if we lose the joy in our craft, what exactly are we optimizing for?
Solving problems for real people. Isn't the answer here kind of obvious?
Our field has a whole ethos of open-source side projects people do for love and enjoyment. In the same way that you might spend your weekends in a basement woodworking shop without furnishing your entire house by hand, I think the craft of programming will be just fine.
- frollogaston 2y agoSame as when higher-level languages replaced assembly for a lot of use cases. And btw, at least in places I've worked, better traditional tooling would replace a lot more headcount than AI would.
- codr7 2y agoNot even close, those were all deterministic, this is probabilistic.
- tptacek 2y agoThe output of the LLM is probabilistic. The code you actually commit or merge is not.
- rozap 2y agoi'm just vibing though, maybe i merge, maybe i don't, based on the vibes
- jaggederest 2y agoThat sounds like a lot of work, better ask a LLM whether to merge.
- genewitch 2y agoIt does the PR for me, too
- frollogaston 2y agoAnd argues on behalf of you in the PR. "You're absolutely right, this should not be merged."
- jll29 2y agoYes. The output of the LLM is determined by the weights (parameters of the artificial neural network) estimated in the training as well as a pseudo-random number generator (unless its influence, called "temperature", is set to 0). That means LLMs behave as "processes" rather than algorithms, unlike any code that may be generated from them, which is algorithmic (unless instrcuted otherwise; you could also tell an LLM to generate an LLM).
- discreteevent 2y agoThe parent is saying that when higher-level languages replaced assembly languages you only had to learn the higher level language. Once you learned the higher level language the machine did precisely what you specified and you did not have to inspect the assembly language to make sure it was compliant. Furthermore you were forced to be precise and to understand what you were doing when you were writing the higher level language. Now you don't really have to be precise at any level to get something 'working'. You may not be familiar with the generated language or libaries but it could look good enough (like the assembly would have looked good enough). So, sure, if you are very familiar with the generated language and libraries and you inspect every line of generated code then maybe you will be ok. But often the reason you are using an LLM is because e.g. you don't understand or use bash frequently enough to get it to do what you want. Well, the LLM doesn't understand it either. So that weird bash construct that it emitted - did you read the documentation for it? You might have if you had to write it yourself. In the end there could be code in there that nothing (machine or human) understands. The less hard-won experience you have with the target and the more time-pressed you are the more likely it is that this will occur.
- pjmlp 2y agoThe code that the compiler generates, especially in the C realm, or with dynamic compilers is also not regular, hence the tooling constraints in high integrity computing environments.
- ben-schaaf 2y agoExactly. If LLMs were like higher level languages you'd be committing the prompt. LLMs are actually like auto-complete, snippets, stackoverflow and rosetta code. It's not a higher level of abstraction, it's a tool for writing code.
- frollogaston 2y agoIt's not a higher-level language, I mean it's a productivity tool. It's not going to take away the joy or demand for coding, like how C didn't ruin things by cheapening assembly creation.
- frollogaston 2y agoSo what? I know most compilers are deterministic, but it really only matters for reproducible builds, not that you're actually going to reason about the output. And the language makes few guarantees about the resulting instructions.
- eddd-ddde 2y agoYet the words you chose to use in this comment were entirely modelled inside your brain in a not so different manner.
- pjmlp 2y agoI already see this happening with low code, SaaS and MACH architectures. What used to be a project doing a CMS backend, now is spent doing configurations on a SaaS product, and if we are lucky, a few containers/serveless for integrations. There are already AI based products that can automate those integrations if given enough data samples. Many believe AI will keep using current programming languages as translation step, just like those Assembly developers thought compiling via Assembly text generation and feeding into an Assembly would still be around.
- achierius 2y ago> just like those Assembly developers thought compiling via Assembly text generation and feeding into an Assembly would still be around Confused by what you mean. Is this not the case?
- pjmlp 2y agoNo, only primitive UNIX toolchains still do this, most modern compilers generate machine code directly, without having to generate Assembly text files and executing the Assembler process on it. You can naturally revert to old ways, by asking for the Assembly manually, and call the Assembler yourself.
- EasyMarion 2y agosolving real problems is the core of it, but for a lot of people the joy and meaning come from how they solve them too. the shift to AI tools might feel like outsourcing the interesting part, even if the outcome is still useful. side projects will stick around for sure, but i think it's fair to ask what the day-to-day feels like when more of it becomes reviewing and prompting rather than building.
- ToucanLoucan 2y ago> Solving problems for real people. Isn't the answer here kind of obvious? Look at the majority of the tech sector for the last ten years or so and tell me this answer again. Like I guess this is kind of true, if "problems for real people" equals "compensating for inefficiencies in our system for people with money" and "solutions" equals "making a poor person do it for them and paying them as little as legally possible."
- tptacek 2y agoThose of us who write software professionally are literally in a field premised on automating other people's jobs away. There is no profession with less claim to the moral high ground of worker rights than ours.
- frollogaston 2y agoYeah I see it as fair game
- dml2135 2y agoIt’s not automation that is the problem, it’s that the fruits of that automation disproportionately go to those at the top. Don’t blame software engineering for that, blame capitalism.
- ToucanLoucan 2y ago> Those of us who write software professionally are literally in a field premised on automating other people's jobs away. Depends what you write. What I work on isn't about eliminating jobs at all, if anything it creates them. And like, actual, good jobs that people would want, not, again, paying someone below the poverty line $5 to deliver an overpriced burrito across town.
- tptacek 2y agoI think most of the time when we tell ourselves this, it's cope. Software is automation. "Computers" used to be people! Literally, people.
- JohnFen 2y ago> Solving problems for real people. Isn't the answer here kind of obvious? No. There are a thousand other ways of solving problems for real people, so that doesn't explain why some choose software development as their preferred method. Presumably, the reason for choosing software development as the method of solving problems for people is because software development itself brings joy. Different people find joy in different aspects even of that, though. For my part, the stuff that AI is promising to automate away is much of the stuff that I enjoy about software development. If I don't get to do that, that would turn my career into miserable drudgery. Perhaps that's the future, though. I hope not, but if it is, then I need to face up to the truth that there is no role for me in the industry anymore. That would pretty much be a life crisis, as I'd have to find and train for something else.
- fragmede 2y agoI'm probably just not as smart or creative as you, but say my problem is I have a ski cabin that I want to rent it to strangers for money. Nevermind a thousand, What are 100 ways without using software that I could do something about that, vs listing it on Airbnb?
- JohnFen 2y agoI was speaking about solving people's problems generally. It's easy to find specific problems that are best addressed with software, just as it's easy to find specific problems that can't be addressed with software.
- simonw 2y ago"There are a thousand other ways of solving problems for real people, so that doesn't explain why some choose software development as their preferred method." Software development is almost unique in the scale that it operates at. I can write code once and have it solve problems for dozens, hundreds, thousands or even millions of people. If you want your work to solve problems for large numbers of people I have trouble thinking of any other form of work that's this accessible but allows you to help this many others. Fields like civil engineering are a lot harder to break into!