KO
March 19, 2026
programminggamingguide

You're Already a Programmer, You Just Don't Know It Yet

Every gamer already thinks like a developer. You edit configs, write macros, and min-max spreadsheets. Here's why that means you're closer to coding than you think.

KO
KernelOutlaw@KernelOutlaw

Every gamer I know has done at least one of these:

  • Edited a config file to squeeze out more FPS

  • Written a macro or keybind script

  • Modded a game and broken it spectacularly

  • Spent three hours tweaking OBS settings instead of actually streaming

  • Built a spreadsheet to min-max stats in an RPG


  • Congrats. You're already thinking like a programmer. You just haven't written the code yet.

    The Overlap Nobody Talks About



    Gaming and programming use the same part of your brain. I'm not being motivational poster about it. I mean it literally.

    In any intense match, you're reading the state of the game, making decisions based on incomplete information, executing precise inputs under time pressure, and adapting when something goes wrong. That's a gameplay loop, but it's also what debugging feels like.

    You see a problem. You form a theory. You test it. It doesn't work. You try something else. You iterate until it clicks. Then you push to the next problem.

    If that sounds like your Tuesday night in Valorant, welcome to software development.

    Where to Actually Start



    I'm not going to tell you to go watch a 47-hour beginner Python course on YouTube. That's how you learn to hate programming.

    Start with something you care about:

    You mod games? Learn Lua. Half the modding communities on earth run on it. Roblox, Garry's Mod, World of Warcraft addons. All Lua.

    You want to build a Discord bot? JavaScript or Python. Pick one. You can have a working bot in an afternoon that does something dumb in your server, and that dopamine hit of "I built this" is real.

    You want to understand how your computer actually works? Rust or C. This is the deep end, but if you're the type who already tweaks BIOS settings and overclocks for fun, you'll love it. Rust is what I use. It's hard, it's satisfying, and it doesn't let you write garbage code without telling you exactly why it's garbage.

    You just want to make a website? HTML, CSS, JavaScript. Three files. Open a text editor. You can have something on screen in ten minutes. This site started the same way.

    The Real Reason



    Here's what nobody in the "learn to code" crowd will tell you. It's not about getting a job. It can be. Devs get paid well and the job market albeit rough right now for engineers isn't going anywhere despite what Twitter doomers say. Tech is currently going through a transformation and nobody knows what it looks like. The market will recover, as is all things in life, time heals all.

    But the real reason is independence.

    Right now, if you want a custom overlay for your stream, you pay someone or use a template. If you want a website, you use Squarespace. If you want a Discord bot that does exactly what you want, you hope someone already made it.

    When you can code, you just... build the thing. You stop waiting for someone else to make the tool you need. That's the unlock. That's the kernel-level access to your own life.

    Don't Overthink It



    You don't need a computer science degree. You don't need to pass a whiteboard interview. You don't even need to be good at math. I barely passed precalc and I write Rust for fun.

    Just pick something small, something you actually want to build, and start breaking stuff. That's how every programmer who's any good got started.

    And if you get stuck, drop into the Discord. There's a whole channel for code stuff. No judgment, no gatekeeping. We figure it out together.

    let you = gamer();
    let next = you.learn("code");