502 karma · joined April 11, 2018
I am the person everyone calls when things hit the fan, when disagreements need to be settled, when unfixable things need to be fixed, when something needs to be figured out. Do I feel qualified, never, no. I don't feel I'd last one day at say Facebook, no chance, I don't have skills to fit into a team, to play nice, the patience needed to grind the political structures. I like my dark corner.
Is it this bad across the industry? Its way worse, there are more people in the industry than ever, finding someone that actually knows something is impossible.
Build a book of people over 5–10 year period and never, ever letting go of them, keeping those relationships alive.
If any of this is true why is it so surprising that wpe was cut off?
> WP Engine wants to control your WordPress experience, they need to run their own user login system, update servers, plugin directory, theme directory, pattern directory, block directory, translations, photo directory, job board, meetups, conferences, bug tracker, forums, Slack, Ping-o-matic, and showcase. Their servers can no longer access our servers for free. The reason WordPress sites don’t get hacked as much anymore is we work with hosts to block vulnerabilities at the network layer, WP Engine will need to replicate that security research on their own. Why should WordPress.org provide these services to WP Engine for free, given their attacks on us?
So much drama.
Microsoft can easily drop a fork of windows, slam out all of the com crap, leave .net core and include some IIS, but why, you already have someone doing it in Linux.
The reality is that we shouldn't be making the transformation in written data, now you have staging tables, procs, views, resulting tables procs, views, a staging database (often called staging or etl), and an unhappy DBA who yells at you every time you cross-apply incorrectly.
ETL should be done before the data lands in SQL.
Why? We are pretty deep into the ecosystem.
Abstraction -> the only thing data factory does not allow you is to reference a previous activity as a variable, which makes sense if you don't want to let your customer blow up your product. Parametrize all you want.
Unit testing -> test all you want each activity, pipeline, flow, resume it from where it broke. Clone the entire thing into a test data factory, then deploy that once ready.
CI/CD -> the first step it nags you about is setting up CI/CD. If you want to get fancy, you setup a dev environment and deploy that to production after testing and sign-off.
Abstracting ETL only works when you remember or have the same people on staff that abstracted that ETL process. Data factory 'could' be visual but does not let you pull the same level of non-sense that SSIS would.
For example, we call data factory via API, the pipeline is fully abstracted, it does one thing, but it's inputs and outputs are controlled by the request.
There are major improvements in taking a curve and not scaring the shit out of the driver, much faster basic turn right on stop sign, lane changes when it does it, it’s hard to describe just how smooth they are it’s a little nuts the car just floats over it’s not human, but it really should not have changed lane most of the time… so decision logic is shit. Etc.
Driving with FSD on empty roads is very enjoyable and whenever it decides to do something you can recover/correct with no stress.
Driving in poor conditions with FSD feels safer, it sees better than me in the dark and rain for sure.
Driving with fsd in heavy traffic about the same as driving a car yourself, this where I usually drop back to AP.
Is driving my tesla easier or harder than another vehicle? It’s much much easier than driving my ICE suv. But from a pure FSD perspective, if the car didn’t have AP I believe my opinion would not be the same.
The only time fsd works ‘ok’, single lane roads with 90 degree stop signs / turns.
I don’t believe that the current hardware can handle what is needed to have passable FSD for an average consumer.
You have to steal the private key for the SAML signing certificate for an app. The correct answer would be to scope any token to only have access to what the app has access to, the second layer which is documented in their 2020 article, is to require mfa on admin actions, and the 3rd layer is to disconnect azure admin accounts from on-prem admin accounts preventing this type of attack.
But disabling SSO altogether is non-starter for most businesses, what are we going to do tomorrow? Spend months recreating 100,000x accounts in various applications, no.
We decrypt ssl traffic in our company, someone steals the private key and now can read the entire stream including your bank account details, lets stop decrypting ssl traffic because someone might leak the key? The answer from the infosec communinity has been its worth the risk.
Autowipers do not work. Cannot work, will never work. My tesla can't see a full downed tree in my lane, gets spooked by dips in the road and pops collision alerts, how the hell would it see rain.
There are plenty of tasks that become impossible when using the wrong tools. It's like trying to move a lot of sand with a fork.
Apple releases M4 and tsmc rips it off tomorrow. All done on the their (americas) dime because we outsourced the means of production.
As far as this… you got morons quitting their jobs over crap like omg the oil industry is using our cloud. Meanwhile the biggest death machine on the planet e.g. the US government literally has two private azure offerings fully services by Microsoft with dedicated staff, but that’s not sexy, I can’t quit over that and post it in my socials, because that would be unpatriotic. But Microsoft not being green enough for me to work there is a stand that I can brag about.
You should put that on a coffee mug and sell it. It would make a great gift to a bunch of people that I know.
You need fossil fuels to get off of fossil fuels, you need regulation, the entire planet working on this, etc. Making the process LESS efficient is not going to help at any point. Let's start blowing up the equipment used to dig coal out of the ground so we can go back to doing it by hand like in the early 1900s, and let's start unscrewing the bolts in the machines at the factories, let's all quit at CAT and never build another digger...
>It’s true that Microsoft is taking numerous steps to address the sustainability of its own operations. But for years, the company has also furnished fossil fuel giants with cloud computing services and specialized software tools powered by machine learning and AI in order to streamline and automate their operations.
Let's make the extraction of the life blood of all industry on the planet less efficient, less streamlined, less clean. And do let us all know how you plan to build the next Azure data center without using fossil fuels dug out of the ground and processed plastics.
We all do tech here right? It’s a simple infra stack to store settings for a device and report on them once in a while.
No one is sitting at home and doomscrolling their ecobee thermostat for temperature updates.
I expect the cloud infra needed to support the thermostat to be so cheap at this point that it’s completely irrelevant. I expect that ecobee spend more money on coffee than the infra needed. Fact is I bet that a free aws account can service a significant portion of the demand.
I can connect up to 100 wyze cams to my account and store footage and remotely access them for the huge sum of 7$/mo.
You are telling me thermostat configs are harder to handle? Bullshit.
This will be a shift for on-prem deployments. For cloud solutions running VMware in AWS/Azure, unless those renewals go up significantly, most of VMwares mrr is already locked in and the people running these setups generally refuse to learn how the cloud works so it’s a pure lift and shift mentality.
But the pattern begins, broadcom buys VMware does nothing increase prices. Why would any sane client stay around to get VC squeezed.
Or buy a 200-dollar device and walk up to a car in a hoody and steal it?