Python

Dagger CI Pipelines: Write Your CI in Go or Python Instead of YAML

Dagger lets you write CI/CD pipelines in Go, Python, or TypeScript instead of YAML. Your pipelines run inside containers, execute identically on your laptop and in CI, and get type-checked by your compiler or linter before they ever touch a remote runner. If you’ve spent hours pushing commits just to debug a GitHub Actions workflow, Dagger is the fix.

The core idea: pipeline steps are function calls in a real programming language. Each function call builds a directed acyclic graph (DAG) of container operations. The Dagger Engine (built on BuildKit ) executes this graph with automatic parallelization and layer caching. You run dagger call ci --source . locally, get the same result in GitHub Actions, GitLab CI, or CircleCI, and never write vendor-specific YAML again.

NATS JetStream vs Kafka: Simpler Ops, Sub-Millisecond Latency

To wire up loose Python microservices, use NATS JetStream as the message bus with the nats-py client. JetStream gives you durable consumers, full stream replay, and exactly-once delivery through message dedup and double-ack. It does this in sub-millisecond time, with one small server binary. No Kafka brokers, no ZooKeeper.

This guide covers JetStream setup, pub/sub with durable consumers, a three-service order pipeline, and the steps to harden it for production.

Claude Agent SDK: Build Custom AI Agents Without Reinventing the Orchestration Layer

The Claude Agent SDK is the Claude Code engine stripped down to a library. Same agent loop, same built-in tools, same context handling, but you call it from your own Python or TypeScript code instead of the CLI. If you’ve used Claude Code to read files, run shell commands, search codebases, and edit code, the SDK points that same machinery at any problem you want. No human needs to sit in the loop.

Claude Code for Data Analysis: Process 500K Rows Without Writing Code

Yes, you can point Claude Code at a 541,909-row retail dataset and walk away with a six-sheet Excel workbook, professional charts, and a parameterized report script, without opening a Python file or debugging a single line of code. The complete workflow takes roughly 15 to 20 minutes from raw data to finished output.

The goal is real delegation. Claude handles setup, cleaning, math, and charts. You focus on the right questions to ask.

URL Shortener in 200 Lines of Python

I’ll show you how to build a real URL shortener in under 200 lines of Python. We’re going to use FastAPI for the web layer, SQLite for storage, and base62 encoding for short codes. I’ll walk you through a redirect endpoint, a click counter, and rate limiting with SlowAPI . In my experience, this simple stack handles millions of links on one server.

Key Takeaways

Build a production-ready URL shortener with fewer than 200 lines of Python.
Use SQLite for zero-config storage that handles thousands of requests per second.
Implement base62 encoding to turn database IDs into short, clean strings.
Protect your service with SlowAPI rate limiting to block spam bots.
Deploy the entire app in a 50 MB Docker container behind a Caddy reverse proxy.

Architecture and Tech Stack Choices

Before I write any code, I want to walk you through why I picked this stack. Picking the wrong stack for a small project either over-engineers it or under-builds it. I’ve seen systems fall over at a few hundred users, and I want to help you avoid that.

AppDaemon 4.5 State Machines: Beyond YAML Automations

AppDaemon 4.5.14 is a Python runtime that runs next to Home Assistant . It lets you write rules as full Python classes. You get state machines, scheduling, outside API calls, and logic that YAML can’t handle. Install it as a Home Assistant add-on, drop a Python file in the apps folder, define a class that inherits from hass.Hass, and use callbacks like listen_state() and run_daily() to drive multi-step flows, saved values, and live data.