40+ years of coding here. I've been using LLMs all day and getting a large boost from it. That last thing I did was figure out how to change our web server to have more worker processes. It took a half dozen questions to cure a lot of ignorance and drill down the right answer. It would have taken a lot longer with just a search engine. If you're not seeing the large economic advantage of these systems you're not using them like I am.
I think that one of the reasons there's a surprising amount of pushback because a lot of developers don't like the sort of collaborative, unstructured workflow that chat-oriented tools push onto you.
I once worked with someone who was brilliant, but fell apart when we tried to do pair-programming (acturial major who had moved into coding). The verbal communication overhead was too much for him.
This is a really interesting observation that makes a lot of sense to me. I can relate to this and it really helps to explain my own skepticism about LLMs "helping" with programming tasks.
I've always thought of software development as an inherently solo endeavor that happens entirely inside of one's own mind. When I'm faced with a software problem, I map out the data structures, data flows, algorithms and so on in my mind, and connect them together up there. Maybe taking some notes on a sheet of paper for very complex interactions. But I would not really think of sitting down with someone to "chat" about it. The act of articulating a question "What should this data structure look like and be composed of?" would take longer than it would take to simply build it and reason about it in my own brain. This idea that software is something we do in a group socially, with one or more people talking back and forth, is just not the way I operate.
Sure, when your software calls some other person's API, or when your system talks to someone else's system, or in general you are working on a team to build a large system, then you need to write documents and collaborate with them, and have this back-and-forth, but that's always kind of felt like a special case of programming to me.
The idea of asking ChatGPT to "write a method that performs a CRC32 on a block of data" seems silly to me, because it's just not how I would do it. I know how to write a CRC function, so I would just write it. The idea of asking ChatGPT to help write a program that shuffles a deck of cards and deals out hands of Poker is equally silly because before I even finished writing this sentence, I'm visualizing the proper data structures that will be used to represent the cards, the deck, and players' hands. I don't need someone (human or AI) to bounce ideas off of.
There's probably room for AI assistance for very, very junior programmers, who have not yet built up the capability of internally visualizing large systems. But for senior developers with more experience and capability, I'd expect the utility go down because we have already built out that skill.
I consider myself to be fairly senior, and use it all the time for learning new things. I work with some brilliant senior developers who lean on it heavily, but I do think it doesn't mesh with the cognitive styles of many.
There might be something to this; however, N=1, I'm very much the kind of developer who hates pair-programming and falls apart when forced to do it. But it's not the conversation that's the problem - it's other people. Or specifically, my fight-and-flight response that triggers when I am watched and have to keep up with someone (and extreme boredom if the other person can't keep up with me). LLMs aren't people, and they aren't judging me, so they do not trigger this response.
Chat interface is annoying, though. Because it's natural language, I have to type a lot more, which is frustrating - but on the other hand, because it's natural language, I can just type my stream of thought and the LLM understands it. The two aspects cancel out each other, so in terms of efficiently, it's a wash.
