Squiddlioni

It’s me, I do it. But only when I need something to do to stay awake in hour five of today’s meetings to address the “quick turnaround” patch that I finished coding three weeks ago, but now they want a label to change and no one on the six teams that have somehow become involved seems to know who owns the package that the field the label represents belongs to, but they’re absolutely certain we need to programmatically retrieve the text in case the package owner changes it at some point, and someone remembers that the original developer wrote code to get the label text 16 years ago, but it was removed from the program two years before the project started using source control, and they have an old installer around here somewhere that we can decompile or trace with Wireshark to get the right RPC name (sharing their screen while they have a rummage for it, natch), and someone else volunteers that they might know how to get a version of the server application from around that time since the client and server versions have to match, but it’s technically the intellectual property of a different subcontractor who was just a guy in Alaska who passed away five years ago, but they’re sure they can convince his estate to burn it to a disk and mail it to me if they can just find the contact information…

Almost 20 years ago I convinced my high school library to let me install Debian on one of the computer groups. I found the “eject” command, and wrote a script that just invoked it with an argument to close the tray. I named that script “inject”. Being high schoolers, my friends and I made scripts to “eject” and “inject”, along with various beeps, and named the scripts suggestive and tawdry things. We all had a good giggle setting the systems off on their little routines and walking away.

Or, in the modern nomenclature, “systemd and friends”

Even proper TED talks can have some big issues. I’m thinking specifically about Kary Mullis getting up on stage and saying anthropogenic climate change isn’t real because he found a study that says there’s a current that fluctuates and absorbs anything we do–or something to that effect. If you didn’t know anything about Kary Mullis and just heard “Nobel prize winner” you might assume he’s credible. In actuality he was a pariah for talking out his ass about things he doesn’t have expertise in and doesn’t understand, specifically his climate and HIV/AIDS denialism.

It’s always a good idea to approach any lecture with a critical view, but I can see why TED talks might warrant extra scrutiny. They project expertise and authority which may or may not actually be credible. The organization has a mottled record of vetting their speakers for actual expertise. (ETA: actual expertise in the content of their talk. Obviously Kary Mullis had actual expertise, just not in the things he said on stage)

Maybe “credentialed” wasn’t the right word. I was thinking of software licenses and access to third party tools and systems. Probably not as big a mess in game dev as it is in government.

It’s called Brook’s Law. It takes a lot of time and effort getting people up to speed, and that takes experienced devs away from coding. You also have to get them credentialed, teach them the tools, need extra code reviews/testing/bugfixes while they learn the quirks and pitfalls of the code base, etc. In the long term you’ll be able to get more done, but it comes at the cost of short term agility.