> But the culls are smaller, and so the impact lessened. The problem becomes more distributed.
Presumably the risk of spread of bird flu to humans increases though, due to the increased amount of contact. And then the increased risk of mutation leading to human to human transmission.
Bit wild to me that we don't seem to be taking this very seriously other than "o no my eggs" given we just had a pandemic a few years ago.
Arguably all the awful and crazy politics around COVID-19 has led directly to the scenario of people really not willing to take new pandemics seriously.
I think the way to think about H5N1 at the current time, for the hyper individualist types who don't care about no pandemic, is that it's like ebola. You really, really don't want to get it (~50% mortality) but you have to do quite specific things to put yourself at risk. One of those things is interacting with outdoor birds on a regular basis. Even in the absence of a pandemic it's just good sense not to expose yourself to that for the sake of questionably cheaper eggs.
There is also the question of whether the actions required to cut the waste are themselves expensive. If you spend a huge amount of time and effort to cut waste, there's a point at which it would have been cheaper to just accept that some waste is inevitable and to not worry about it.
Literally every organisation I've been in has had "waste", but most of them have been smart enough to realise that you don't want to spend thousands of person-hours measuring every tiny little thing and doing wildly complex RoI analyses (especially on stuff where it's almost impossible to figure out anyway because there are too many variables), and instead focus on having metrics around the outcomes that they do care about.
Heh I read Atlas Shrugged and had the exact same response as you reading Fountainhead. I recall quite enjoying the writing style, but just found the whole thing silly and the idea that anyone could come out of reading it thinking they'd just stumbled across a great life philosophy funny and depressing.
> it's impossible to bill at scale and exactly cut off service usage globally when a target is hit,
How much does the problem change if you remove the word 'exactly' from here, though?
Like, I don't mind if I end up paying a couple of extra bucks. Or even tens of bucks! Some people might not mind hundreds or thousands, or even more depending on their scale.
But blowing out several orders of magnitude past my usual monthly spend is the problem I'd like to avoid.
An old monolithic PHP application I worked on for over a decade wasn't set up with independent modules and the average deploy probably took a couple seconds, because it was an svn up which only updated changed files.
I frequently think about this when I watch my current workplace's node application go through a huge build process, spitting out a 70mb artifact which is then copied multiple times around the entire universe as a whole chonk before finally ending up where it needs to be several tens of minutes later.
Even watching how php applications get deployed these days, where it goes through this huge thing and takes about the same amount of time to replace all the docker containers.
I avoid Docker for precisely that reason! I have one system running on Docker across our whole org - Stirling-PDF providing some basic PDF services for internal use. Each time I update it I have to watch it download 700mb of Docker stuff, instead of just doing an in-place upgrade of a few files.
I get that there are advantages in shipping stuff like this. But having seen PHP stuff work for decades with in-place deploys and no build process I am just continually disappointed with how much worse the experience has become.
One approach I've seen rather successfully is to have a container that just contains the files to deploy, and another one for the runtime. You only need to update the runtime container ~ once a week or so (to get OS security updates), and the files container is literally just a COPY command to a volume.
I've only seen that in one place, ever. Most people just do the insane 40 minute docker build -- though I've also seen some that take over 4 hours...
Not sure what you mean about either of those two things? Never had any issues with instance state in our primary production environments, which were several instances of load balanced web servers. No idea what you're referring to as "slow"?
Do you mean wetness as in the juices in the steak gravitate to the bottom? Or do you mean literally the bottom of the steak is wet? Either way neither of those issues seem to be a problem for me.
When I first started cooking in the air fryer I did flip it at half way though. I just forgot once and found it didn't make any perceptible difference, so gave up on it and it's just that one less task to do. My partner and I both agree it comes out awesome pretty much every time, and I'd say we are reasonably fussy steak eaters.
I don't worry about crust I guess? I don't think I even try to do that when I'm cooking them in a pan. I'm more interested in trying to get the fat right - it tends to crust over pretty nicely in the air fryer. It works better on thicker bits so it has longer in the heat.
