trailrunner46

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.

Source: Firefighter in a rural dept

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).

100% agree, taking huge unhedged duration risk and then loading up on negatively convex MBS again unhedged is so crazy.

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.

Im not sure I agree with this. If you have a lot of extra taxable money just put it in a taxable investment account and keep some lowing amount in checking to handle bills. Keeping it all in checking and making the entire thing investments seems like an odd approach, the low interest you are getting in like <10k in your checking is not a big deal.

I can see how you came to wanting this but I think it could lead to dangers for many.

For most people (this is not financial advice for any one person) money in checking and savings should have a low rate of return and therefore low volatility because they need or may need that money to actually be there to pay bills or in times of crisis (emergency savings). Once you have these two pools of money, then you should invest in retirement and finally extra taxable investments. Most people should automate the money going into retirement and investments I agree but turning your entire checking account into a volatile/uninsured pool of money I think is the wrong direction.

There is a lot of skepticism around financial advisors and rightful so given the track record of many (picking insanely expensive funds, charging high fees themselves, etc.)

However, I do think there is a place for advisors not to pick investments but rather actually plan for life events (including tax stuff), which is right up the alley of this app). Having someone who could take all of your inputs, ask the right followup questions and appropriately model the likely range of outcomes on this kind of app could be quite attractive.

This is very slick and well executed. I especially appreciate the thought that went into data transfer (making it opt in, otherwise stays client side). I have a CFA and have been in finance for a while and have maintained a spreadsheet but honestly this does it better so I will use and support you. I wish more people would take a long view with their financial wellness, maybe I can convince a few friends to see the impact of their debt binges :)

On the UI side there are a few odd things like trying to paste a number that has decimal points makes it so nothing gets pasted in, the colors on some of the graphs are hard to read (especially for people with color vision deficiencies), etc. As I use it I will try to give more specific feedback. Can't wait to dig in further.

Python is certainly more popular and for job prospects I always tell that to newer data folks. That being said if you want to load in some data do some SQL like manipulation, run some stats and make a graph or output a report I would argue R is way better experience than Python but that’s much more about the package ecosystem and less a comment on the language. Dplyr is just more friendly to use than pandas (often 3-5 ways to do something and as a beginner this can be disorienting) and ggplot2 vs matlibplot. For interactive graphs you are probably going to use plotless anyway from both languages.

One other thing I would mention is knowing SQL well is the most translatable skill. A lot of dplyr and pandas are doing SQL like operations (in fact dbplyr will generate SQL equivalent commands for your dplyr code for various backends).

In summary know how to manipulate data in SQL then pick a language (because you will need to do some IO/reporting stuff outside just data work) where the ecosystem of packages feels user friendly to you and your work flow and roll with that.