Dominik Czerwiński
Solution Architect | .NET | Distributed Systems | Cloud
"Pragmatic approach to solving complex problems."
About me
I am a .NET architect and developer. I design business systems using DDD, modularity and clear responsibility boundaries, so they can evolve without adding unnecessary complexity.
I am currently focused on practical Generative AI workflows in software delivery: from knowledge gathering and specification to implementation, review and technical decision support.
System architecture
I design backend system architectures — from modular monoliths to distributed systems. I focus on clear boundaries, consistency and long-term evolution.Working with business
I collaborate with business stakeholders and end users to understand real needs. I help translate them into technical solutions and identify opportunities for improvement..NET and Cloud
I build solutions using .NET and Azure, focusing on scalability, reliability and maintainability in production environments.Latest from the blog
From Vibe Coding to AI Workflow: What Controls an Agent?
AI workflowLLMSoftware deliveryAI agentsSDLC
In the first post, I explained why a single prompt is not enough in a larger project. The natural next step is an agent, but that word gets used very broadly. Before talking about tools and configuration, we need to define what we actually mean by an agent in AI-assisted software work.
From Vibe Coding to AI Workflow: Why a Single Prompt Is Not Enough
AI workflowLLMSoftware deliveryVibe codingSDLC
AI can quickly make software development look easier than it really is. You type a prompt, get code, and sometimes even a complete working project. With a small project or an isolated part of a system, everything looks good. This becomes a problem when that code has to fit into an existing system that already has its own rules, past decisions, and constraints - not an empty repository.