• 8 Posts
  • 222 Comments
Joined 2 years ago
cake
Cake day: July 8th, 2023

help-circle


  • Continuing gaming’s long tradition of dumb names for game genres, boomer shooters are first person shooters that don’t use auto-regen health (COD, Halo), in offline they give health frequently from killing enemies (rather exclusively health packs), and they’re designed to be fast paced, usually with a wide FOV, an absurdly high “walk” speed with no run button, and somewhat disorienting or labyrinth-like map style. They’re often offline, but can be multiplayer player-vs-player.

    Even if the game is completely modern: Doom Eternal, Ultrakill, Dusk, Turbo Overkill, etc its still called a boomer shooter.




  • I disagree. Yes there can be good intermediate steps, but deleting slop is not even half as healthy as locking a phone away.

    1. Interruptions

    Not just phone calls or texts, but things like typing an email on the phone and then seeing a text or having the GPS interrupt your train of thought by yelling “Continue straight for 5 miles”. Brains hate interruptions. Those are still going to exist even when the slop is gone.

    1. Resisting a temptation is exhausting. “not eating candy is healthy”… yes but having a candy bowl right next to your desk is exhausting. It takes 2sec to open a twitter link in the browser. Uninstalling an app is like moving the candy bowl to a nearby room, yeah its better, but it only takes 30 sec to reinstall.

    Turning off the dopamine machine (not eating candy) is one thing. But Eddy was showing something a lot bigger than that; deleting his access to the temptation. He didnt know the code to unlock the phone.










  • Don’t Speculate

    Go to Twitch/YouTube. Watch a senior Vim/Jetbrains/Emacs/VS Code/Helix dev churn out code for a hackathon/advent-of-code, and see what you are (or are not!) missing out on.

    If you have “how the hell did they just do that” moments, figure out what that feature is, and STEAL IT. If its too hard to steal, then maybe you are being limited by your editor. Base your “fear of missing out” on what you see rather than random people tossing their opinions around. Only you can answer “how much is that feature worth to me and my workflows?”

    • If you’re going to try modal editors, sooner is exponentially better. Probably start with Vim bindings for VS Code.
    • If you’re not going to go modal, then make absolutely sure you don’t bottom out. To be frank, Ctrl+D is the tip of the iceberg. Half the benefit of modal editors is, mastery is mandatory; they chase you around with a 10k volt taser until you’ve got 100 instinctual shortcuts. Hardly anyone mentions this but Go beyond/outside your editor: At the OS level, use spacebar as a modifier key, where holding spacebar converts your WASD into arrow keys. Then disable your normal arrow keys. Something like that will get you vim-like benefits, but in every app, and with a learning bump instead of a learning mountain. For VS Code, get cursor jumper extensions like Mario (block jumper), get cursor-alignment extensions, write boatloads of custom code snippets, get a macro record+replay extension, make a jump-to-next quote, jump to next bracket, install sequential number generator extension, a case change (camel case, snake case, etc) extension, sort lines, case-preserving rename. If you can avoid bottoming out, and keep learning, you’ll likely never feel that you are missing out on whatever modal editor people are swearing by.






  • Its a tough problem. You have to find something that you want to exist; like an app or a website or a game. For example, try making a GUI for managing SSH keys. You know, like the ones github makes you create in order to clone and push to a repo. Make a visual representation of those keys (stored in the .ssh folder), and tools to add/delete them.

    Along the way you’ll find tons of missing things, tools that should exist but don’t. Those are the “real” projects that will really expand your capabilities as a developer.

    For example, I was coding in python and wanted to make a function that caches the output because the code was inherently slow.

    • but to cache an output we need to know the inputs are the same
    • hashes are good for this but lists can’t be hashed with the built-in python hash function
    • we can make our own hash, but hashing a list that contains itself is hard
    • there is a solution for lists, but then hashing a set that contains itself is a serious problem (MUCH harder than hashing a list)
    • turns out hashing a set is the same problem as the graph-coloring problem (graph isomorphism)
    • suddenly I have a really deep understanding of recursive data structures all because I wanted to a function that caches its output.