> Annual number of prescribed burn acres had been stable since the 70s with a sharp increase in the last two-three years.
The number of burns isn’t as important as much as how much ground is covered by burns and where. Has anyone studied it in greater detail?
> The main issues are sprawl and aging, above the ground electrical infra
I am not sure what sprawl matters, but I agree electrical infrastructure that is surrounded by fuel or can be affected by winds is problematic. But that still comes down to local and state leadership doing their job. It’s incredible that such large budgets and large numbers of public employees fail to produce outcomes that are any better than other states.
In practice, using async insert with wait means you need batching/retries implemented on the client side or else you may find you have thousands of threads stuck in wait. If you need to replay bc you messed something up you're also SOL. I generally appreciate not having to run kafka but that comes at a cost.
Same here except Motorola circa 2007. The build took hours and compiler was licensed from Windriver. We had to schedule time to do builds and test runs using some Rational pos software and we had a dedicated eng in charge of doing merges on release branch
Operators that just render a config are a waste of resources. Operators that manage state of other operators (e.g Deployment) or external resources (e.g Crossplane) are a really convenient, developer-friendly way of solving infra automation challenges.
reply