I’m impressed they managed to make an app that makes me not want to use it or my phone to take photos! After I used it for about 5 mins I resolved to dust off my older DSLR and use it instead.
Readit Newsstlava commented on It's the end of observability as we know it (and I feel fine) honeycomb.io/blog/its-the... · Posted by u/gpi
I feel that if you need an LLM to help pivot between existing data it just means the operability tool has gaps in user functionality. This is by far my biggest gripe with DataDog today. All the data is there but going from database query to front end traces should be easy but is not.
Sure we can use an LLM but I can for now click around faster (if those breadcrumbs exist) than it can reason.
Also the LLM would only point to a direction and I’m still going to have to use the UI to confirm.
stlava commented on Home Battery versus Generator pv-magazine-usa.com/2025/... · Posted by u/gnabgib
We've discussed getting backup power periodically since moving (most of our neighbors have something). After the big bomb cyclone that hit the NPW this became a priority and I did a very similar tradeoff matrix.
Here were some of my consideration points against a generator (I had a list for batteries too):
1. the previous owners electrified the house so having a tank just for a generator didn't make sense
2. per 1, a small tank wouldn't last very long and if we're out of power for multiple days gas delivery is unlikely to be happening anyway.
3. tank + generator didn't have a practical placement location for us
4. smaller portable generators didn't make sense from a maintenance perspective since they didn't auto test.
5. what happens if it fails a self test right before a storm?
6. we get intermittent power cuts / fluctuations / outages throughout the year and the generator + ATS wouldn't protect sensitive electronics well
Edit: ATS + batteries can play nice together then I might look at doing a small portable as aux backup
stlava commented on WASM will replace containers creston.blog/wasm-will-re... · Posted by u/hpincket
> In the year 2030, no one will remember Kubernetes.
I highly doubt that. Maybe there will be an evolution to k8s but fundamentally it solves a whole host of challenges around defining the environment an application runs in.
Nice! I'm one of the authors of pg-bifrost which is in the same space. Have you thought about / have solved sharding consumption across multiple slots / multi consumers to increase throughput? This is on my radar but not something I've investigated yet.
The issue we've ran into is some team at work decides to re-write an entire table and things get backed up until they stop updating rows.
stlava commented on Error handling in Go web apps shouldn't be so awkward boldlygo.tech/posts/2024-... · Posted by u/todsacerdoti
Sounds like the author is missing an interface to abstract the DB backend.
stlava commented on Ways to shoot yourself in the foot with Redis philbooth.me/blog/four-wa... · Posted by u/philbo
My team manages a handful of clusters at work and I wrote on an internal redis client proxy (it's on my todo list to opensource). A few things I tell other teams to set them up for success (we use Elasticache):
- Connection pooling / pipelining and circuit breaking is a must at scale. The clients are a lot better than they used to be but it's important developers understand the behavior of the client library they are using. Someone suggested using Envoy as sidecar proxy, I personally wouldn't after our experience with it with redis but it's an easy option. - Avoid changing the cluster topology if the CPU load is over 40%. This is primarily in case of unplanned failures during a change. - If something goes wrong shed load application side as quick as possible because Redis won't recover if it's being hammered. You'll need to either have feature flags of be able to scale down your application. - Having replicas won't protect you from data loss so don't treat it as a source of truth. Also, don't rely on consistency in clustered mode. - Remember Redis is single threaded so an 8xl isn't going to be super useful with all those unused cores.
Things we have alarms on by default: - Engine utilization - Anomalies in replication lag - Network throughput (relative to throughput of the underlying EC2 instance) - Bytes used for cache - Swap usage (this is the oh shit alarm)
Right, so basically taxi cabs but personalized ads. GG on marginally progressing the wheel.
Sure we can segment this into code generation models and code review models but are engineers really going to want to be questioned by a code review tool on "what are you trying to do?" or are they just going to merge and pull the slot lever again?