I use Claude Code and one of the steps in my workflow is do a review loop until no issues are found and it never loops. So my experience is entirely different. Even if I say: fix all issues. So not only the critical issues.
I think the Google Go style guide is really nice and pragmatic. There are some references to the GoTips for some advanced subjects. I hope they release it someday.
Although the handhelds have been backwards compatible, only the Wii and the Wii U had backwards compatibility. The SNES, N64, Gamecube and Switch did not have backwards compatibility.
Although NativeAOT sounds cool and it's better than nothing: I don't like that it comes with a bunch of limitations[1]. I would have loved this if you could just use it without any changes, but I'm very worried that at some point I used something that prevents me from getting it to work and I have to figure out which limitation I just walked into. Correct me if I'm wrong.
Saying "tech is bad" or "screens are bad" sound very narrow-minded to me. Sure, there are issues in this "Tech-Saturated World" but I don't think avoiding Tech as much as possible is the answer.
I prefer a digital balance over digital minimalism.
I discovered the Adrian's basement channel recently. It's amazing! Been watching repair videos that are over an hour. Somehow he can keep me interested. I like how he explains things and his enthusiasm is very contagious. "It freakin' works!"