| ▲ | lrvick 2 hours ago |
| I did things the old way for 25 years and my carpal tunnels are wearing out. LLMs let me produce the same quality I always have with a lot less typing so not mad at that at all. I review and own every line I commit, and feel no desire to go back to the old way. What scares the shit out of me are all these new CS grads that admit they have never coded anything more complex than basic class assignments by hand, and just let LLMs push straight to main for everything and they get hired as senior engineers. It is like hiring an army of accountants that have never done math on paper and exclusively let turbotax do all the work. If you have never written and maintained a complex project by hand, you should not be allowed to be involved in the development of production bound code. But also, I feel this way about the industry long before LLMs. If you are not confident enough to run Linux on the computer in front of you, no senior sysadmin will hire you to go near their production systems. Job one of everyone I mentor is to build Linux from scratch, and if you want an LLM build all the tools to run one locally for yourself. You will be way more capable and employable if you do not skip straight to using magic you do not understand. |
|
| ▲ | adamddev1 2 hours ago | parent | next [-] |
| > It is like hiring an army of accountants that have never done math on paper and exclusively let turbotax do all the work. It's not though. It's fundamentally different because TurboTax will still work with clear deterministic algorithms. We need to see that the jump to AI is not a jump from hand written math to calculators. It's a jump from understanding how the math works to another world of depending on magic machines that spit out numbers that sort of work 90% of the time. |
| |
| ▲ | bluefirebrand 22 minutes ago | parent [-] | | Imagine if Math calculators were just subtly wrong some percentage of the time for use cases that people use dozens or hundreds of times a day. If you could punch in the same math formula 100 times and get more than 1 answer on a calculator, most people wouldn't trust those for serious work. They probably wouldn't think that the calculator makes them faster either |
|
|
| ▲ | thesz 2 hours ago | parent | prev | next [-] |
| From what I remember, typical new C++ debugged code speed is about 20-25K lines per year, lines that are non-blank, non-comment and not completely verifiable by compiler. E.g., standalone bracket or comma or semicolon are not lines of code, function header is too not a line of code, but computation, conditions and loops are. This is from old IBM statistics, I learned about it circa 2007. If we assume that there are 50 weeks per year, this gives us about 400-500 lines of code per week. Even at long average 65 chars per line, it goes not higher than 33K bytes per week. Your comment is about 1250 bytes long, if you write four such comments per day whole week, you would exceed that 33K bytes limit. I find this amusing. |
| |
| ▲ | slopinthebag an hour ago | parent [-] | | LOL. If you look at their comment history, they sure are typing a lot of characters for their wrists. | | |
| ▲ | thesz 43 minutes ago | parent [-] | | Yes, I checked their history of comments before posting. It made me confident that I hit the right note. My software engineering experience longs almost 37 years now (December will be anniversary), six-to-seven years more than Earth's human population median age. I had two burnouts through that time, but no carpal tunnel syndrome symptoms at all. When I code, I prefer to factor subproblems out, it reduces typing and support costs. |
|
|
|
| ▲ | sho_hn 2 hours ago | parent | prev | next [-] |
| > If you have never written and maintained a complex project by hand, you should not be allowed to be involved in the development of production bound code. So only the old hands allowed from now on, or how are we going to provide these learning opportunities at scale for new developers? Serious question. |
| |
| ▲ | hallway_monitor 2 hours ago | parent | next [-] | | Junior developers have always been a lot less effective than senior developers. We will need new senior developers so we will need to train junior developers. Maybe we train them by forcing them to do things the hard way. The slow way. By hand. Because if we let them do things the fast way they are going to cause some serious damage. | | |
| ▲ | SlinkyOnStairs an hour ago | parent [-] | | Who's going to be doing that? Employers were already refusing to hire juniors, even when 0.5-1 years' salary for a junior would be cheaper than spending the same on hiring a senior. They'll never accept intentionally "slower" development for the greater good. | | |
| ▲ | jacobsenscott 41 minutes ago | parent | next [-] | | > They'll never accept intentionally "slower" development for the greater good. That comes post Chernobyl. | |
| ▲ | 8note an hour ago | parent | prev [-] | | internships for one. my last summer intern did everything the manual way, except for a chunk where I wanted him to get something done fast without having to learn all the underlying chunks |
|
| |
| ▲ | lrvick 2 hours ago | parent | prev | next [-] | | The same way I learned 25 years ago still works today. Volunteer on open source projects. Always happy to mentor people at stagex and hashbang (orgs I founded). Also being a maintainer of an influential open source project goes on a resume, and helps you get seen in a crowded market while boosting your skills and making the world better. Win/win all around. | | | |
| ▲ | rafaelmn 2 hours ago | parent | prev [-] | | Even by pessimistic progress projections AI will be better than most at coding before this is a long term issue. And the output multiplier I'm seeing I suspect the number of SWEs needed to achieve the same task is going to start shrinking fast. I don't think SWE is a promising career to get started in today. | | |
| ▲ | mwwaters an hour ago | parent | next [-] | | There’s certainly a lot of uncertainty. But pro-AI posts never seem to pin themselves down on whether code checked in will be read and understood by a human. Perhaps a lot of engineers work in “vibe-codeable” domains, but a huge amount of domains deal with money, health, financial reporting, etc. Then there are domains those domains use as infrastructure (OS, cloud, databases, networking, etc.) Even where it is non-critical, such as a social media site, whether that site runs and serves ads (and bills for them correctly) is critical for that company. | |
| ▲ | lrvick 2 hours ago | parent | prev | next [-] | | But you have to be good at SWE to be good at security engineering and sysadmin, and the demand there is skyrocketing. We have a completely broken internet with almost nothing using memory encryption, deterministic builds, full source bootstrapping, secure enclaves, end to end encryption, remote attestation, hardware security auth, or proper code review. Decades of human cognitive work to be done here even with LLM help because the LLMs were trained to keep doing things the old way unless we direct them to do otherwise from our own base of experience on cutting edge security research no models are trained on sufficiently. | |
| ▲ | 8note an hour ago | parent | prev | next [-] | | im not convinced that it will. you dont notice it when you are only looking at your own harness results, but the llm bakes so very much of your own skills and opinions into what it does. LLMs still regurgitate a ton. | |
| ▲ | jazz9k 26 minutes ago | parent | prev [-] | | Perhaps at some point, but tokens are expensive and the major providers are burning through cash. I suppose it's like bandwidth cost in the 90s. At some point, it becomes a commodity. |
|
|
|
| ▲ | teruakohatu 2 hours ago | parent | prev | next [-] |
| > It is like hiring an army of accountants that have never done math on paper and exclusively let turbotax do all the work. That is exactly been the situation for years. Once graduated accountants are not doing maths. They are using software (Exel, Xero etc.). They do need to know some basic formulas eg. NPV. What they need to know is the law, current business practices etc. |
|
| ▲ | einpoklum an hour ago | parent | prev [-] |
| > LLMs let me produce the same quality I always have with a lot less typing If that's true, then you likely used to produce slop for code. :-( > I did things the old way for 25 years and my carpal tunnels are wearing out. You wrote so much code as to wear out your carpal tunner? Are you sure it isn't the documentation and the online chatter with your peers? :-( ... anyway, I know it's corny to say, but - you should have, and shoudl now, improve the ergonomics of your setup. Play with things like the depth of your keyboard on your desk, the height of the chair and the desk, with/without chair handrests, keyboard angle, etc. > Job one of everyone I mentor is to build Linux from scratch "from scratch" can mean any number of things. |