Every job will have some sort of crunch time. Even just staying in a programming position, the definition of “crunch time” will vary wildly. I’m lucky enough that “crunch time” just means that I set aside all my other tasks until I fix whatever is on fire, but I still get to go home on time unless I really want the overtime pay.
I don’t envy positions with forced 80-hour workweek crunch times. That’s a sign of bad management.
Because I am addicted to solving puzzles.
Looks like this may be a known issue for some users.
Bluey.
It wasn’t that hard if you kept feeding it quarters. It took a lot of trial and error, but having infinite lives means it was eventually beatable.
A couple dozen devices maybe. I don’t really need dedicated ranges, but it’s nice to know exactly which device I’m looking at just by the IP when reading logs.
I know they exist and vaguely what they do, but I don’t know how to set them up. What’s their advantage over simple DHCP reservations for a small client list?
I like the range for new devices- hadn’t thought of that!
The chat history is the big one for me. It’s not even that it’s not persistent; I’d be fine if it just purged all messages after a set period. The problem is that it seems to selectively purge some messages but keep others. Makes me feel like I’m crazy when I go back and try to find something that I know I sent a while ago, but there’s just a gap.