All posts by Grzegorz Ziemoński

Pair Programming Essentials

It appears to me that Pair Programming is, next to TDD, one of the most controversial of XP practices. It also appears to me that most people criticising Pair Programming have never done it or, if they

Continue reading

Let It Go!

I sat today morning in front of my computer, opened KanbanFlow and started planning out my day. First thing on the list? Enable previewing the posts, so that my wife or my friend Darek can review my latest

Continue reading

Reusable Components in Java

I can’t name exact sources, but I feel like ever since I started learning how to program, I was reading tales and legends about “reusable” components, modules and so on. It was not until

Continue reading

Refactoring to Components

Imagine you’re assigned to work with an old codebase without a reasonable component structure or any structure at all. A big ball of mud! What now?! How do you get from there to nice, reusable components

Continue reading

Java Encapsulation For Adults

For proper understanding of this article I’d like you to close your eyes and imagine something. But since having closed eyes and reading at the same time is not an option, we’ll skip the “close

Continue reading

Three Modes of TDD

Among the discomfort of being sick over the weekend, I also had the pleasure to do some reading – Kent Beck’s TDD by Example in this case: I’m not even sure if that’s a valid square,

Continue reading

Small Things Matter

Hey boy, are you doing microservices? Sure you are. Everybody does. Have you moved to 4-tier architecture already? Are your applications cloud-native? Have you containero-dockerized yourself? All of it?

Continue reading

SLAP Your Methods and Don’t Make Me Think!

In my recent post about creating a blogging platform I posted a piece of code like this: public MarkdownPost(Resource resource)

Continue reading

Package Structure

Packaging is one of the underrated features of Java. We use common sense to put things here and there, after some time everybody knows where certain things go and nobody cares any more. Well, as long as

Continue reading

To Interface or Not To Interface

How do you decide if a class should be hidden behind an interface or not? What has to happen to make you think “Oh, I should create an interface here”? Quick googling and we land on a StackOverflow

Continue reading