• 3 Posts
  • 107 Comments
Joined 1 year ago
cake
Cake day: October 12th, 2023

help-circle


  • I carry a spare usb stick and some low-capacity microsd cards, because sometimes its just easier to hand someone a file the old fashioned way.

    Sometimes I do play games on my phone, but whenever possible I use a usb or bluetooth gamepad, because touchscreens aren’t supplanting buttons any time soon.

    And of course the Steam Deck is my favorite gizmo, not just because it can run every PC and emulator game, but also because it doesn’t have any bullshit preventing me from installing mods. If phone modding was easy and accessible i’d be willing to spend more on a phone.







  • When dating people, I often ask “name a book that’s not Harry Potter”. Doesn’t even have to be one you’ve read. Pick any book at all (other than Harry Potter) and tell me why you thought of it.

    I’m not gatekeeping people who do or don’t read books, and i don’t care if it’s sci fi, fantasy, fanfic, nonfic, whatever. what i do care about is that you are aware of at least one book and care enough to remember what it’s about. That’s a low bar, but not as low as you might think.

    The “no Harry Potter” clause isn’t specifically due to jkr being a terf (although that too), but because it’s such an overused answer. Yeah, I do remember the books that were so popular that they had their own brand of jelly beans. I have run out of things to say about them. Pick literally anything else.


  • depending on your budget, consider the MNT Reform, a notebook computer designed to be as repairable as you can possibly imagine. Every plastic part is 3d-printable, every circuitboard is open source, and it uses off-the-shelf parts for its keyboard, batteries, and screen. really its only downsides are the entry price (around $1600) and the fact that it relies on a relatively low-power SOC (system on chip) for CPU, GPU, and RAM.

    disclaimer: I don’t have one myself (yet) but I’m keeping an eye on them because it looks like an incredible hobby computer




  • Good callout! I agree, don’t rewrite just for the sake of rewriting. By “barely works” I am referring to code that functions but where a small change to the requirements would make it incorrect. In that situation you should “break it” in order to add changes, rather than calcifying the legacy code by building around it.


  • I’ve worked in programming for the last ten years and the most important skill you might not have guessed: Bravery. People are going to say “if it works, don’t fix it”, but a lot of real-world code barely works, and you need to be willing to break it to make it better.

    If you’re good at your job, you will spend a lot of time reading other people’s code and testing small changes to see what happens. Write “new” code for yourself, because it’s fun and its good practice, but also learn to read and repair “old” code.