shcallaway

8 ms·

1.
Our $8M Seed Round and Open Beta(sazabi.com)
2 points by shcallaway 3mo ago|0 comments
2.
Sazabi: The AI-native observability platform for fast-moving engineering teams(sazabi-git-main.preview.sazabi.dev)
6 points by shcallaway 6mo ago|0 comments
3.
The Sazabi Manifesto(sazabi.com)
1 points by shcallaway 7mo ago|1 comments
4.
by shcallaway 7mo ago
AI has changed what's possible in software systems. Observability hasn't caught up. This manifesto lays out a path forward.
5.
by shcallaway 8mo ago
I completely agree w/ your points about why observability sucks: - Too much setup - Too much maintenance - Too steep of a learning curve This isn't the whole picture, but it's a huge part of the picture. IMO, observability sh
6.
by shcallaway 8mo ago
Vibe-coders don't comprehend how the code works, yet they can create impressive apps that are completely functional. I don't see why the same isn't true for "vibe-fixers" and their data (telemetry).
7.
by shcallaway 8mo ago
You're so right. > We'll have solved the problem when AI detects the problem and submits the bug fix before the engineers wake up. Working on it :)
8.
by shcallaway 8mo ago
You're not the first person I've met that has articulated an idea like this. It sounds amazing. Do you have an idea about why this approach isn't broadly popular?
9.
by shcallaway 8mo ago
These are great. I should have included them in my timeline! Huge fan of historical artifacts like Cantrill's ACM paper
10.
by shcallaway 8mo ago
This is a super insightful comment & there is a bunch that I want to respond to but I can't do it all neatly in one comment. Hahaha I'll choose this point: > reliability is still ultimately an incentive problem This is a fa
11.
by shcallaway 8mo ago
Hello! Yes, you are right - observability and APM have both been around for many decades, but the incarnations that most people are familiar with are the ones that emerged in the 2010s. My intention wasn't for this post to be a compreh
12.
Observability's past, present, and future(blog.sherwoodcallaway.com)
79 points by shcallaway 8mo ago|29 comments
13.
by shcallaway 10mo ago
Wow, this is great. I have been using Inngest for over a year now and really like the APIs you guys have created for defining step functions / event handlers. I'm very glad to see that this API is now open-source so that it can be
14.
by shcallaway 10mo ago
I've been programming for 15 years now, 10 years professionally, and have worked at 5 startups. These are my reflections on the first decade of my career. Also, an announcement: I’m starting something new!
15.
Round Two(blog.sherwoodcallaway.com)
6 points by shcallaway 10mo ago|1 comments
16.
by shcallaway 11mo ago
Congrats LC team! I don't have much experience w/ "vanilla" LangChain or the LC Python tools, but I've been an avid user of Deployments and the LangGraph TypeScript SDK for like a year now (started using Deployments
17.
by shcallaway 5y ago
Love this. As engineers, we need to do better than reviewing in the GH web interface...
18.
Bookmarklet for Getting Past Paywalls(gist.github.com)
1 points by shcallaway 8y ago|0 comments
19.
Download a CSV of Wealthfront's Career Launching Companies(gist.github.com)
3 points by shcallaway 8y ago|0 comments
20.
by shcallaway 8y ago
I love the idea that typed languages create backpressure. I have very little confidence in peoples' ability to create well-designed (in software architecture terms) projects.
21.
The simplest, cleanest todo list for command line(github.com)
3 points by shcallaway 8y ago|1 comments
22.
by shcallaway 9y ago
At the very least, this experience has made me question the conventional wisdom that microservices = good and monolith = bad.
23.
by shcallaway 9y ago
My company is in the process of building out an integration test suite for our microservices platform. A few pain points: 1. The tests themselves are housed in a separate repository, so you can't update the tests alongside your service
24.
by shcallaway 9y ago
Postman can be handy for quick and dirty HTTP tests. Unfortunately, I find the Postman GUI unintuitive. The alternative -- working with minified JSON -- is equally painful. Edit: English
25.
A better guide to using Amazon S3 with Rails(peptwenty.wordpress.com)
1 points by shcallaway 10y ago|0 comments