I sometimes name booleans after the action that will be taken rather than the condition they represent For example, I might have booleans called “doQuickInit” or “invertResult”. I find this very useful when the value of a boolean is determined by a complex series of conditions that are not actually true or false.
It’s only a matter of time before it’s not an option anymore. Every shitty new behavior they put in is an easy-to-use option at first, then a registry setting or policy, then even that goes away and it gets baked in.
Embedded software developer here.
Oh damn, I thought I was going to be the only one here!
I don’t know how you get by with only one. Between source code, simulators/emulators, datasheets, requirement specs, log files, e-mails from senior devs with tribal knowledge not written down anywhere else, and a bunch of other bullshit, I sometimes find 3 24" monitors to be lacking.
Distractions aren’t a problem because I can easily use up all that screen real estate for a single task.
Jank was the style at the time.
If you don’t mind old shitty graphics and mechanics, start with the original Deus Ex. I played it when it first came out and it blew my little stupid mind. I still replay it once every couple of years. It really taught me what an art video games can be, which was totally new to me after growing up on Wolfenstein and Doom.
I’ve heard BL described as a “looter shooter”, but found that I can mostly ignore the loot aspect. Like OP, I’m not a fan of grinding for special drops, managing a shitload of inventory items, or memorizing loot stats. I just play through the games, occasionally checking drops for something better than what I have, and moving right along. It never felt like a burden to me because I didn’t care about having the “best” gear.
If you’re into FPS games, here are a few suggestions that have RPG elements:
PS2 is retro now? Damn, getting old really does sneak up on you.