Kuba
@kuba.zalas.pl
320 followers 180 following 220 posts
Software Engineer https://zalas.pl
Posts Media Videos Starter Packs
Pinned
kuba.zalas.pl
Kuba @kuba.zalas.pl · Nov 15
At its core, I see #EventSourcing as a transformation of a command and past events to a list of new events.

The command is an intent to perform an action.

Events capture decisions made.

We can also get an error back if the command cannot be executed.
(Command, List<Event>) -> Either<Error, List<Event>>
kuba.zalas.pl
The day hasn't passed yet and I think Ghostty will also replace tmux for me.
kuba.zalas.pl
Careful. It's as addictive as years ago!
kuba.zalas.pl
I still can't believe I can just play this game on my mobile.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Sep 9
what's the trakcer/logging app on the screenshot?
kuba.zalas.pl
Kuba @kuba.zalas.pl · Sep 8
"You can’t do BDD. You might be able to write some scenarios or some acceptance tests, but they’re likely to be brittle and it’s unlikely that anyone will be interested. Here’s why."

lizkeogh.com/2011/03/04/s...
Step Away from the Tools
This may seem odd coming from someone who spent months coding a BDD tool, but seriously… put it down. Step away. BDD has taken off in the last few years, and lots of people have approached me…
lizkeogh.com
kuba.zalas.pl
Kuba @kuba.zalas.pl · Sep 8
"Start by having conversations, engaging both testers and business stakeholders or their proxies (analysts are good here). If you can’t have those conversations, stop."
Reposted by Kuba
jasongorman.bsky.social
You know what?

DON'T hire entry-level software developers.
DO use chatbots to generate as much of your code as possible.
DON'T bother investing in your dev teams and dev processes.
DO let their ability to comprehend code atrophy.

I've got my eye on a bigger house, you see.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 8
"There’s always more to build than we have time or resources to build—always."

If you somehow started to build 10x quicker, would you fire 9/10 of your developers or would you rather start building 10x more? 🤔
Reposted by Kuba
jessitron.bsky.social
Putting all your controllers in one directory and your views in another
Is like putting the cortisone and hemorrhoid cream in the drawer with toothpaste because they're all tubes.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 8
You need to turn around. Monitors are behind you!

Also, I can't stop giggling at "Full Snack Developer" 😂
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
- Your job isn’t to build more software faster: it’s to maximize the outcome and impact you get from what you choose to build.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
- Stories aren’t the requirements; they’re discussions about solving problems for our organization, our customers, and our users that lead to agreements on what to build.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
- Stories aren’t a written form of requirements; telling stories through collaboration with words and pictures is a mechanism that builds shared understanding.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
"There’s always more to build than we have time or resources to build—always."

"Minimize output, and maximize outcome and impact."

"Remember: at the end of the day, your job isn’t to get the requirements right—your job is to change the world."
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
"Good story conversations are about who and why, not just what."
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
Impact.

Impact is a longer-term consequence of good outcomes. Outcomes are often something you can observe right away after delivery. The impact takes longer.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
Output vs Outcome

Output is what happens between the idea and delivery. It's what we build. Output isn't the point, an outcome is. Outcome can be measured by looking at what people do differently to reach their goals as a consequence of what we've built.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
Documents.

"Good documents are like vacation photos"

"But, remember, what’s most important isn’t what’s written down—it’s what we remember when we read it. That’s the vacation photo factor."

"To help remember, photograph and shoot short videos of the results of your conversations."
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
User stories.

"The real goal of using stories is shared understanding."

"Stories in Agile development get their name from how they should be used, not what you write down. If you’re using stories in development and you’re not talking together using words and pictures, you’re doing it wrong."
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
Shared understanding.

"Shared documents aren’t shared understanding."

"Shared understanding is when we both understand what the other person is imagining and why."
kuba.zalas.pl
Kuba @kuba.zalas.pl · Aug 7
I re-read the introduction to "User Story Mapping" by Jeff Patton, and there are so many gems in this chapter alone.
kuba.zalas.pl
Kuba @kuba.zalas.pl · Jul 20
The Big OOPs: Anatomy of a thirty-five-year mistake is an excellent talk.

I love it when someone makes the effort to dig into the background of concepts instead of reinventing their own interpretations.

Those who don't learn the past are deemed to repeat it.

youtu.be/wo84LFzx5nI?...
Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025
YouTube video by Better Software Conference
youtu.be