Just thinking what a useful command line utility `z` is - I use it all the time. (`z foo` navigates to a frequently accessed directory that best matches "foo").
Just thinking what a useful command line utility `z` is - I use it all the time. (`z foo` navigates to a frequently accessed directory that best matches "foo").
New Year’s Eve: Musings on Y2K
At 3pm PST on 31 December, 1999, I sat down at the computer in my home office in Yakima, Washington. I logged remotely into the network at HQ and started monitoring our systems. The most critical moment would come at 4pm local time. We were in Pacific Standard Time (PST), -0800 UTC. In other words, at 4pm in Yakima, it would be midnight in Greenwich, England, where the time zone aligns with Coordinated Universal Time. (Coordinated Universal Time is abbreviated as UTC, not CUT, because there are actually other languages in the world besides English, and… never mind. Look it up if that story interests you).
Anyway.
The GPS satellites run on UTC, and our entire multi-state operation depended on GPS timing. My first hint of system failure because of a Y2K bug would occur at midnight, UTC.
Beginning at 3:55pm I began testing the major system once a minute. At 4:05pm I sent out the notice to corporate management that all was well.
I tested hourly, then, but the next critical moment wasn’t until 9pm PST, which was when midnight occurred on the US East Coast. Our equipment was all in MST and PST, but some of our many telecom providers might have systems with local time coordination in some other US time zone. (They’d all be using GPS now, but – this was 1999, and US telecommunications had plenty of legacy systems with other clocking methods).
In the end, nothing failed. Our entire system worked.
This wasn’t because Y2K was overblown.
It was because we replaced our billing system, which wasn’t able to generate an invoice after the date flip.
It was because we did software updates on several proprietary systems that would have failed.
It was because we did firmware updates, too.
Equipment inventories.
Application inventories.
Operating system inventories.
Software version inventories.
Firmware version inventories.
The reason January 1, 2000 seemed like such an ordinary day is because of the MASSIVE amount of work and money spent to make it ordinary. There are unsung heroes around the world who put in the work to update or replace systems that would’ve failed otherwise.
If you’re one of those people, I would love to hear your story.
‘Insulate Britain’ activists trial delayed after heating problems left the courtroom too cold to proceed…
How much of people's reluctance to support climate policies† is due a background perception that the wealthiest have a free pass to pollute with private jets, mega yachts, helicopters, etc?
https://petition.parliament.uk/petitions/641289
†This isn't to say all climate policies are unpopular, but some essential policies are less wildly popular than would be ideal.
1 in 10 flights from UK airports are private jet flights, but loopholes (0% VAT and 0 Air Passenger Duty on larger private aircraft) mean they pay almost no tax. It does not make sense for these flights to be zero-rated for VAT, and some to pay no APD, as they are not essential items.
This is the least that a country taking emissions seriously and tackling them fairly would do:
Tax private jet flights fairly and phase out kerosene private jets
https://petition.parliament.uk/petitions/641289
1 in 10 flights from UK airports are private jet flights, but they pay almost no tax.
1 in 10 flights from UK airports are private jet flights, but loopholes (0% VAT and 0 Air Passenger Duty on larger private aircraft) mean they pay almost no tax. It does not make sense for these flights to be zero-rated for VAT, and some to pay no APD, as they are not essential items.