I thought it had to be a joke article from the title. Yeesh wouldn’t want to be the person who gets the fallout from this idea.

Not if the place doesn’t do daylight savings time, and not all places in a timezone will do that (least in North America) so you need extra code if they do or do not. It becomes a pain after awhile when you do it in multiple projects. Technically one extra setting but it’s still a pain to make sure it’s handle properly in all cases, especially when the previous programmer decided to handle it for each case individually, but that’s a different issue.

Also when you deal with the times, say in .Net you gotta make sure it’s the proper kind of date otherwise it decides it’s a local system date and will change it to system local when run. Sure it’s all handled but there are many easy mistakes to make when working with time.

I probably didn’t even get to the real reason, I sort of picked this up on my own.

The problem with stuff like flow charts is that when you do a new feature that changes the chart then there’s another chunk of time to update that document. If you’re really interested in that all you can really do is make your own as you go through software and you’ll see usual patterns how different code areas interact. it’s not as useful as figuring it out on your own or studying design paradigms.

True, they should have better campaigns to showcase those repairs, also manufacture support for it. Unless they do and I missed it, which is very possible. Just seems they don’t want you to change batteries since they make it a hassle.

Yeah but that seems like a pain, of course I had a cell back to analog days and am probably is. Used to sell so many batteries for cells in my Radio Shack days, and many were people wanting a second one for a backup when they were in the bush. Even remember $80 for a lithium startac battery heh, like 20ish years ago.