End Of Year Open Tab Bankruptcy Roundup Jamboree, Part 2: AI & Other Tech
I’m declaring bankruptcy on my open tabs; these are all things I’ve had open on my laptop or phone over the last several months, thinking “I should send this to someone? Or Is this a blog post?” Turns out the answer is ‘no’ to both of those, so here they are. Day 2: AI and Other Various Tech Topics
A Coder Considers the Waning Days of the Craft | The New Yorker
At one point, I had a draft of Fully Automated Insults to Life Itself with a whole bunch of empty space about 2/3 down with “coding craft guy?” written in the middle. I didn’t end up using it because, frankly, I didn’t have anything nice to say, and, whatever. Then I had two different family members ask me about this over the holidays in a concerned tone of voice, so okay, lets do this.
This guy. This freakin’ guy. Let’s set this up. We have New Yorker article where a programmer talks about how he used to think programming was super-important, but now with the emergence of “the AIs”, maybe his craft is coming to an end. It’s got all the things that usually bother me about AI articles: bouncing back and forth between “look at this neat toy!” and “this is utterly inevitable and will replace all of us”, a preemptively elegiac tone, a total failure to engage with any of the social, moral, or political issues around “AI”, that these “inevitable changes” are the direct result of decisions being made on purpose by real people with an ideology and an agenda. All that goes unacknowledged! That’s what should bother me.
But no, what actually bothered me was that. I spent the whole time reading this thinking “I’d bounce this guy in an interview so fast.” Because he’s incredibly bad at his chosen profession. His examples of what he used GPT for are insane. Let’s go to the tape!
At one point, we wanted a command that would print a hundred random lines from a dictionary file. I thought about the problem for a few minutes, and, when thinking failed, tried Googling. I made some false starts using what I could gather, and while I did my thing—programming—Ben told GPT-4 what he wanted and got code that ran perfectly.
Fine: commands like those are notoriously fussy, and everybody looks them up anyway. It’s not real programming.
Wait, what? What? WHAT! He’s right, that’s not real programming, but a real programmer can knock that out faster than they can write. No one who writes code for a living should have to think about this for any length of time. This is like a carpenter saying that putting nails in straight isn’t real carpentry. “Tried Googling?” Tried? But then he follows up with:
A few days later, Ben talked about how it would be nice to have an iPhone app to rate words from the dictionary. But he had no idea what a pain it is to make an iPhone app. I’d tried a few times and never got beyond something that half worked. I found Apple’s programming environment forbidding. You had to learn not just a new language but a new program for editing and running code; you had to learn a zoo of “U.I. components” and all the complicated ways of stitching them together; and, finally, you had to figure out how to package the app. The mountain of new things to learn never seemed worth it.
There are just under 2 million iOS apps, all of them written by someone, usually many someones, who could “figure it out”. But this guy looked into it “ a few times”, and the fact that it was too hard for him was somehow… not his fault? No self-reflection, there? “You had to learn not just a new language but a new program…”? Any reasonably senior programmer is fluent in at least half of the TIOBE top 20, uses half-a dozen IDEs or tools at once.
But that last line in the quote there. That last line is what haunts me. “The mountain of new things to learn never seemed worth it.” Every team I’ve ever worked on has had one of these guys—and they are always men—half-ass, self-taught dabblers, bush league, un-professional. Guys who steadfastly refuse to learn anything new after they made it into the field. Later, after all the talk about school, it turns out his degree is in economics; he couldn’t even be bothered not to half-ass it while he was literally paying people to teach him this stuff. The sheer nerve of someone who couldn’t even be bothered to learn what he needed to know to get a degree to speak for the rest of us.
I’ve been baffled by the emergence of GPT-powered coding assistants—why would someone want a tool that hallucinates possible-but-untested solutions? That are usually wrong? And that by defintion you don’t know how to check? And I finally understand, it turns out it’s the economists that decided to go be shitty programmers instead. Who uses GPT? People who’ve been looking for shortcuts their whole life, and found a new one. Got it.
And look, I know—I know— this is bothering me way more than it should. But this attitude—learning new things is too hard, why should I care about the basics—is endemic in this industry. And that’s the job. Thats why we got into this in the first place. Instead, we’re getting dragged into a an industry-wide moral hazard because Xcode’s big ass Play Button is too confusing?
I’ll tell you what this sharpened up, though. I have a new lead-off question for technical interviews: “Tell me the last thing you learned.”
looonnng exhale
Look! More links!
Defective Accelerationism a concise and very funny summary of what a loser Sam Altman is; I cannot for the life of me remember where I saw the link to this?
Tech Billionaires Need to Stop Trying to Make the Science Fiction They Grew Up on Real | Scientific American; over in SciAm, Charlie Stross writes a cleaned up version of his talk I linked to back in You call it the “AI Nexus”, we call it the “Torment Pin”.
Ted Chiang: Fears of Technology Are Fears of Capitalism
Finally, we have an amusing dustup over in the open source world: Michael Tsai - Blog - GitHub Code Search Now Requires Logging In.
The change github made is fine, but the open source dorks are acting like github declared war on civilization itself. Click through to the github issue if you want to watch the most self-important un-self-aware dinguses ruin their own position, by basically freaking out that someone giving them something for free might have conditions. WHICH IS PRETTY RICH coming from the folks that INVENTED “free with conditions.” I accidentally spent half an hour reading it muttering “this is why we always lose” under my breath.