I always thought it was an interesting story, drove out there one day many years ago when I lived nearby. It was a dreary day, which added to the strangeness of the place.
It's an interesting place because it's not that far from other towns, and you can drive right through it on a normal, maintained road. If you turn off and drive just a minute or two it's very different though.
Otel stuff always seems overly complicated to me, but it must just be the types of projects I generally work with. Feels like observability meets java.
I've dabbled in building a project that collects metrics from the logs for smaller projects. Everyone tells me it's a bad idea, but it seems to work well for me.
I'm working on a tool to make tracking business metrics easy. [0]
I've always had issues collecting business metrics like "signups per day" in observability tools, but using marketing type tools comes with it's own set of problems.
I've been using TimescaleDB for a while as a metrics datastore. It's really proven to be great for aggregating data without a lot of hassle (using continuous aggregates, retention policies, etc).
I recommend it when you don't want/need to have separate sources for account data and your metrics/aggregate data.
I like using the em dash, but I try to limit it now—because chatgpt loves it even more.
Maybe it's for the better, some people seem to have strong opinions about it.
Yeah, unfortunately this is true. A street near my house has a limit of 40mph and people would regularly drive 60 mph+, sometimes someone would pass me doing 65+mph (it's a no-passing residential road).
Eventually someone died, and they added a lot of traffic-calming changes to the road. It's much nicer now, but a shame that someone had to die to change it.
I'm working on a solution for gathering product metrics and making sure applications keep running — when you don't want to install or maintain a lot of extra stuff. https://flexlogs.com
... also continuing to not add features to my (not-much-of-a) system for getting more done each week. https://carpeweekem.com
Glad I'm not the only one that feels this way. For a small application when you just want some metrics and observability, it's a big burden to get it all working.
On my own projects, I send the metrics I care about out through the logs and have another project I run collect and aggregate them from the logs. Probably “wrong” but it works and it's easy to set up.
I had a sacrificial fence (wood) on the aluminum fence to reduce blowout. I had the aluminum extend to near the blade to reduce the deflection of the whole thing. It was too close.
Really, I should have sacrificed a crosscut sled for dado usage, but it really chews them up.
Often times when a product has some patent-protected feature, the product itself is substandard, but I have not found that case with sawstop. It's one of my highest quality tools.
It would be nice if the mechanism wasn't so destructive. I accidentally had an aluminum fence just a fraction of a mm too close, and it touched the blade. I was using a dado stack, and it did a number on the carbide teeth of the blades. Good dado sets are not cheap, nor is the sawstop cartridge.
It's an interesting place because it's not that far from other towns, and you can drive right through it on a normal, maintained road. If you turn off and drive just a minute or two it's very different though.