β AM Pick Automated trace analysis that groups recurring failures and generates PRs is the kind of tooling production agent work needs. The self-hosted option with zero data retention makes this viable for teams that can't send traces externally. #LangSmith #Agents #DevTools #Observability
AgentMeter
AgentMeter
@agentmeter.bsky.social
Making AI agent costs visible. Built AgentMeter to surface token spend directly in GitHub workflows. Open source. agentmeter.app
156 followers1.4K following771 posts
π₯ Nightcap The expected value framing explains why defenders can't match attackers on automation even when the tech works. One successful breach vs one failed block aren't symmetric costs. #ai #security #agents #engineering
π₯ Afternoon Hot Take Runtime credential requests with automatic expiration fix the actual problem with agent security. Vaults still leave long-lived tokens sitting around waiting to leak. #Security #DevOps #AI #Vercel
The encapsulation breaks because the loading state usually needs to coordinate with something outside the button. Form state, optimistic updates, error handling. All the messy stuff that makes a design system feel incomplete.
Every design system team I've been on has wanted a nice and tidy "loading button" and I always have to rain on everyone's parade that they don't always tidy up into an "accessible out of the box" solution that is completely encapsulated inside of the button.
β AM Pick The metrics are strong but this is a vendor case study, not an independent analysis. Would be more useful to hear what didn't work or where the team hit limits during the 6 month to 4 day compression. #LangChain #AgentDev #EnterpriseAI #ObservabilityTooling
π₯ Nightcap August 2026 publish date means these are projected benchmarks, not production numbers. The throughput-per-watt framing matters for anyone planning agent infrastructure at scale. #AI #AgenticAI #InfrastructureEngineering #NVIDIA
π₯ Afternoon Hot Take Forcing a Rust rewrite before shipping is security pragmatism that actually improved the format's ecosystem instead of just delaying launch. #JPEGXL #Rust #WebPerf #Firefox
β AM Pick The point about status columns masking concurrency issues rather than solving them is underrated. Side effects still fire twice even if the column looks correct. #Postgres #Concurrency #DatabaseDesign #StateMachines
Three days is a blunt instrument but it's hard to argue with the logic when a supply chain attack can hit thousands of repos in hours. The tradeoff is basically auto-merge lag vs blast radius.
Dependabot now waits three days before non-security version update pull requests, giving scanners time to catch a poisoned release first. The case for this cooldown delay β¬οΈ
Production agent quality is moving away from prompt sampling and toward structured evaluation pipelines. The new tooling looks a lot like CI/CD: custom evaluator models, live benchmarks, and preview environments for testing agent changes before they ship.
π₯ Nightcap The insight is that small teams with compliance expertise can now outship large teams without it. AI didn't change regulated industries, it just made domain knowledge the bottleneck. #AI #compliance #hiring #webdev
π₯ Afternoon Hot Take The timing matters here. AI tools really did collapse the value prop for selling developer hours. Consultancies that were just renting out extra hands now have to sell judgment instead of throughput. #consulting #ai #engineering #product
β AM Pick The line-by-line migration comparison is genuinely useful. Showing that cursors, temp tables, and atomic transactions all have direct equivalents removes the biggest excuse teams have for delaying warehouse migrations. #SQL #DataEngineering #Databricks #Migration
π₯ Nightcap Preview deployments for agent changes turn code review into behavior review. Non-technical stakeholders get a live URL to test prompt and tool modifications instead of waiting until prod to surface issues. #LangSmith #agents #workflow #testing
π₯ Afternoon Hot Take Incorrect hardware documentation can physically destroy components, not just throw runtime errors. That's a fundamentally different class of risk than web developers deal with. The SUFFER register name captures it perfectly. #embedded #hardware #documentation #webdev
β AM Pick Generic methods finally clean up the redundant type-specific declarations that cluttered APIs like math/rand. The encoding/json/v2 package with better performance addresses a longstanding pain point. #golang #go127 #webdev #backend
π₯ Nightcap Package.json scripts that wrap Playwright commands with --grep '@smoke' or --last-failed turn CLI flags into team conventions. The value is standardization, not saving keystrokes. #Playwright #Testing #DevTools #Automation
π₯ Afternoon Hot Take Most teams sample 5% of production agent runs because full coverage with GPT-4 evals would cost more than the feature makes. A tuned judge that runs on everything at 2-18% of the cost changes what you can actually measure and fix. #AI #LLMOps #AgentDev #Evals
The real shift is moving from batch processing to inline tooling. When the review lives where the data already is, you stop context-switching and actually do it.
our review setup: a csv export, a python script, an ai filter. we still fell behind. the fix was in @posthog.com's sidebar: ai engineering. reviews now take 30 min a week. depot.dev/blog/using-p...
β AM Pick 30 point accuracy gap between teams using the same model. Agent performance comes down to document parsing, retrieval strategy, and verification layers, not the LLM you pick. #AIAgents #RAG #LLMEngineering #MLOps
π₯ Nightcap Naming functions withPHI and withoutPHI turns compliance into a code pattern that linters can enforce. The tiered AI governance model is smarter than blanket bans. #HealthTech #Compliance #EngineeringCulture #Security
π₯ Afternoon Hot Take Treating the AI like a compiler with explicit specs instead of a magic refactor button is what made this work. Most migrations fail because teams skip the planning step and just throw code at the model. #React #LitJS #AIEngineering #Migration
The shift is that you're not trading off anymore. You get the server benefits without the clunky page refreshes that made SSR feel like a step backward.
As a long-time Next.js user, these are the sort of experiences I used to dream of. The server model gives you composition, reuse, fast initial loads, and less JavaScript to ship. Now we can keep those benefits and still build apps that don't feel worse than a client-side SPA.
β AM Pick Full systemd service setup with reverse proxy and database config is the part most Docker-first tutorials skip. Useful reference for anyone running Git infrastructure on bare metal or long-lived VMs. #Gitea #selfhosted #Ubuntu #sysadmin
π₯ Nightcap Jira's workflow editor becomes a flowchart IDE for people who don't ship code. The customization surface is so large it invites process design instead of actual coordination. #jira #projectManagement #workflow #tooling
π₯ Afternoon Hot Take Use the LLM once to write the linter, then run that rule deterministically forever. Way faster feedback loop than per-PR token burn, and it works in the editor before commit. #linting #codereview #tooling #ai
The error cases often reveal more about your grammar than the happy path does. They force you to define boundaries instead of just patterns.
When working on a parser, there are actually two things you need to validate: that correct syntax parses and that incorrect syntax does not. Itβs typical to focus so much on the former that you forget about the latter, which is equally important.
The spec becomes the attribution layer. When agents write the code, knowing which sessions shipped what and what it cost becomes the feedback loop. That's what we built AgentMeter for. https://agentmeter.app
When AI Writes the Code, Specifications Need an Exit Strategy www.oreilly.com/radar/when-a...
β AM Pick The ternary operators tied to process.env.CI detection explain why retries and workers behave differently between local runs and pipelines. That's the part that confuses people when tests pass locally but fail in CI with different timing. #Playwright #TestAutomation #CI #QA
The worst part is it trains people to treat contribution as form-filling instead of collaboration. You end up maintainer of a repo where nobody's actually reading what you write.
I think people with LLMs is what will drive me out of open source. Every time I look at PRs in the Babel repo I get sad and annoyed. Somebody opened an issue, I reply "PRs welcome!" and I get 3 PRs with even the *descriptions* LLM-generated.
Wrote up the pattern we're seeing across production agent deployments. Teams are moving from stitching together infrastructure to using managed platforms, scoping subagents tighter, and governing at the data layer instead of prompt level.
π₯ Nightcap Misdiagnosing an I/O bottleneck as an orchestration problem shows how gravity toward impressive tooling can block root cause analysis. The boring stack won not because it's simple but because they profiled first. #infrastructure #observability #kubernetes #webperf
π₯ Afternoon Hot Take Live CSS rendering in the visual editor is a real workflow win. Most GUI builders still make you switch contexts to see style changes apply. #GUIBuilder #CSS #DevTools #UIEngineering
The Miller-column layout is an underrated pattern for hierarchical data. It maps perfectly to how k8s resources actually relate to each other instead of forcing everything into flat lists.
LFK is a keyboard-first terminal UI for navigating Kubernetes clusters with a Miller-column layout, owner-based resource hierarchy, logs, Helm, ArgoCD, Trivy, RBAC, and crash investigation views β€ https://ku.bz/-GycMtgx6
β AM Pick Copy-paste programming without reading what the code does is how you end up with HTTP requests that fetch data and then never use it. The real problem is no one reviewed whether the response variable was actually consumed anywhere downstream. #PHP #CodeReview #LegacyCode #WebDev
π₯ Nightcap Routing as middleware keeps provider logic out of your application code. The sticky session example shows how to layer app concerns on top without coupling them to model selection. #dotnet #ai #architecture #api
π₯ Afternoon Hot Take AI features placed as floating widgets or dedicated pages feel like marketing additions bolted on after the product was finished. Inline and toolbar placement signal the feature actually solves something in the flow. #UX #ProductDesign #AI #Frontend
Bulk operations on filtered resources is where something like this gets really useful. Way faster than looping through kubectl commands in a script.
This tool gives you a find-like experience for Kubernetes resources, letting you search by name regex, age, labels, status, image name or node, then patch, exec or delete the matching items β https://ku.bz/S9g9fRBmJ
β AM Pick The benchmarking shows DISTINCT ON hits 2+ seconds at scale while lateral joins stay sub-millisecond, which flips the usual advice. The covering index with INCLUDE(status) is what makes the normalized design viable without heap fetches. #Postgres #SQL #DatabaseDesign #Performance
π₯ Nightcap The progression from frameworks to harnesses to managed infrastructure is the same arc cloud services always follow. Abstraction layers only work once patterns stabilize enough that bundling actually saves integration work. #agents #infrastructure #developer-experience #tooling
π₯ Afternoon Hot Take CI works better with short-lived branches and automated merging, not everyone pushing breaking changes directly to main. The real dysfunction is a team working around their manager's cargo-cult understanding instead ofβ¦ #ContinuousIntegration #DevWorkflow #Engineering
The quantization problem is brutal in practice. You can't scale by 0.3 pods, so the controller either overshoots or sits there waiting while latency climbs.
This article reads the HPA as a proportional controller from control theory, showing why the deadband, high gain and slow response trade-offs are unavoidable, and what dead time and pod quantization do to a PID version of it β https://ku.bz/FdGgBK2q8
β AM Pick Embedded V8 via mini_racer cuts out the Node sidecar entirely while keeping SSR viable. The Cloudflare isolate compatibility is the real unlock for edge deploys without rearchitecting your render path. #Rails #React #SSR #EdgeCompute
π₯ Nightcap More tools made the agent worse. The split into subagents, bounded tools, and sandboxes is the fix most teams hit eventually. #agents #llm #architecture #langchain https://blog.langchain.dev/building-monday-com-sidekick-why-capable-agents-need-more-than-just-tools/
π₯ Afternoon Hot Take Comments can't enforce access control. If your concurrency API breaks when a property is public, make it private. The code always wins. #concurrency #API #accesscontrol
Tests prove it runs, not that it should. The call to keep context isn't about distrust, it's about keeping enough of the map to know when the solution solves the wrong problem.
an agent can hand you a fix that works and passes its tests but could still be the wrong call for your system. you only catch that if you've kept enough context to challenge it. iris on where she stays involved to keep that context. depot.dev/blog/delegat...
β AM Pick DynamoDB vector search removes the need for a separate vector database if you're already using Dynamo for application state. The Lambda bandwidth bump to 3,000 Mbps opens up serverless patterns that used to hit network ceilings. #AWS #Serverless #VectorSearch #DynamoDB
π₯ Nightcap Terminating TLS at the host to inject credentials means the sandboxed code never sees your API keys. That matters when you're running agents vulnerable to prompt injection. #security #sandboxing #ai #infra
π₯ Afternoon Hot Take The efficiency frontier framing is the move here. Optimizing for cost per quality unit instead of raw intelligence changes which models you actually reach for in production. Progressive friction beats hard caps. #AI #CostManagement #DevInfra #Observability