IMO every datetime should be in utc, and variables for datetimes should either be suffixed “Utc” or have a type indicating their time zone (DateTimeOffset or UtcDateTime etc). Conversion to local time happens at the last possible second (e.g. in the view model or an outbound http request parameter). Of course that doesn’t solve the problem of interoperating with other morons programmers who don’t follow these rules, but it keeps things a lot neater locally.
Scheduling based on regional time conventions (holidays, weekends, etc) is just not great though.
It makes a HUGE difference in compile time. Which only matters if you’re building your own kernel anyway. It’s a solution for its own problem.
I think it’s a good learning experience though. There is genuinely a lot of stuff in there that you can easily, safely remove, and reading up on all the less obvious flags is fun.
That has nothing to do with file transfer (“updating”), just long term storage. It’s also a solved problem. You can solve it at the software level with modern self-healing filesystems.
I agree for drinking at home, but for travel, get a ceramic-lined double-walled steel cup like a Fellow Carter or a Stanley Ceramivac. (I use the Carter and love it.)
I hate adware and nagware, but I respect it here. From the get-go you know this is a space where this person gets paid. This is just an extension of that.