great article, but the clickbait title is clearly intended to be misleading

even for visual programs, I absolutely despise the 10min videos for something that I only really care about 5 seconds of. If visual programs had the option of decent text tutorials (with screenshots) it’d be much easier to get into

is figuring out this sort of stuff an exercise of trying to reverse engineer the product, or is it much simpler than I make it out to be? whenever I want to try and fix something all the videos I see people just magically know which places shouldn’t be shorting, and magically know which capacitor is causing it

Most of the time there’s a cap after which there are diminishing returns. A $700 phone will probably last you a good 3-4 years, compared to a shitty year or two with a $300 one. However, a $1500 phone isn’t gonna be that much better and won’t last that much longer to be worth it.

this example seems to use Cherry style keycaps, but that direction should take you to a choc set that works

probably the keycaps that people use for steno should do what you’re looking for. Idk specifically what keycaps any of them use, but take a look at the Uni (https://stenokeyboards.com) and see if you can figure out which keycaps they use - those should play nice with your idea

For some other people this might differ, but whenever I have to interact with them, the Apple docs are absurdly bad. They read more as an autogenerated list from the API than something an actual human wrote trying to be useful. In general I agree, for most languages/packages the official docs are great