Wading through the Technobabble

So last night, as I was trying to fall asleep, my mind awoke and began presenting me with ideas for the project I’m currently working on. Despite my decided preference for sleep, I finally gave up and went to my desk to get some thoughts down in code.


That’s when I ran into a roadblock. I’m using VSCode to create a web app. And the extension that allows you to see your changes instantly had decided, without my approval, not to work. Instead of showing my site, it through up an error I’d never seen before. Instead of letting the creativity flow, I had to stop and try to figure out how to fix the problem.
In these situations, I always jump immediately into a google search. Errors and problems like this are rarely unique. But, in this case, the suggested answers were in a language I don’t speak well: gibberish.

I’m not bad at deciphering technobabble, but this was over my head. None of it made sense to me. The error code, as is usually the base, offered little direction, referring to components and actions I don’t comprehend. After struggling to make sense of it, I finally gave up, left a bug report in a hopefully appropriate Github location, and went back to bed.

This morning, I went through the rather drastic steps of uninstalling and reinstalling VSCode. That didn’t solve the problem. I had to google “completely uninstall VSCode” to figure out how to get VSCode entirely off my system. I followed the steps provided by Google, reinstalled, and now everything works as it should. I still have no idea what I might have done to cause the problem, which means I’ll have a hard time avoiding it in the future.

This type of frustration is quite common, especially for people like me who are learning it as I go along. But the key is to solve the problem and move forward — any way you can.

P.S. Just to irritate me, my keyboard suddenly began lagging this afternoon. Apparently Microsoft decided I need to have the “Filter Keys” setting turned on. I only figured that out after an hour of searching Google for answers. Suck it hard, Microsoft.

Author: Michael W. Bay

Michael is a geek. He likes smart science-fiction, good coffee, playing the bass guitar, making up songs in the shower, cats and dogs and a nice, long Stephen King novel.