I'm sure you are capable of switching careers and skillsets more successfully than I was, but for me, metaphorically speaking, after peering over the hedge, I came to be content with the color of the grass on my own side.
A good lens might be to view those positions as senior first, and technology second, even if you don't necessarily voice that perspective in the cover letter / interview.
Was the vertex compression responsible for the wobbling/swimming effect you'd see on models, when running Q1 and Q2 in OpenGL mode?
You can also look to some guided courses that may help if you just need some direction. Odin Project is a good one and free. Colt Steele has a good one (my nephew worked through it and liked it) on Udemy called the "Web Developer Bootcamp". Don't pay full price though for that one, clear your browser cache, go into incognito mode, etc and you should see it discounted to like $20... if a sale isn't already running.
I can't emphasize enough... learn HTML, CSS, and JavaScript deeply. They are the foundation before things like React, Angular, etc. Don't fall for the "get rich quick" promise of frameworks. Nothing makes a senior developer more insane than when you come in as a "React whiz" but don't understand the fundamentals at all.
And finally... BUILD BUILD BUILD. Build and abandon a thousand projects. See something on a website or in an app you like? Try to recreate it. Learn to pull it apart and see how it works.
If you have never done anything like this, your going to hit rough patches. The pain you feel is "learning". I'm the lead dev on my team and they act like I'm some genius. Truth is, I'm a slow learner but I'm not afraid of being uncomfortable and experimenting all the time. Best of luck!
To a lesser extent, even being able to modify pretty much any game mechanic via the pull-down Console was amazing too. A great entryway to programming for the young enthusiast!
Always was a wonderful advantage to owning a PC over a console. That, and the accompanying utilities you could combine with the game, to create new graphics, sounds etc.
The code is clear, coherent, and straightforward. I’m not going to say it’s the best source code I’ve ever read, but it set a high bar. I’ve read source code to games since then, and I’ve seen all sorts of weird stuff… I’ve seen functions with nesting levels that go past the right side of the screen, I’ve seen functions a mile long that do a million things, you know. It was an early lesson that you could do cool things with simple code.
We used Quake and Quake II to teach a VR class to kids in the late 1990s and early 2000s. You got a VR headset, you got a half-dozen PCs with Q.E.D. or Qoole, and you taught a room of 12-14 or 14-18 year-old students how to make their own virtual reality game.
“Make your own virtual reality game” was, essentially, making your own Quake or Quake II level, without any monsters or guns in it. The story for the game could be told through on-screen messages triggered in the level. Students made all sorts of levels. One group made a level with slime you had to cross, and a button that turned on pumps to drain the slime (very much like what you would see in a standard Quake II level). Another group made a 3D maze out of water that you had to swim through, floating in space. I still have some of these student-made levels on my hard drive, after all these years, although I have trouble getting some of them to work.
For the class, I made a mod that gave the players a flaregun instead of the blaster. Basically, it was still the blaster, but with a different sound effect and no weapon model. I modified the blaster bolt to be affected by gravity, bounce off of things, and go out after a certain amount of time.
(If you were in that class—you may not have gotten the headset. We couldn’t always get it to work.)
This, of course, makes perfect sense as an output from an industry leader in the field (Carmack). However it definitely requires a lot of foreknowledge and, dare I say it, a mathematical bent to follow with confidence.
Also as a more passive job-seeking strategy, you could leverage your professional network of past co-workers to let you know if any opportunities come up (always had a lot of success with this personally). That way you can dip your toes into the job pool without having to switch focus completely.