An opinionated list of Python frameworks, libraries, tools, and resources
We're all learning how to ship more side projects. If you're "in the bubble" it can feel like everyone is repo-maxxing. Shipping weekly. Spinning up agents to scaffold full apps overnight. New OSS dropped every Friday. The reality I see with most developers is much more normal: They have six or seven repos sitting in various states of half-attention. A side project from last year that still gets a
AutoGPT is the vision of accessible AI for everyone, to use and to build on. Our mission is to provide the tools, so that you can focus on what matters.
My scrapers run on PythonAnywhere. My phone runs Termux. I wanted them to talk to each other. The standard options all had the same problem: they required infrastructure I didn't want to maintain. Firebase — cloud lock-in, SDK overhead, costs money at scale Ngrok — exposes a port on my phone, dies when the tunnel resets A VPS with Redis — another server to maintain, SSH into, keep alive Webhook to
Before you train a model, you need data in the right format. This took me longer than I expected and taught me a lot about how LLMs actually learn. I used MedQA USMLE — real medical licensing exam questions used to certify doctors in the US. It's available on HuggingFace for free. from datasets import load_dataset dataset = load_dataset("GBaker/MedQA-USMLE-4-options") Each sample looks like this:
Series: How Machines Learn: A Complete Guide from Zero to AI Engineer Phase 6: Machine Learning (The Core) You've been hearing "machine learning" for years now. Your phone uses it. Netflix uses it. Your spam filter uses it. Every tech company puts it in their job posts. And yet, if someone asked you right now to explain what machine learning actually is in plain words, you might freeze up a little
I have a confession: I used react-i18next for years and genuinely never questioned it. It worked. It was everywhere. Every project I joined during my internships at DNB had it set up. You install it, you configure it, you wrap your app in a provider, and you ship. Done. But then I started building more things on my own, projects where I got to choose the stack from scratch, and I started noticing
The 3 AM Nightmare Last week, I let an AI agent run loose on my production server. It was fine — until 3 AM. To interact with the agent, a user must first authenticate across Gmail, a support desk, and a payment platform — all before the agent takes its first action. Permission denied. Permission denied. Permission denied. Three different connectors. Three different auth systems. One very tired