zlacker

[parent] [thread] 6 comments
1. themag+(OP)[view] [source] 2022-12-15 20:59:43
I never thought leopards would eat MY face!

Creative professionals might take the first hit in professional services, but AI is going to come for engineers at a much faster and more furious pace. I would even go so far as to say that some (probably a small amount) of the people who have recently gotten laid off at big tech companies may never see a paycheck as high as they previously had.

The vast majority of software engineering hours that are actually paid are for maintenance, and this is where AI is likely to come in like a tornado. Once AI hits upgrade and migration tools it's going to eliminate entire teams permanently.

replies(4): >>willsm+E1 >>scj+e4 >>SkyPun+Z9 >>grandm+Ue
2. willsm+E1[view] [source] 2022-12-15 21:06:45
>>themag+(OP)
> The vast majority of software engineering hours that are actually paid are for maintenance

Do you have a source for that? Doesn't match my experience unless your definition of maintenance is really broad

replies(2): >>themag+t8 >>itroni+09
3. scj+e4[view] [source] 2022-12-15 21:21:54
>>themag+(OP)
I believe the current generation of AI would be better suited to augmenting human understanding of code (through static analysis tools and the like), rather than generating it.

On an infinite timeline humans will no longer be needed in the generation of code (we hopefully will still study and appreciate it for leisure), but I doubt we're there yet.

◧◩
4. themag+t8[view] [source] [discussion] 2022-12-15 21:44:20
>>willsm+E1
Just experience, but my definition is pretty broad. Once you get out of the valley most of what pays well (banking, finance, telecom, analytics, industrial, etc.) is maintenance code IMO. Basically anything that doesn't come out real R&D budget, even if it is a "new feature", is maintenance to me at this point.
◧◩
5. itroni+09[view] [source] [discussion] 2022-12-15 21:46:24
>>willsm+E1
The caveat there is 'paid hours'. The current working model for the industry is that all software engineers leetcodeuberhack on open source repos at night and by day have paying jobs maintaining companies' systems that use open source.
6. SkyPun+Z9[view] [source] 2022-12-15 21:51:22
>>themag+(OP)
> The vast majority of software engineering hours that are actually paid are for maintenance, and this is where AI is likely to come in like a tornado.

I have the exact, almost completely opposite opinion. Greenfield is where AI going to shine.

Maintenance is riddled with "gotcha's", business context, and legacy issues that were all handled and negotiated over outside of the development workflow.

By contrast, AI can pretty easily generate a new file based on some form of input.

7. grandm+Ue[view] [source] 2022-12-15 22:18:12
>>themag+(OP)
> The vast majority of software engineering hours that are actually paid are for maintenance, and this is where AI is likely to come in like a tornado. Once AI hits upgrade and migration tools it's going to eliminate entire teams permanently.

There's been huge improvements in automating maintenance, and yet I've never once heard someone blame a layoff on e.g. clang-rename (which has probably made me 100x more productive at refactoring compared to doing it manually.)

I'd even say your conclusion is exactly backwards. The implicit assumption is that there's a fixed amount of engineering work to do, so any automation means fewer engineers. In reality there is no such constraint. Firms hire when the marginal benefit of an engineer is larger than the cost. Automation increases productivity, causing firms to hire more, not less.

[go to top]