@valigo I really like the work Kirill Pokrovsky and Borislav Slavov have done for the Larian titles.
Other than that: Morrowind, Outer Wilds, Ori and the Blind Forest.
@nicbarkeragain Does programming count if I do it for free?
Otherwise, second would be bouldering, and I used to play piano and do photography, but they've been living on the sidelines for a long time.
@valigo I cried every time I was a contractor on a three.js project. It is very good for prototyping, but clients have a way of declaring prototypes production ready. To fix missing features and performance issues, we almost always ended up with a locally modified version.
@nicbarkeragain Yeah, you almost want to teach people the array that should have been, perhaps leaning on some of the newer C alternatives for explanation, and then go back to the array that exists in C and teach people how to avoid its footguns.
@valigo Resonates with me. I started my career in the Java world, using IDEs. Over the years, I trained my thinking such that now I use a plain editor with syntax highlighting and grep.
Knowing both worlds, I appreciate how much simpler the same program is, if your tools are sharp.
@wookash_podcast Don't know how far you've listened, but it gets better. And yes, I've shivered and cried listening to this.
And then there is Azazoth Blues.
@valigo And yeah... my strong preference is for greppable cosebases. Might be my age, but overcomplicated type metaprogramming doesn't excite me anymore. Instead I want code to read like prose.
@valigo Can tell from personal experience that if you stick to diet typescript, it is also very greppable. Unfortunately almost nobody writes it that way :(
@valigo@balaganovitch We had a C-style 100kloc Rust codebase where I just grepped around. My colleauges did use lsps, though. Rust can be written in a simple way, but it is unfortunately not the cultural standard.
@valigo Not sure if the AI interpretted the instructions well, though.
Also, Rust projects tend to be overcomplicated slop, because people can't help themselves, but you *can* write handmade-style Rust.
@valigo Had a look with the expectation to hate this, but at least the translation guide is better than I aas expecting. For instance, not using std::io, tokio, async and other overcomplicated parts of Rust should make the code more C-like and easier to understand by humans.
@wookash_podcast Also, the reviews took me painstakingly long and I didn't enjoy the process at all. I'd much rather be making stuff than making sure others didn't break things.
@wookash_podcast People told me I had "laser eyes" when reviewing. I spotted both architectural problems and tiny mistakes in their PRs. But that was codebase I knew really well. I don't think I could do that in an unfamiliar codebase, because it requires a model of the thing.
@SandorHQ@wookash_podcast This. I've listened to him a lot on stream. He is often moody and generally not everyone's cup of tea, but I've never seen him do the bad things people accuse him of.
(The design and programming knowledge I learned from him during those years has been invaluable to me)