DeborahEmeni_

4 ms·

1.
by DeborahEmeni_ 8mo ago
I’ve been experimenting with this recently. Running services inside microVMs instead of plain containers makes the threat model easier to reason about, especially for multi-tenant or untrusted workloads. I’ve been trying it out on Northflan
2.
Quick question for platform engineers or DevOps engineers
1 points by DeborahEmeni_ 1y ago|2 comments
3.
What's the most misleading 'minimum spec' you've seen in software?
2 points by DeborahEmeni_ 1y ago|0 comments
4.
Getting tired of Helm – any better way to handle deployments in Kubernetes?
25 points by DeborahEmeni_ 1y ago|23 comments
5.
Kubernetes Day 2 ops: what's working for you?
1 points by DeborahEmeni_ 1y ago|0 comments
6.
Has anyone found a non-chaotic way to do CI/CD with Kubernetes?
2 points by DeborahEmeni_ 1y ago|1 comments
7.
by DeborahEmeni_ 1y ago
makes sense tbh. i’ve seen teams take that approach and only think about cost once it’s already a problem. ever had that come back to cause issues later?
8.
by DeborahEmeni_ 1y ago
yeah exactly. feels like the pricing model alone keeps a lot of folks from even starting. one wrong config and you’re done before you ship anything.
9.
by DeborahEmeni_ 1y ago
yeah that’s the part that gets me too. feels wild that there’s no built-in way to cap spend at the account level. even a “pause all” button would go a long way
10.
by DeborahEmeni_ 1y ago
agreed. old reddit actually works. no extra stuff and doesn’t get in the way
11.
by DeborahEmeni_ 1y ago
yep that’s the one. rough situation but the replies were interesting
12.
by DeborahEmeni_ 1y ago
yeah cost anomaly detector is underrated. do you usually set custom thresholds or just let it use the defaults?
13.
by DeborahEmeni_ 1y ago
yep this is the one. feels like a lot of people just copy-paste from stackoverflow without realizing they're hardcoding keys. have you seen this cause issues in prod or mostly in hobby stuff?
14.
by DeborahEmeni_ 1y ago
yeah makes sense. the idea that success = risk now is kind of wild. did you end up doing anything to limit that egress, or just ride it out?
15.
by DeborahEmeni_ 1y ago
appreciate the context. do you know if the platform itself didn’t meet dev needs, or was it more about rollout and team buy-in?
16.
by DeborahEmeni_ 1y ago
thanks for sharing this. really interesting seeing the jupyterhub setup combined with devcontainers. curious how usage went long term. did people keep using it without needing much hand-holding, or was it more of a “power users only” kind o
17.
by DeborahEmeni_ 1y ago
got it, that makes sense. i was trying to keep things centralized at first but splitting per cluster might be the better call. did you end up automating anything around managing those separate instances or mostly manual?
18.
Anyone here built an internal dev platform that people used?
3 points by DeborahEmeni_ 1y ago|4 comments
19.
Anyone scaling ArgoCD across multiple clusters?
4 points by DeborahEmeni_ 1y ago|2 comments
20.
Why do small teams keep getting wrecked by AWS bills?
8 points by DeborahEmeni_ 1y ago|17 comments
21.
Why do small teams keep getting wrecked by AWS bills?
2 points by DeborahEmeni_ 1y ago|0 comments
22.
by DeborahEmeni_ 1y ago
The “holding a button” thing actually resonated. It feels like the real work here is engineering the reward structure to make exploration even remotely viable. Dreamer’s world model might be cool, but most of the heavy lifting still seems t
23.
by DeborahEmeni_ 1y ago
I’ve done something similar using OpenRouter and fallback chains across providers. It’s super helpful when you’re hitting rate limits or need different models for different payload sizes. I would love to see more people share latency data,
24.
by DeborahEmeni_ 1y ago
Really cool setup! Curious how much of the performance here could vary depending on whether the model runs in a hosted environment vs local. Would love to see benchmarks that also track how cloud-based eval platforms (with potential rate li
25.
by DeborahEmeni_ 1y ago
Apple's shift away from GPL has been showing for years, so this doesn't surprise me. But dropping rsync 2.6.9 this late without full 3.x support feels like a step backwards, especially for anyone relying on metadata preservation.