Queuebird
A lightweight job queue for services that need reliable background work without a heavyweight broker.
- At-least-once delivery with idempotent workers
- Retries, backoff and a dead-letter queue
- Small HTTP API for enqueueing and inspecting jobs
I design services that stay simple under load: clear APIs, boring infrastructure, and automation that makes shipping feel uneventful.
{
"alias": "Dankaristic",
"role": "Backend Engineer",
"focus": [
"Backend Engineering",
"Distributed Systems",
"Automation"
],
"languages": [
"Go",
"Python"
],
"status": "building things"
}
I'm a backend engineer who likes systems that are easy to explain.
Most of my work sits between APIs, data stores and the tooling that keeps them honest. I care about small interfaces, observability and leaving things easier to maintain than I found them.
Let's build something together ↗Technologies I use to build, deploy, and maintain software.
Real-world projects, experiments, and engineering challenges.
A lightweight job queue for services that need reliable background work without a heavyweight broker.
A CLI that turns repetitive release steps into a single, reviewable command.
A small double-entry ledger service built to explore event-driven design and strict consistency.
Build the smallest thing that solves the problem, measure it, and only add complexity when the evidence asks for it.
Engineering lessons, experiments, and things worth sharing.
Why retries are inevitable, and how to make endpoints safe to call more than once.
A practical mental model for channels, cancellation and avoiding the usual deadlocks.
Small scripts and good defaults beat elaborate platforms for most repetitive work.
Open to engineering opportunities, technical collaborations, and interesting problems worth solving.
Let's talk