it does feel ambiguous though as even what you outlined misses a 4th case. if null means delete, how do I update it to set the field to null?

it’s not about using all 100 IP addresses for every atom

it’s about having large enough ranges to allocate them in ways that make sense instead of arbitrarily allocating them by availability

the question then becomes how much weight are you adding/energy are you consuming by having to carry the weight. I honestly don’t know and considering how heavy batteries are it is likely not that significant, but if you are only getting a few % charge a day then anything eating into that is going to hurt.

I still see some merit in a more utility style vehicle where you do expect to take it out camping, but for a daily commuter I think most people would prefer the sunroof to the trickle charging.

Also as an apartment dweller… I just wish they’d make normal wall outlets more available. Not everyone needs a proper fast charger but only having a few inconveniently located ones to fight for also sucks. But if more spots could just plug in and slow charge that would be a huge improvement

not OP but I’d love something like this for a few reasons.

Sometimes I’m debugging really complicated things and it gets hard to keep track of the info I’ve captured and what I’ve learned, and sometimes you want to recheck some earlier assumption or you learn something new and want to look through older data captured to see if it aligns with newer understandings

Or it’s a long standing thing and need to step away and come back and refresh your memory of the current understanding. And especially when others might also be working on the same problem and you want to collaborate better.

Though I am SRE and thinking of debugging issues in overall systems spanning multiple codebases, hosts, and networks. not just specific bugs in a single codebase like I think OP is doing. So I’m also curious if any tool would actually fit both use cases or if being perfect for one would make it not useful for the other.

the other reply covered the actual ranges and why it’s important, but in case it’s not obvious:

You should never put hot food in the fridge. Particularly food with a lot of thermal mass like a bowl of soup or thick lasagna. While that would cool the food quicker than just leaving it out, the heat you’re adding is going to heat up the other items in your fridge and risk their safety. And since it will all eventually cool back down it will not be obvious what food was at unsafe temps or how long.

the biggest downside imo is it can be hard to leave because you’ll feel more connected to everyone involved. but they won’t necessarily be able to pay you much more than you start at even if you do stay. and you’ll be spending that time on more or less the same tech stack which can limit your growth and make it harder when finding a new job later.

id say it’s fine especially as an early job but strongly consider a new job after 2-4 years