zlacker

[parent] [thread] 1 comments
1. lordfr+(OP)[view] [source] 2022-12-16 15:58:07
I agree with everything you're saying. It surprises me that people can call themselves programmers and not know the basics of computer computation, but it seems that just means I have an older/more-narrow definition of what "programming" is compared to what it has become.

I still stand behind my main point, which is that some of these jobs will be automated before others. Apparently the skill set differences between different kinds of programmers even wider than I thought it was. So instead of talking about whether AI will/won't automate programming in general, it's more productive to discuss which kind of programming AI will automate first.

replies(1): >>unity1+SR1
2. unity1+SR1[view] [source] 2022-12-17 01:25:34
>>lordfr+(OP)
> narrow definition of what "programming" is compared to what it has become.

Isnt that the case in every field in technology? Way back engineers used to know how circuits worked. Now network engineers never deal with actual circuits themselves. Way back back programmers had to do a lot of things manually. Now the underlying stack automates much of that. On top of TCP/IP, we laid the WWW, then we laid web apps, then we laid CMSes, then we came to such a point that CMSes like WordPress has their own plugins, and the very INDIVIDUAL plugins themselves became expertise fields. When looking for someone to work on a Woocommerce store, people dont look for WordPress developers, or plugin developers. They look for 'Woocommerce developers'. WP became so big that every facet of it became specializations in itself.

Same for everything else in tech: We create a technology, which enables people to build stuff on it, then people build so much stuff that each of those became individual worlds in themselves. Then people standardize that layer and then move on to building next level up. It goes infinitely upwards.

[go to top]