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

Nicholas Ocket

Backend developer

About Coding

The mission of About Coding is to help developers to build better software. I want to share real and valuable content, show them the importance of software design and how to apply it correctly. This will help developers grow in confidence, allowing them to make better coding decisions and tackle more complex problems. It helps them become more valuable developers

Oprichter

GemOne

I am building Proof of Concepts mainly using Java and Spring boot, mainly in the field of trace and track. Even though these projects are just proof of concepts, we hold high coding standards, making sure that we deliver something understandable, maintainable and testable. 
Furthermore, I investigate IoT technologies and electronics in the field of track and trace. This is very versatile, allowing me get out of my comfort zone (looking into RFID cards, writing C code for small devices, learning about basic electronics).

Senior software engineer

Lightspeed HQ

Maintain and expand the Lightspeed hospitality PoS. During my time at Lightspeed, I have done several big and impacting refactorings, fixed some tough database related problems and added new functionality and features. Tech stack: Java, Spring, Spring boot, Akka, Kafka, Redis, MySql

Roularta Media Group

Maintaining existing in-house applications, help with building the new application for managing online subscriptions.  Tech stack: Java, maven, Spring, REST, Angular

Senior Java Developer

At TVH I maintained some existing applications and learned a 4GL language (Progress). Using that language, I took care of some big data migrations, which I later partially automated by writing a java application together with Spring and Jersey as base for the REST api. The frontend was javascript and AJAX calls to the REST api.

Java software developer

Thomas Cook Retail Belgium

Creating and maintaining existing software in the travel sector. My most memorable project was optimizing the website for packaged travelling to the USA. Together with my analyst, we cleaned up most bugs and fixed most functionality. Tech Stack: Java, Spring, maven, REST services

Java Software developer

Lisis

Extending the existing POS framework in Java. I was responsible for finishing smaller projects, such as daily PoS reports, etc. Tech stack was mainly java. The daily PoS reports were made with JasperReports.

Junior Java programmeur

MGB Tech

Mostly training projects in preparation of later projects. Tech stack: Java

Junior java developer

Most developers can write code. Few can turn business problems into maintainable solutions.
That's the difference between being replaceable and being irreplaceable.

I teach software design...the one skill that separates good developers from great ones. The skill that gets you promoted, trusted with important projects, and paid what you're actually worth.

After almost 2 decades and countless painful lessons, I've learned what most developers never figure out: how to go from problem to well-designed code systematically.

No more guessing. 
No more design paralysis.
Just confidence to start building. 

Ready to stop coding and start building? 

Check out my free resources: www.aboutcoding.be
Or message me directly - I respond to everyone in due time

taplio

The Battle

Sönke Schwenk

Nicholas Ocket

Followers

Posts

Engagements

Likes

Ready to grow your LinkedIn presence?