It is crazy how we are one algorithm change away from feeling isolated and unheard on the internet. Glad X is back to what it was in 2021.
The career of a software/infrastructure engineer is mostly doing boring things and asking ridiculous questions in hopes of making order out of chaos and making light work of something. That’s when that satisfactory smile is put on our faces.
Always a delight to read such blog posts.
Debugging infra at scale is rarely about one big “aha” moment.
In our latest engineering blog post, Brian Stack (github.com/imbstack/) recounts his journey through the "Kubernetes hypercube of bad vibes" and how one small flag change led to a significant impact.
render.com/blog/how-we-found…
You’ve likely come across terms like HTTP, TCP, IP, and TLS, or heard discussions about latency and bandwidth. But what do these concepts really mean, and how do they work together?
I covered that in my latest post on the TCP/IP protocol, where I dive into how the internet works:
Just published a follow-up article exploring HTTP/3 and QUIC:
themsaid.com/http3-and-the-q…
Last week, I wrote several articles on secure web sessions and building a session manager in Go.
If you’re curious about how web sessions work, how to secure them, or just want to read some Go code—give it a read!
Yesterday I helped a friend with their startup's single server going down after an update. Turned out the contractor's AI generated code loads over 12k records from the database and presents them in JSON responses (on every request).
The pool of bad software contractors is already huge. With AI, I'm afraid it's getting even larger. I think it'll be very difficult for experienced coders to compete in contracting gigs.
Had a really good time talking with Nuno face to face for the first time yesterday. 5 years working together and I only discover the guy is very cool in reality as he is on Slack.
