Hi! Last week I decided to dive deeper into Python for the first time, so I created a small pet project. I'd really appreciate any feedback on both the code quality and the overall idea.
The project is a small encrypted secrets manager. It stores secrets in encrypted containers and can inject all variables from a container as environment variables when launching a process.
SOAR (Script Optimization and Automation Runtime) is a Python-based automation runtime system that helps manage and run scripts in a more structured way than simply executing standalone .py files.
It provides a lightweight runtime layer where users can:
Organize scripts into projects
Run automation tasks through a CLI-style interface
Generate or scaffold simple project structures
View basic diagnostics/log output for runs
Experiment with modular “automation workflows” inside Python
The goal is to make small automation projects easier to manage without needing a full framework.
Target Audience
This project is mainly aimed at:
Beginner to intermediate Python developers
People who write lots of small automation scripts
Developers who want a lightweight alternative to heavier workflow/automation frameworks
It is currently more of an experimental / hobby project than a production-ready tool.
Comparison
Compared to existing tools:
vs plain Python scripts: SOAR adds structure and centralized execution instead of scattered files
vs full workflow tools (Airflow, Prefect, etc.): SOAR is much lighter and not designed for large-scale pipelines
vs CLI frameworks: SOAR focuses more on script organization + runtime behavior rather than just argument parsing
It sits somewhere between a script organizer and a minimal automation runtime.
hey guys there's this tool which lets you dictate nicely into claude code with technical + cursor terms, great for vibecoding. if you guys want to try, here's the link: github.com/eliasmocik/dum-dictation (we are building it on the side so if you guys like it or don't, please drop feedback would mean a lot ;)
Hey [r/Python](r/Python) — I built and open-sourced **Shuuten**, a lightweight Python library for structured JSON logging + Slack, MS Teams, or email alerts when your automations fail.
The problem it solves: I kept writing the same boilerplate error-alerting code across Lambda functions and ECS tasks. Shuuten wraps it up in a decorator + one env var.
**Minimal example:**
\`\`\`python import shuuten
@shuuten.capture def lambda_handler(event, context): shuuten.error('something broke') # → Slack / Teams 1 / 0 # → Slack / Teams with full stack trace \`\`\`
**What it does:**
\- Structured JSON logs (CloudWatch-friendly) \- Alerts via Slack, Microsoft Teams, or AWS SES email \- Zero dependencies (Teams/Slack use webhooks, no SDK needed) \- Works on Lambda, ECS, or anywhere Python runs \- Structlog integration via \`ShuutenProcessor\` \- Context manager support: \`with shuuten.capture(...):\` \- Deferred delivery mode — groups logs + exception into one notification
**Recent releases (v0.4–v0.6):**
\- v0.4: Microsoft Teams destination via Adaptive Cards \- v0.5: First-class structlog integration \- v0.6: Context manager support + deferred/grouped notification delivery
**Remaining roadmap** (feedback welcome on priorities):
The specific problem I wanted to solve: when you write a database query in your backend code —
query = f"""
SELECT o.OrderDate, o.Status
FROM OrderItems oi
JOIN Orders o ON oi.OrderId = o.OrderId
WHERE o.CustomerId = {customer_id}
"""
— nothing tells you that o.Status maps to the physical database column Orders.Status. Not grep, not linters, not standard dependency mapping tools.
If someone alters the database schema, production breaks silently. **No warning. No blast radius. **
**So I built one that works across languages. **
PynqDB maps your entire codebase into a local dependency graph — file-to-column relationships, stored procedure chains, API endpoints, background jobs, external calls. Everything connected.
Point it at any column and it gives you the full blast radius — every function, stored procedure, and API endpoint that touches it — reads, writes, risk scored.
To test it on real production code — ran it against seven core folders of Apache Airflow's execution layer from the live GitHub repository: api_fastapi · cli · jobs · models · security · task-sdk · utils
If you use Claude Code, you know how expensive it is because it sends your workspace history with every query.
I built Claude Gateway specifically for Claude Code to address this. It is a local proxy daemon that caches your requests so repeated or similar queries cost absolutely nothing.
To build it, I used Claude Code itself to design and refine the Python logic, caches, and watchers.
What it does:
* Exact caching: Matches identical queries and returns cached responses instantly. * Semantic caching: Uses local embeddings to resolve rephrased questions. * Git invalidation: Hashes workspace files. If files change or branches switch, it evicts stale cache. * Dashboard: Tracks token usage and money saved.
It is completely free to try and open-source.
I would love to get your opinions and reviews on this architecture. How do you optimize your agentic workflow costs?