I'm very curious to know if you had an obituary written up for Princess Diana already, or did you only have them written up for celebrities that were "at risk"?
Was there any kind of cutoff in terms of age? Were there obituaries maintained for child actors and singers? So many questions but it's a very interesting topic!
But AWS alternatives ARE just a smattering of open source stuff.
Getting everything into AWS doesn't solve anything by itself, either. Then they'd still need to get everything off of windows, office, exchange, AD, etc. etc. Which is a ridiculous amount of work and they'd be fighting bugs and issues for years and years at their scale.
To be fair, that alone doesn't account for it, since 90m only ~25% of the total population, so it's still skewed. Probably attributable to density and cost of living etc though.
Florida/Washington/California are more hospitable to surviving while homeless. New York has New York City, which has a law requiring it to provide shelter from the elements for all homeless.
Not much of a surprise that there are more homeless where a person is more likely to survive winters and summers without shelter.
My experience is that it's night and day... in favor of Microsoft. Caveat is that I'm on the data side, but AWS is a hodge podge of open source projects that they "integrated" (poorly). There's issues with data type mismatches between glue catalog and Athena/Presto, you can throw your data into Redshift but that's behind its own security curtain in postgres. You can move your data via glue, emr, MWAA, etc. but they all feel bolted on and integration is always more painful than it needs to be.
Microsoft, meanwhile, is moving towards synapse and fabric which is just everything you need in one spot, (more) easily integrated. I'm not saying it's perfect, but the vast, majority of companies I've worked with don't have the expertise or desire to put together some bespoke architecture taking into consideration the 5 options they have every single step along the way. They want something they can use out of the box.
Automated license plate readers, in this case. Or the legality of police purchase of private ALPR data, to hurt the economic incentive of private surveillance. Or the ease with which individuals and license plates are linked in the first place - remember, while we're quick to give up and say we can't do anything about private ALPRs, they're just gathering publicly available data, license plates themselves are government-mandated. I'm sure there are ways to improve their privacy, while still permitting identification for hit&runs. Like gratis switching of plates, and closely guarded access to the license plate database, akin to library records.
There are many possibilities. Carving out narrow exceptions for a handful of uses favored by the ACLU, thereby stealing momentum from any larger anti-surveillance movements, is possibly the worst of them.
ACLU has been fighting ALPR implementations for over a decade, now.
If you want to them to fight a case that will impact all ALPR, they will need to be given a case that can set such a precedent, and it will likely rely on legislation that does not currently exist.
> If you want to them to fight a case that will impact all ALPR, they will need to be given a case that can set such a precedent, and it will likely rely on legislation that does not currently exist.
As the current top comment states [1], this is such a case, and the legislation already exists! Yet instead of demanding cops merely follow existing law, they're making a narrower demand tailored to cover just their preferred activity.
I have to be very careful how far I scroll down when reading threads. If I scroll a little beyond the last reply, I get a "See what's happening" full splash screen. Extremely frustrating when you have these X/? Posts and have no idea when the actual end is without checking for existence of the next.
If you're able to take Paternity, take it. It's going to be a whirlwind, especially if this is your first child, and this is likely the first real stretch of time you've had off in your entire adult life. It's hard to bond with a week-old child, but spend as much time as you can with the baby and make yourself available to help mom with anything she might want help with.
The good news is that the baby sleeps... a lot. You can only fill up so much time doing laundry, cleaning bottles, and doing dishes. You will have some free time, especially at the start. Use some of this time dusting off your resume and learning some things that interest you that you haven't had the chance to dig into previously. You should be free from the typical day-to-day work stresses so, if you're like me, this might actually be enjoyable. If you're already confident you dislike your job, maybe even try to get an interview or two scheduled during this time.
Once you're back to work you can evaluate with a clear head just how much you (dis)like your current job, and you should have a clearer idea of how close to the chopping block you truly are. Some employers have a knack for making you feel worthless even if you're incredibly valuable.
Make sure you're prioritizing your family; it's a lot easier to find another job. This is an very exciting time- enjoy it!
The baby will sleep a lot.. in two hour chunks with crying in between. That said, yes the beginning part isn't actually that many hours you're really doing anything for the baby and you'll (hopefully) be stuck at home, so it is a good time to apply for jobs and do interviews. Good luck and congrats!
> The good news is that the baby sleeps... a lot. You can only fill up so much time doing laundry, cleaning bottles, and doing dishes. You will have some free time, especially at the start.
I guess your child is very different to mine or you are very different to me, but for at least the first two weeks there's really not enough time for everything, certainly not to get enough sleep. Doing some side work as well seems incomprehensible to me.
>"I just moved to this place and I'm getting local robocalls to my cell number"
This is more than likely just a combination of National Change of Address database (which is updated daily, I think, and there seems to be a lot of companies selling it) and some marketing information from one of many services that sell it, almost all of which contain your cell phone.
> AWS feels like 700 two pizza teams designing a cloud all in their own black boxes.
Couldn't agree with this point more, and it's enough to make me prefer Azure. AWS is taking open source tooling and slapping a very thin veneer on top to make it their own. Almost nothing is cohesive or easily integrated. You can ask the same question to three AWS solution architects and get three similar-but-different stacks suggested.
Azure seems to be going the way of solid, simplified, integrations between their tooling (things like Synapse), while AWS is trying to be first to market (or fastest, or cheapest) with all of these individual components.
Yes, the number of comparable & overlapping offerings in AWS is very confusing to someone not fully immersed in it for years and years.
There isn't exactly clear comparison matrices or design trees on why you would use one service over the other. It really just feels like 100s of different services that were built for different specific end users and then slowly grown into overlapping offerings.
It's worse in big corporate, and especially financial settings as only certain flavors of certain services will get the cyber/infosec blessing. Then you have vendor products you want to use in AWS which only support certain flavors of those same service types as well.
So we end up having to bang heads against walls to actually get internal cyber&external vendor onto same page. If the product touches several service types (containers/storage/database/etc) then you have to make sure they can all be strung together in an approved compatible fashion.
In the old days a vendor could say they support x86 Linux, and you knew you'd more likely than not be able to install their software. Now you have to go many layers deeper than "we support AWS" to understand if its actually going to work or not, sometimes with multi-week POCs.
I have experience with Google Cloud and AWS is overwhelming for me: it is like going to a buffet with 80 varieties of crab rangoons or something - it was really tough to make a choice. I was just trying to enable alerts on a container-hosted service and it took me quite a bit to get there and even then the result is not very nice. Probably my inexperience though.
Was there any kind of cutoff in terms of age? Were there obituaries maintained for child actors and singers? So many questions but it's a very interesting topic!