I help software developers build successful software through software architecture that fits. | Consultant & Trainer @ imarqio

Trying to move 50 people in a VW Polo? Bad idea.

Trying to scale to 50 developers with architecture knowledge stuck in one person's head? Just as bad.

Architecture development needs to fit your team - like transportation fits the number of people. With 5 developers in one team, informal coordination works. With 50 developers across multiple teams, you need systematic approaches and distributed knowledge - or your teams will trip over each other.

Know the feeling? You hire more developers, but software delivery slows down. Every new feature takes longer. Time-to-market drops. And you ask yourself: "Why is everything getting slower when we're investing more?"

The problem isn't your team. The problem is that knowledge sits in 2-3 heads - and the approach doesn't scale when you grow to multiple teams.

Most companies then try one of 3 solutions:
→ Book external training (theory without context to your organization)
→ Hire a full-time architect (concentrates knowledge in one person again)
→ Let the team figure it out themselves (overwhelming without systematic guidance)

All 3 fail at the same point: They don't embed architecture in the organization.

And meanwhile, the clock is ticking: features pile up, the business is waiting, your best developers are considering leaving.

I do something different: I help decision-makers in growing software companies embed architecture knowledge and ownership in your teams. Not through dependency, but through enablement.

My Context-First approach:
- I start with: Who makes decisions? How do you communicate? Only then: Which patterns?
- I develop WITH your teams, not FOR your teams
- My success is measurable: you don't need me anymore

22+ years of practice, 2,800+ hours of training, 321+ successful projects.

The pattern I see again and again: architecture knowledge in 2-5 heads. My work: Distribute that knowledge into the organization. Typical timeline: 3-6 months to independence.

What does your organization look like when I'm gone?
Your teams make coordinated, autonomous architecture decisions, new team members become productive quickly, and you deliver reliably - without me.

The longer you wait, the deeper the dependency on individual knowledge holders becomes.

I deliberately work with only a few organizations at a time. In our first conversation, we'll figure out if I'm even the right fit for you. No pitch, no obligation, just clarity. 30 minutes. Message me.

Sönke Schwenk

Stijn Dejongh is a software developer, architect, and coach. He has been working in the software industry for over a decade, specializing in government and large enterprise software development. He has been an independent consultant since 2020, helping organizations improve their technical practices and processes.

Beyond his consultancy, Stijn is fueled by a passion for knowledge-sharing and skill improvement. Over the years, he has been a mentor to many junior developers and has written numerous articles and blog posts on software development, personal growth, and productivity. Some of his writing can be found on his knowledge sharing website (patterns.sddevelopment.be), linked-in articles, or his github page.

taplio

The Battle

Sönke Schwenk

Stijn Dejongh

Followers

Posts

Engagements

Likes

Ready to grow your LinkedIn presence?