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 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 recommend it when you don't want/need to have separate sources for account data and your metrics/aggregate data.
I’ve actually never been a fan of the “correct usage” that forgoes any spacing around it. I find it crowded and jarring.
I like to use a “thin space” around an em dash — it breaks it up without adding too much space.
I build most projects in Elixir/Phoenix these days, but wouldn't flinch at ROR if you are comfortable with it.
The road next to my house has a speed limit of 20mph but most cars go 45mph because it's a straight road 4 lanes but space for 6. No bumps, no curves, wide. Effectively it feels like you should be driving fast. If I go the speed limit in the center lane because I'm going to turn left people will get angry and speed around at 60mph pissed off
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.
... also continuing to not add features to my (not-much-of-a) system for getting more done each week. https://carpeweekem.com
I've also been cautiously adding AI-powered features to my Heroku autoscaling tool (https://flightformation.com/) and a simple free-text time/date input has been the most popular (demo: https://x.com/ejschmitt/status/1893268742760448497)
Log interesting things, where interesting is defined as context outside what the "happy path" execution performs.
Collect and make available system metrics, such as invocation counts, processing time histograms, etc., to make available what the post uses log statements to disseminate same.