CS enrollment is declining, but not demand. Everyone is citing the numbers from UC Berkeley showing a 26% percent decline in enrollment. What they fail to mention is that the CS department reduced their admit slots by 25% because the TAs negotiated an $80/hr rate, and they can't afford as many, so they can't open as many classes.
But the number of students applying for CS is actually up slightly.
I've seen all the Space Shuttles in their retirement. It took me 10 years to get to them all.
But I saw Endeavor when it was still just on the ground (like Discovery). I can't wait to go back and (re)complete my collection!
Interestingly, with this display, you can now see the shuttle in all operating modes:
Endeavor is in launch configuration, Atlantis is in orbit configuration, and Discovery is in landing configuration. And if you count Independence at JSC, you can see it in transport configuration.
More cardiac issues than the other vaccine options but far less than the virus. If it were the only option it would still be on the market. It was only pulled because better options showed up.
Ok if you want to be pedantic, the standard says, "if you can't read this file, go to the offset and then execute the code you find" which isn't functionally different from what I said.
Sure, but when the standard says "read this file and execute the instructions you find at the beginning" that is more dangerous than "this is a file with data and your program needs to figure out how to read it".
Another thing making a comeback -- reference checks. I had to supply references for my first job in 1999. Then I wasn't asked for them again until 2024, and then for every job after that.
Hah, you did the one at 12 also? I too remember both, and it was also 30 years ago. I don't know why, probably because they were really important numbers to teenagers, and they say you remember things that happened to you as a teen more than any other part of your life.
I edited my comment to make it clearer. I meant you should only directly store current timestamps, anything else you should leave up to a library to store as it sees fit.
I edited my comment to make it clearer. I meant you should only directly store current timestamps, anything else you should leave up to a library to store as it sees fit.
I would contend that you shouldn't store anything but current unix timestamps in UTC in your database. If you must store time in some other way, then the two column method in the post will work, but leave it up to your software library to do it.
I prefer to leave all the time conversions to software, wherein you only use battle tested libraries, and never do it by hand.
Timezones are just too fraught with peril to try and do it on your own.
Edit: changed some words to make clearer what I was saying.
I've dealt with this before. The problem with doing a billing cap is that now you are bringing an out-of-band batch system (billing) in-band. The only way to do a dollar cap is to constantly calculate your bill.
Capping it at 100K requests is a lot easier, because it's a single number that can be incremented easily in a distributed way.
It's the same reason it took AWS forever to offer billing caps, and even today, they label it as best effort. They don't guarantee you won't pay more than your set limit.