Things I Learnt The Hard Way - Disclaimer

There is one magical thing you need to know when reading this book: It's all personal opinion

Read more...

Things I Learnt The Hard Way - Gherkin Is Your Friend to Understand Expectations

Gherkin is file format for writing behaviour tests (BDD). But it can also give you some insights on what you should do.

Read more...

Things I Learnt The Hard Way - Unit Tests Are Good, Integration Tests Are Gooder

The view of the whole is greater than the sum of its parts. And that includes tests for the whole compared to tests of single things.

Read more...

Things I Learnt The Hard Way - Tests Make Better APIs

Testing things in isolation may give a better view of your APIs.

Read more...

Things I Learnt The Hard Way - Make Tests That You Know How To Run on the Command line

You know that "Play" with a little something on your IDE that runs only the tests? Do you know what it does?

Read more...

Things I Learnt The Hard Way - Be Ready To Throw Your Code Away

A lot of people, when they start with TDD, get annoyed when you say that you may have to rewrite a lot of stuff, including whatever your already wrote.

Read more...

Things I Learnt The Hard Way - Intro

"Things I Learnt The Hard Way (In 30 Years of Software Development)" started as a simple sequence of toots (the same as "tweets", on Mastodon when I was thinking about a new presentation I could do.

But why "a new presentation"?

Read more...

Things I Learnt The Hard Way - Spec First, Then Code

"Without requirements or design, programming is the art of adding bugs to an empty text file." -- Louis Srygley

Read more...

Things I Learnt The Hard Way - Write Steps as Comments

Don't know how to solve your problem? Write the steps as comments in your code.

Read more...

Things I Learnt The Hard Way - The... Book?

Random thought about the previous post about "Things I Learnt The Hard Way".

Read more...