A common problem with a familiar shape: a process can dial outbound to the internet, but nothing on the internet can dial it back. Your dev server on a laptop. A service in a private VPC. A homelab app behind your router. A container in a pod with no ingress. Same shape every time — outbound works, inbound doesn't. rift is a small Go binary I built to solve that. Run it as a server on a VPS you ow
A few years ago I solved 200 LeetCode problems and still froze on Mediums I hadn't seen. The breakthrough wasn't another hundred problems. It was a different loop. A problem asks for the longest substring with at most K distinct characters. You've solved sliding window before. Maximum sum subarray of size K, done. Longest substring without repeating characters, done. This third one stalls you. Twe
Posted by the RagLeap team — building RagLeap, a private-server AI business platform When we started building RagLeap, the easiest path was obvious: spin up an API, connect to OpenAI, store everything in a managed cloud database, and ship fast. The Problem Nobody Talks About You upload your documents, customer data, order history It works. But ask yourself: where is your data right now? What Our U
I like servers. Not in a "let me spend Saturday hand-tuning nginx" way. More in a "this $6 VPS is sitting right here and could probably run half my side projects" way. The weird part is that deploying to one still feels more complicated than it should. For a lot of small and medium web apps, the app itself is not the hard part. The annoying part is everything around it: building the app getting it