Simon Let (@simonlet_) header
Simon Let (@simonlet_) profile picture

Product & Engineering @BetterStackHQ, the company with the best MCP server. Stop micromanaging your agents.

Prague
Joined October 2015
Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)Photo by Simon Let (@simonlet_)
Simon Let retweeted
opus 5.5 is incredible i know the models are gonna get better than this, but man, it really feels like it can do anything
117
77
16
2,607
83,189
"Agents aren't good at this thing I'm working on" Then why are you working on it?
42
4
2
139
19,385
Simon Let retweeted
I don't think writing a spec and splitting it into tickets is how you should use agents since Sol 5.6/Opus 5. Just tell the agent what you want to do and it will do it. If the task is large, discuss with the agent how to split it in several shippable PRs and do it one at a time.
mattpocock/skills v1.3 is out! - /pr (new) writes easy-to-read PR bodies, showing hard evidence that the changes work and assessing merge risk - /implement-spec (new) takes in a spec and tickets, and implements them with subagents - CONTEXT.md renamed to GLOSSARY.md - /retro (new) reviews recent coding agent sessions and suggests repo improvements /retro, especially, feels like a huge upgrade. Enjoy!
103
16
16
553
104,538
Simon Let retweeted
We unfortunately have decided that we cannot continue providing access to our models through Cursor and are ending our partnership. It boils down to trust and we’ve asked that this takes effect on November 12 to give you some time to plan. Many have used the GPT models through Cursor and here are options we know should work in the future: - We will continue to allow using your own OpenAI API key and similarly will continue to provide access through our IDE extensions for Cursor. - We will keep working with the broadest range of tools and harnesses, some of which are OSS, but also many many closed-source ones. We are as committed as ever to continue supporting developers and the flourishing ecosystem of tools, harnesses and products. We will also continue to invest in our own open-source initiatives and believe in broad optionality for developers. You can read more about our decision in the blog: openai.com/index/our-decisio…
We’re ending our partnership with Cursor following its acquisition by SpaceX. Under our proposal, Cursor’s direct access to our models would end on November 12. We know that the people most affected by this decision are the developers who rely on OpenAI models in Cursor. We care about their experience in this transition and we’re ready to go above and beyond to support them. openai.com/index/our-decisio…
1,443
592
472
9,947
4,306,740
I've started a new company: @superlogical! We're going to begin by building a terminal multiplexer. The entire vision is much larger, but the multiplexer is the foundation. Sign up for the newsletter to get beta access and devlogs (product updates only I promise). superlogical.com/
549
519
233
9,148
1,190,752
Simon Let retweeted
why does someone still uses @datadoghq in 2026 - there event based pricing is absolutely ridiculous. we got ~500$ bill for a month, where we recorded ~168 million of logs and it was just about 40gbish. I shifted our whole logging infra to @BetterStackHQ , took <1hr, our last month bill was ~45$. and betterstack mcp is such god tier, datadog mcp is also bad.
12
9
35
3,826
Simon Let retweeted
There's no full-window "Chat" mode in the new ChatGPT app for Mac. Don't upgrade.
1
2
5
512
🏗️ Reverse Engineering DirectX Turn an IDA Pro database into a functional project. We skip generic advice and show how to map decompiled DirectX structures to C++ classes. Learn to reverse a binary, &amp; create verifiable reconstruction.

12
399
3,462,094
Simon Let retweeted
The lovely folks at @JuicedataInc wrote a guide on monitoring JuiceFS with @BetterStackHQ
1
2
4
449
Under-discussed: how good agents are at debugging issues in production. Everybody's constantly talking about how well they write code, but give an agent access to the gcloud CLI and a screenshot of a graph and, good god, will it go.
48
8
9
350
48,106
Simon Let retweeted
We have moved from incident.io to @BetterStackHQ for our incident reporting! • status.scholarxiv.com The status page also reports more monitors; platform, API, AI-Chat, Sandboxes and Subscriptions with status history and chart. We've also made our health check API public for transparency! scholarxiv.com/api/health will respond with a comprehensive result! We've made this change to enable for more in-depth monitoring and incident reporting for our users and our on-call team!
1
4
23
892
Simon Let retweeted
Replying to @stevenssup
claude is so good i wouldnt call it vibe coding anymore
9
1
65
4,804
Simon Let retweeted
Today, we're introducing eBPF-based OpenTelemetry tracing alongside a remotely controlled Better Stack Collector. eBPF is ready for prime time. Here's the playbook for adopting it. What's eBPF? "extended Berkeley Packet Filter" is a Linux kernel technology that lets you run sandboxed programs inside the kernel safely and efficiently. Thanks to eBPF, you can now instrument your clusters with OpenTelemetry without changing any application code 🤯 The eBPF ecosystem has matured significantly over the past few months and many Better Stack customers are already using it in production. Until now, deploying eBPF to production has been tricky. We're simplifying it today by bundling the best of the open source eBPF sensors into a single remotely controlled Better Stack collector you can deploy with a single command. Better Stack collector gives you granular control over what exactly gets instrumented. Get the service map of your cluster, RED metrics for individual services, see network flows, and aggregate your application and system logs out of the box. Without changing any code. Observability tools are only useful if you actually ingest all relevant data. Today, we're making that simpler and more convenient than ever. The eBPF OpenTelemetry playbook™ = "Do the easy thing before doing the hard thing" 1. In your staging environment. 2. Deploy the eBPF collector into your distributed cluster. 3. In 98% of cases: Declare victory, your app is now instrumented. 4. In 2% of cases: You notice a particular service has slowed down. For example, the CPU utilization on a high-throughput Redis instance handling millions of operations per second got noticeably higher. Better be safe, so you disable eBPF for this single instance while keeping it enabled for the other 98% of services. 5. If needed, use the OpenTelemetry SDK auto-instrumentation to instrument the last 2% of applications. Most teams today still start with step 5. If you're revisiting your observability stack, I encourage you to give eBPF a chance: it has matured significantly and is better than you might expect. Better Stack encourages combining OpenTelemetry traces from the OTel SDK, eBPF, and your frontend. That's the only way to get the clearest picture of what's actually happening in your application. Want to chat eBPF? Catch me at KubeCon in Amsterdam next week!
5
14
5
52
39,874
Some evenings in Amsterdam are simply gezellig. On March 26 at 7:00 pm, we’re hosting a beer tasting at Café Struis, the official @BrouwerijtIJ tasting room. No pitches. No slides. Just award-winning beers brewed under the windmill. Join us! RSVP link in the thread below ↓
1
5
5
559
What do you do when you’re in Amsterdam? You get on a boat! March 24, 8:30 PM. We’re hosting a private canal cruise for the cloud native crowd. Cold beers. Dutch snacks. Zero agenda. Join the Better Stack crew for a night on the water! Link to RSVP below ↓
1
5
1
5
505
Simon Let retweeted
No need to decipher Unix timestamps, country codes or IPv4 addresses anymore. Agents are cool, but @BetterStackHQ makes your logs readable by humans too.
3
4
14
787
Simon Let retweeted
"You're with Better Stack, the YouTube channel?" "Yes! Sort of." I knew our YouTube channel was a success when I had to start explaining to people that @BetterStackHQ is more than just a media company. Today, we crossed 100k subscribers 🎉 Amazing job @RichOBray @JollyShopland @AGauracs72140 @The_JoshWenner 👏👏👏 LET'S GOOO 💪
4
3
4
29
1,949
Simon Let retweeted
Announcing Worktrunk! A git worktree manager, designed for running AI agents in parallel. A few points on why I'm so excited about the project, and why I hope it becomes broadly adopted 🧵
77
82
20
1,027
98,126
The people who don't feel this way are the ones who are fucked, honestly.
I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind.
97
120
10
2,760
315,124
when you observability bill is 2X your cloud bill 😅
7
1
1
20
1,673