You forgot to include the yearly $400 for Adobe so that they can create PDF's of said screenshots and Word documents so people with other versions or missing fonts can also see the Outlook e-mail.

Why would you need MS Office to communicate with others. That's what we have e-mail and phones and a number of other tools for. Using a Word document to communicate something generally gets ignored. Also, most people have evolved to be able to use more than just MSOffice, they can use LibreOffice, Google Docs etc. If your HR drones fail to recognize the technological process since 2000, their performance needs reviewing.

Pick one, make sure your systems run against it. If you always use NTP sourced data, you cannot assume your GPS sourced data (or local nuclear clock data) will give you the same results.

You can never assume that time will not change due to external factors. That could be due to a sysadmin executing the 'ntpdate' command, leap years, leap seconds or even daylight savings.

You're talking mainly about human representations of time though and although the conversion should be handled delicately, they should not be used for internal time representations (a major mistake I see very often is to handle/parse hh:mm:ss strings back and forth between a model and a controller).

The testcase however is one that does need handling though if you do require such reliance on time. It may not be simple but yes, it is possible to fake the clock (ntpdsim). External (live/production) data within a test environment is likewise a 'bad thing', you most likely will not handle outliers if you assume the current external data includes improper data.

Most, if not all of them. Unix time is leap second-ignorant and there are a number of other time sources that likewise handle leap seconds. If you do for some reason, require solar seconds or GPS time, there are other solutions for that. Most likely though, it's your platform that needs to handle the leap seconds and Linux, Mac, BSD, Solaris is more than capable of that, don't know about Windows or other esoteric systems though.

The issue is in human date/time representations and/or bad programming. I've seen many times programmers parsing a MM-DD-YYYY HH:mm:ss string rather than a proper timestamp. I've also seen programmers implement timers even in lower-level languages like C by simply subtracting "$current time" - "$past time" or having a timestamp with a "unique" requirement. If you've ever worked on platforms that do not keep accurate track of time or have no hardware clock such as embedded devices, virtual servers etc, then you know that it's a bad idea.

If you're relying on mm:ss to progress 'properly' during these time events, then you're in trouble. The article gives the example of timers as well which just gives me the heebie-jeebies.

Slow news day? Software dependent on accurate timing should be able to handle such exceptions such as leap seconds, leap years etc. It is a simple test case and is well documented. So if your software fails, you have a bug in your software, which shows you either didn't test or you're simply incompetent.

Also, most if not all languages have libraries that can handle accurate timing very well.

Exactly, it has been rumored that VeriSign actively cooperates with MITM attacks.

VPS has the same problem as shared hosting amongst the majority, especially the 'cheap' VPS. Shared hosting == VPS and Shared Hosting is way more resource-friendly to the hosting company.

A good VPS is nicer to have than a shared host because you're (generally) not locked to a specific operating system or software stack but if you're just doing static or simple PHP content you may be better off with a good shared host than a similar cost VPS.

1998 may be a "convenient" mile post but it doesn't reflect reality. There was a lot of large scale development going on in C++ in the early & mid-90's. By your measurement, C++ is younger than Java!

Does your OS actually do TRIM or is it merely reporting that it supports TRIM? Or does it require a binary to execute TRIM? I've noticed, most devices are simply ignoring TRIM commands. Also, do you actually continuously verify that your data is written and stored correctly? Unless you have ZFS or BTRFS, you most likely are accumulating errors across your data.

I wouldn't say that. There are plenty of stories about random SSD corruption across all platforms. Some platforms (Windows/Mac) simply do not execute TRIM unless the device is whitelisted or a proprietary piece of binary is running on the computer.

TRIM is a kludge at best, a hack to get better performance out of shitty drives. Get a decent SSD and you won't need TRIM.

I learned C++ in 1987. The original Stroustrup book came out in 1985, so more like 30 years old.

Bluetooth works pretty well, never had a problem with it. I have 2 controllers, keyboard and a mouse, no latency issues ever. If you're working on a console, latency doesn't matter anyway. You won't get much over 30fps anyway which gives the controller a decent 30ms to respond.

The NSA doesn't have to hide anything, they'll just ask the providers and they'll provide it to them.