Paved roads over gatekeeping
Make the right way the default with templates and shared workflows, instead of reviewing every team into compliance.
~/what-i-do/platform
Good platforms are paved roads: the safe, observable, repeatable way is also the quickest way to ship. I build the plumbing that makes that true, from queues and retries to config and policy as code.
Make the right way the default with templates and shared workflows, instead of reviewing every team into compliance.
Pipelines, configuration and policy live in the repo, reviewed and versioned like any other change.
Seen in: Foundry →
Slow or unreliable work goes on a queue, with retries and backoff, idempotency and an audit trail, so a flaky dependency never takes the product down.
Seen in: Illux Product AI →
Providers, databases and AI models sit behind ports and adapters, so changing vendor is a new adapter, not a rewrite.
Seen in: Jobbuddy →
Generative-AI product enrichment & room visualization for Shopware 6
A fail-safe guardrail for LLM agents' tool calls
AI job-application platform - from posting to tailored CV
Spin a wheel, settle movie night
from hourly
Custom Shopware 6 plugins - admin modules, storefront plugins, DAL entities, migrations, scheduled tasks and Messenger/RabbitMQ workers - built the way I built a business-critical one for WEXO.
from hourly or fixed
From MVP to maintainable product: Spring Boot, .NET or Node backends with clean architecture; Angular, React, Vue or Astro frontends; Postgres with full-text and vector search.
No posts on this yet. Coming soon.