About

Agile development, refactoring, automated self-testing and continuous integration/deployment have changed the way application development is done during the past years (or already decades).

Unfortunately, I see large parts of the database development community stuck behind those changes – and I don’t think that’s a good thing.

Challenging myself to improve my database development I will write down my experiences and try to share what I learned and thought about as part of my personal reflection.

Join me on my journey!

Author

My name is Samuel “pesse” Nitsche, I am husband, father of two amazing kids and a passionate software developer.

I started programming around 20 years ago, but it took me some time until I found my love for pragmatic, clean programming – normally in object-oriented programming languages like Java, but recently also in PL/SQL and TSQL.

I take care for the java-API and CLI of the great utPLSQL unit-testing framework for PL/SQL since autumn 2017.

Since 2019 I’m also an Oracle ACE (which is an award for community activity and sharing knowledge) and listed in the directory of Oracle Groundbreakers.

I speak at conferences and local meetups, mainly about automated self-testing, PL/SQL and compassionate coding.

If you’re interested to have me for your meetup, just reach out.

From Clean to Compassionate

When I started my blog I was fascinated by the principles and strong guidelines of Clean Code, a pretty famous book by Robert C. Martin but even more a term for a specific mindset focused on software quality and craftspeopleship.

During my journey, I noticed that “Clean Code” also bears a lot of dogmatism and several practices (or the way they are taught) reinforce elitism and gatekeeping – something I can absolutely not identify myself with.

I, therefore, searched for a theme which better describes my values and principles and found it in the term “Compassionate Coding”, defined by April Wensel.
Its main idea is to reduce suffering for everyone included in the process of developing and using software.

This fundamentally includes all the principles of Clean Code, which is mainly focused on reducing the suffering of maintaining code (by making it easier) and using software (by making it higher quality), but with a more human, more empathetic and less “right-or-wrong” intention.