Architectural Tests: Encode the Decision Once, Enforce It Forever
A PR looked fine and quietly broke a module boundary anyway. Nobody caught it, because the boundary lived in my head. So now the build catches it.
From Code to Impact
Eight teams since 2018. Pick one to see what I did there.
In The Pocket
- Designing and developing backend systems for DVZ (Dienst Vreemdelingenzaken - Belgium Immigration Office)
- Building scalable APIs and platform infrastructure for critical public sector applications
- Implementing Infrastructure as Code with Terraform and Bicep for Azure deployments
- Contributing to system architecture decisions in a product-focused digital studio environment
.NET 10
Azure
SQL Server
PostgreSQL
EF Core
Dapper
Dapr
Docker
Kubernetes
Terraform
Bicep
What I Bring
Value I deliver to your team.
Technical Leadership
I design architectures, define patterns, and guide teams through implementation.
ADRs for decisions that matter, clean boundaries between domains. I lead technical discussions, mentor developers, and make sure the team knows where we're headed.
Problem Ownership
Complex systems don't scare me. I decompose them into manageable pieces.
Vertical slices, incremental delivery, coherent high-level design. When something breaks at 2am, I'm the one who wants to understand why, not just patch it.
Quality at Speed
Fast iterations with solid foundations. Ship often, fail forward.
CI/CD pipelines, automated tests, feature flags, observability. I believe you can have both velocity and reliability if you invest in the right guardrails early.
Research First
Before I commit to a stack or pattern, I spike it.
POCs, benchmarks, edge cases. I've been burned by shiny-object syndrome before. Now I validate assumptions before they become architecture.
Team Player
Clear async communication, honest code reviews, pair when it helps.
I connect with the team and make sure context flows. Good code is a team sport. I'd rather have a healthy team shipping good code than a hero shipping great code alone.
Regulated Domains
Medical records, immigration data, government systems.
Security and privacy baked in, not bolted on. I understand compliance isn't optional in these spaces, and I design with audit trails, access control, and data protection from day one.
Engineering with Purpose
Bridging ideas, architecture, and execution.
Timothy De Bock
Nearly a decade of experience building software in demanding domains like public services and healthcare related platforms.
I work mainly with .NET and Azure. I turn complex requirements into clear architecture and production ready code that stays maintainable over time. I focus on reliability and performance and clean delivery. I enjoy collaborating with teams and keeping communication straightforward.
Outside work I am a father of two. I recharge with weekend BBQ and books and games.
Tech Stack
What I build with day to day.
Backend
.NET 10
ASP.NET Core
Minimal APIs
EF Core
Dapper
MediatR
FluentValidation
Background Services
gRPC
LINQ
AutoMapper
xUnit
FluentAssertions
Azure & Ops
Azure App Service
Azure Functions
Azure Service Bus
Azure Storage
Azure SQL
Cosmos DB
Application Insights
Bicep
Terraform
Docker
Kubernetes
GitHub Actions
CI/CD
Frontend
Blazor Server
Blazor WebAssembly
Angular
React
Vue.js
ASP.NET MVC
Bootstrap
Tailwind CSS
MudBlazor
Data & Messaging
SQL Server
PostgreSQL
Cosmos DB
MassTransit
RabbitMQ
Outbox Pattern
Saga Pattern
CQRS
Hangfire
Redis Caching
Message Replay
AI-Enhanced Development, Done Responsibly
Engineering judgment first. AI second.
I use AI tooling every day. It speeds up the typing. It does not replace the engineering thinking. You are trusting me with the decision: architecture, trade-offs, what's actually safe to ship in a regulated environment. Not the keystrokes.
A few things I hold to:
Fundamentals first.
Deep knowledge of patterns, systems and security is what makes AI output usable
instead of just confident-sounding text.
Privacy is a tooling decision.
I know which tools send data where. I know what should never leave a client's environment.
Every diff gets human review.
AI proposes. I decide.
Common Questions
The things people usually ask first.
Field Notes
Ideas that won't leave my head.
Fundamentals Matter More in the AI Era, Not Less
The model is plausible. That's its whole trick. Deciding whether it's actually right takes the stuff you already know, and without that you're shipping whatever sounded confident in the IDE.
AI Tools and the Data Boundary: What Should Never Leave the Environment
Using AI tools and understanding them are two different skills. In regulated work, the gap between those skills is where breaches happen.
Ready to talk?
Let's build something together
I'm always open to interesting missions and good conversations.
I typically respond within 24 hours
Availability
- Open for short-term consulting and long-term engagements
- On-site in Belgium or remote (CET)
- Focus: .NET, Azure, APIs, architecture, messaging, performance