So, what was up last week, when all of tech suddenly decided that writing software isn't good or useful or interesting?

Cuz, I gotta say, that sucks, and you're all wrong.

Like, I really don't get why so many of you are so eager to have statistical models write code for you.

I've been arguing for literally my whole career that the actual writing isn't the hard part of software development. But wow, did everyone take that in the wrong direction recently.

Understanding the system is the hard and valuable part. And I genuinely don't know how you think you're going to do that if you never get to do any of the safe and easy interactions with the system.

The statistical model is super duper never going to do that understanding for you. That's literally, exactly not what they do. So why are you so eager to give up all the space where you can experiment and make mistakes?
@jenniferplusplus the one benefit I've found is that using it to spit out examples of obscure Win32 API calls can be quite helpful, although I wouldn't actually copy paste the code itself.
@bitflipped @jenniferplusplus I haven't had much success with even getting examples from it, but it has given me useful answers to questions of the form "Do BeOS and Haiku have a native API for X?" when just searching the documentation has run up against the fact I used a different word to describe something. It generally spits out code that has no hope of compiling but contains references to what I need to look up.
@jeremy_list @jenniferplusplus yeah that's pretty much the same as how I use it and the results I get. I don't use it for .net stuff, but when talking about the more esoteric Win32 API calls, some of them can be poorly documented, so it helps point in the right direction.