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

Vedran B.

Many such cases. 

OOP pushed by DDD has become a dog chasing it's own tail.

I've been seeing more and more posts on tech Reddit like that.

Good. Push back against lunacy.

Vedran Bilopavlović

NpgsqlRest Automatic PostgreSQL Web Server

Here is a really, really interesting side-by-side comparison I did with a little help from AI. You tell me, is it far off from reality?

1. PostgreSQL analytical query

Fairly complex zero-islands detection analytical query in a hypothetical IOT scenario. Something that you would probably have to write ad-hoc if some of your devices malfunctions. It detects consecutive zeros in data, and it runs very fast.

2. Same query on MongoDB

I'm not sure how this would even run, but AI says not too good. Query planners are not even comparable. If we ignore the sheer ugliness of that query (if you can even call it that), and let's just say that it is a matter of personal taste (although the Mongo version is longer), why would you want to deprive your system of these kinds of ad-hoc analytics?

But wait, it gets worse. Let's say, we don't want this to be ad-hoc anymore - we want this to be on our dashboard.

3. Same PostgreSQL version in modern C# and .NET with EF and modern DDD

As we can see, modern EF has limited support for window functions. You can do one window function (and with a limited subset) via an extension that would translate a grouping expression into a window function (which makes it even more confusing, is it a grouping or a window function), but it cannot do two consecutive window functions one after another, so we must fall back to raw SQL.

But wait, it gets worse.

4. Modern C#/.NET fully Linq/DDD and everything

But we can always listen to wise advice from our beloved gurus and keep this business logic out of the database and SQL out of our codebase.

Nevermind that our codebase has now doubled again and bloated out of proportion (we haven't even got to the unit tests, oh boy), we are now actually downloading the database into memory in order to be able to process it properly. Performances of something like this are going to be abysmal.

And yet, so many teams are prepared to do exactly this - they are making their users suffer and wait for responses and pay huge cloud bills, just to make their domain pure and clean.

Insanity.

But, wait, it gets worse.

5. MongoDB with modern C# and .NET and DDD

At this point, I don't know what to tell you anymore. Just learn SQL. Thank me later.

I don't have anything smart to say about AI. The worlds best and brightest minds are on the case. But I do about PostgreSQL. What else to do on hangover Sunday, and I'm right?

Did you know you can format PostgreSQL intervals to a human-readable format directly in PostgreSQL?

Well, neither have I.

If we go and create an interval:  "select 8197156465 * interval '1 ms'" It returns boring "2276:59:16.465". Not very nice.

We can use the function "justify_interval" that adds days and months if the interval exceeds 24 hours, and so this "select justify_interval(8197156465 * interval '1 ms')" returns this: "3 mons 4 days 20:59:16.465". A little bit better, but we can do even better than this.

There is a setting called "intervalstyle" which is by default set to "sql_standard". We can set it to "postgres_verbose".

However, doing "set intervalstyle = 'postgres_verbose';" would affect the entire connection (session), which is problematic if we use a connection pooler (and who doesn't). So we must set it locally to a transaction scope, and in order to do that, our query needs to run in a dedicated transaction. So now we can do this and try with and without "justify_interval" function:

begin;
set local intervalstyle = 'postgres_verbose';
select 
    8197156465 * interval '1 ms',
    justify_interval(8197156465 * interval '1 ms');
rollback;

This returns two columns:
@ 2276 hours 59 mins 16.465 secs	
@ 3 mons 4 days 20 hours 59 mins 16.465 secs

For some reason, this PostgreSQL interval includes "@ " in front of every interval. So we can trim that:

begin;
set local intervalstyle = 'postgres_verbose';
select ltrim(justify_interval(8197156465 * interval '1 ms')::text, '@ ');
rollback;

Yields "3 mons 4 days 20 hours 59 mins 16.465 secs". Much better than "2276:59:16.465".

Just don't forget to read from the 3rd command (instead of the 1st), and that is it.

This Bun thingy is getting crazier and crazier but in a good way. 30% faster, 50% faster, etc 

I'm using it for a frontend build scripts and occasionally for some server services when needed for simple tasks, but more and more.

Crazy how we all got used of living woth JavaScript and all it's quirks and logical black holes.

Can't beat them, join them.

https://lnkd.in/d2zcYh5C

I am actually thinking of buying a pizza and coca cola to Claude Code to show my gratitude. Like every responsible and good manager does. Am I right.

Scrolling trough tech interwebs is new doom scrolling but only for software development:

- Software Engineering is just about to die
- Software Engineering is not dead yet, it just smells real bad
- Software Engineering is dying
- Software Engineering is almost dead
- Software Engineering is dying and is dead
- Software Engineering is buried

You mean to tell me no more ORMs, no more DTO mappings, no more DI configurations, no more Repository Service Unit of Work Query Builder Domain Object Immutable Record bullshit? Is that what you saying? Good riddance.

And why we were doing that in the first place? 

Just to execute the query on something like PostgreSQL that looks something like in this picture bellow?

If software engineering is dead, and AI generates all the code, then we certainly can skip all of that and just instruct AI to construct raw SQL — and cover everything with AI-generated tests.

Think about it:

☑️ Schema is the full context, everything that AI needs actually a single source of truth
☑️ SQL is the best-understood language, LLMs have seen more SQL than any framework in existence.
☑️ One artifact per feature, no coordinating across layers, fewer hallucinations
☑️ Instant verification — test the function with Pg/PlSql asserts, not through 7 layers of abstraction

That is, if you use automatic web server you your PostgreSQL: https://lnkd.in/dVsE-3Q8

☑️ Less context means fewer hallucinations, AI can't mess up your DI config, domain whatever or immutable thingy if there is none 
☑️ If so much code is either automated (http, endpoints, infrastructure, etc) or auto-generated (TypeScript fetch modules, HTTP files for testing, etc) - then we have reduced our chances for bugs and errors.

It is a radical concept, but such are these challenging times. I believe this is the way.

taplio

The Battle

Sönke Schwenk

Vedran B.

Followers

Posts

Engagements

Likes

Performance ScoreVedran B.'s LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Sönke Schwenk

Vedran B.

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Vedran B.'s LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreVedran B.'s LinkedIn Performance