One reason to consider is around context usage with LLMs. Less is generally better and README.md files are often too much text some of which I don’t want in every context window.
I find AGENT.md and similar functioning files for LLMs in my projects contains concise and specific commands around feedback loops such as testing, build commands, etc. Yes these same commands might be in a README.md but often there is a lot more text that I don’t want in the context window being sent with every turn to the LLM.
Yes, trucks typically are running with the generator constantly on scene. Also many pumps are run on a PTO system where the transmission is put into a pump gear, further wearing on it since pumps can be run a lot on scene.
These numbers for trucks paired with the 3+ year wait times are very real. It hits small communities the hard because they have a small tax base but still need a certain amount of trucks. You can only consolidate so much before you are to far to respond.
Another good point called out in the article are the floating costs. The manufactures do in fact increase the costs after the fact so not only do you need to order a truck years ahead of time with a budget you don’t have (borrow money) but then you have to cough up an indeterminate amount of money years later. A real sad time for first responders.
There very well may be something more effective than water but the economics are probably a barrier here. Water has some pretty amazing at absorbing heat considering how abundant it is. Moving to anything else becomes pricey quickly in a serious quanitiy. Heck, even the foam used is quite expensive in much smaller quantities.
It's also worth keeping in mind that rural fire departments that all have tanker trucks typically carry only 1,500-3,000 gallons and need to continuously fill up from a pump site, drive to the scene, dump in a pond, and continue. Typical gasoline car fires will take less than 1,000 to extinguish. EVs are challenging from this perspective, and departments are just now starting to learn how to deal with them, it's a whole new ballgame.
This was a good read, as someone using K8s a lot in the last two years but not service meshes yet, it gave me a lot to think about.
I understand there are various advantages like metrics, etc, but the encrypted traffic between pods and services is the one that I can see many orgs demanding. If not a service mesh what other options are there?
Might seem like and odd one to some but I became a volunteer firefighter and it has been very rewarding for many reasons but the connection with the community is a big one (most members grew up in the town and a central part of it).
The chart titled “Impact of unrealized securities losses on capital ratios” really shows just how inadequate the tier 1 capital ratio is (what regulators use). Ignoring the impact of unrealized losses in assets marked as held to maturity is crazy. Seems like a regulator problem to me, no bank taking deposits should be able to make high duration and negatively convex (from high MBS holdings) without hedges.
I like the goal of reducing dependency on SaaS product. I use these Strava/Garmin apps a lot and while Strava was cool for a while it hasn’t progressed and doesn’t feel worth the money. Curious to hear what you had in mind, I am in the geospatial space and work with routing tools, etc.
I don’t have a feature list off the top of my head. The basics that Strava offers would be a good start: show your GPS tracks on a map, allow sharing with friends, a chronological feed of your friends’ rides.
I find AGENT.md and similar functioning files for LLMs in my projects contains concise and specific commands around feedback loops such as testing, build commands, etc. Yes these same commands might be in a README.md but often there is a lot more text that I don’t want in the context window being sent with every turn to the LLM.