Piotr Wyczesany

I was writing a type-safe Fluent Builder. Cursor casually dropped the name:
“Curiously Recurring Template Pattern.”

I laughed. I’ve done that before. I just didn’t know it had a name.

LLMs are great at connecting intuition with terminology. Not solving for you, but revealing what you already knew.

Good to be back.
Summer time in #Kraków #Cracow

One agentic coding tip I'm using is asking the agent to prefix its responses with an emoji to confirm it has read a certain file.

It's good - when I see certain emojis I know for sure that it has certain rules files in context.

Picked this up from Llewellyn Falco at Craft Conf 🧠

Current status. Dubrovnik.

Ouch. 😅

Current status.

Current status. Mostar.

Just walked past #DevoxxPL.
Funny — I’m not attending, but it’s literally on my daily walking route.

From an engineering perspective, software wants to be decoupled. From a business value perspective, software wants to be deeply interconnected. That's the fundamental friction that software design, and Domain-Driven Design specifically, attempts to address.

Eventually Inconsistent I help your development team become strategically more efficient by aligning them with the business domain they are working in, instead of just focusing on technical solutions. <p><a href="https://pat...

Right now?

AI is a powerful tool.
But it’s not a shortcut.
Not magic.
Just another part of the toolbox.

Use it with intent — and with eyes open.

Full post here:
🔗 www.eventuallyinconsistent.com/2025/05/ai-i...

9/9

I still think it’ll improve.

Models will get faster. More accurate.
Maybe we’ll trust them more.

Or maybe we’ll just get better at supervising more changes — safely.

8/9

But when it came time to implement those insights?

Nope.
It couldn’t follow through.
The gap between idea and reliable code was just too wide.

Prompting alone couldn’t bridge it.

7/9

That said — it’s not useless.

I used it to explore ideas, unblock some stuck thinking, and even got a few design insights I hadn’t considered before.

It’s a good brainstorming partner.

6/9

Eventually it felt like pairing with a junior dev.

Smart. Fast.
But forgetful. Sometimes chaotic. Occasionally reckless.

Like someone who might’ve just lit the kitchen on fire while you weren’t looking.

5/9

For complex logic? It gets slippery.

You correct mistakes → update the prompt → things look good…
Then the same bugs sneak back in.

Even if you explicitly told it not to do that.

Frustrating.

4/9

For small changes, it’s helpful.
AI picks up some context and gives some good answers.

But it always needs review.
Always.

And even then, small bugs slip through.

3/9

If someone says AI writes all their code, one of two things is true:

the problem is extremely simple

or they’re overselling it

In real systems, with real constraints, you still need actual engineering.

2/9

Three weeks ago, I joined an internal AI hackathon.
The rule: one day, build anything work-related — but rely almost entirely on AI.

Obviously, I chose to refactor a core, complex part of the system.
You know me — I like a bit of #DDDesign chaos.

A thread 👇
1/9

We just scheduled a Craft-IT ticket raffle (and a discount) at dddkrk.pl meetup: www.meetup.com/ddd-krk/even...

YouTube video by Alter Worlds AI Heroes of Might and Magic 3 Units in Real Life - Tower | AI Generated

www.youtube.com/watch?v=N9Fo... cool :)

Haha understanding is one thing. The other one is the song and the artist himself. 😏

www.instagram.com/p/DI3bp34sEKO/ - You'll get that only if you are Polish 🤷 - with sound 🎶

Sure, I use #Java records whenever I can, and I encourage others to use them even more.

They are (almost) perfect for #DDDesign Value Objects.

Current status.

Polish "Wind and Truth" part 2 covers were revealed.

For the first time, I think the hardcover (number 2) is much, much, much better than the paperback (number 1).

(However, the paperback for part 1, with Szeth is still a masterpiece: bsky.app/profile/pwyc...)

#StormlightArchive #WindAndTruth

Current status.

Current status.

Yup, as @ericevans0.bsky.social once said: "not all the system will be will designed".

Great Thread! 👇

Also, the drift can happen more than once, causing more than 2 models to exist.

(Including the modernized one(s)) 😏

I've recently started using the term "valuable slice" over "vertical slice".
If you're delivering value in a slice then often you will have a vertical slice anyway.
Focus on the delivering something valuable, not on how it slices your architecture.