Burnsedia
Boomerbill Is Live
Re:
on Friday March 13, 2026 @07:29PM (#47371399)
Hey HN - I just build a django opencode agent suite
It’s a markdown-first OpenCode agent pack for spec-driven Django monolith workflows, aimed at solo Django devs and small teams.
Core idea: use AI for fast scaffolding/review, but keep humans in control of business logic and enforce safety with local-only blocking checks.
What it includes:
- One-click install for Django-focused agents, commands, skills, and local tools
- Default flow: spec -> architecture -> scaffold -> review
- Local blocking quality gate: ruff, black, manage.py check, pytest
- Guardrails for permissions and service-layer boundaries
- Migration/release safety baked into the workflow
Why I built it:
- AI moves fast but can still produce risky Django patterns
- Solo devs need speed without losing production safety
- Small teams need repeatable architecture + review discipline
Install:
curl -fsSL https://raw.githubusercontent.com/Burnsedia/Django-Agent/mas... | bash
I’d love feedback on:
1) Whether local-only quality gates are enough for your workflow
2) What Django monolith pain point you’d want automated next
Sherlock MCP server so you can use AI to do OSI research
Case Study: Saving over 99% by Migrating from Public Cloud to Private Cloud
Re:Ask HN: Which Open Source License to Choose for a Python Language S...
on Sunday August 31, 2025 @04:25PM (#45086756)
MIT is great for fast adoption, but if you go that route, you’d need closed-source add-ons or a SaaS layer to monetize. Apache is also good for adoption and for getting corporate clients and sponsors, but the trade-off is that anyone can take your code and repackage it without contributing back.
GPL or AGPL gives you more direct monetization options because it forces reciprocity. GPL protects against proprietary redistribution, while AGPL goes further by preventing companies from just hosting your project as a service without contributing. That makes AGPL especially useful for developer tools like LSPs, since it also sets you up for a dual-license model (AGPL for community use, commercial licenses for companies that want to integrate it into proprietary tooling).
In short: MIT/Apache = growth and sponsorship potential, GPL/AGPL = stronger control and licensing revenue. It really depends on whether your priority is fast adoption or direct monetization.