Piotr Wyczesany

Piotr Wyczesany

@pwyczes.patternapplied.com

Tworzę kurs http://cqrsapplied.pl. | I distill DDDesigners. | Domain-Driven Designer, Software Craftsman, Legacy Fighter, and ex-capoeirista. | More -> https://bio.link/pwyczes

268 followers96 following125 posts

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.

Piotr Wyczesany reposted

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 🧠

Piotr Wyczesany reposted

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.

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

View full thread

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

View full thread

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

View full thread

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

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

Piotr Wyczesany@pwyczes.patternapplied.com

Damn, this Polish "Wind and Truth" cover is just perfect! 😍 I absolutely love it and can't wait!!! #StormlightArchive #WindAndTruth

Great Thread! 👇 Also, the drift can happen more than once, causing more than 2 models to exist. (Including the modernized one(s)) 😏

Nick Tune@nick-tune.me

An under-appreciated benefit of architecture modernization is the chance for semantic convergence (of your software and mental model). It's common in legacy systems for words and concepts not to align with how people think and talk about the business. 1/4 #architectureModernization #dddDesign

Piotr Wyczesany reposted

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.