Thanks for your comment.

Yes, I didn’t touch the testing code topic, and it was deliberate as I mentioned in the first paragraph:

I don’t think that writing tests or specifying behavior upfront always a good thing for all kinds of projects.

In my personal opinion, writing testable code is way more important than writing tests in first place. In all the years I’ve been developing in several different platforms, I found that decoupling your code, and thinking on how you can test a piece of code either by TDD or an interactive shell is not something most developers, even experienced ones, do.

Testable code is a state of mind. When you achieve it, doesn’t matter if you’re actually testing it. It matters that you can test when you need.

The fact that you can change a table/file name on request is all nice and dandy while developing, but it doesn’t help you anywhere writing / maintaining tests.

That’s happening, one step at a time.

At the beginning, I thought I didn’t have any achievements, both professional and personal.

We think achievements as big or revolutionary things. In fact they aren’t. Every small thing you do, every decision you make is an achievement you can be proud of.

Changing my perspective on what achievements are, I realized that I have a handful of achievements every day, but treating those small actions and decisions as achievements is the most difficult part for me until now.

But nothing I can’t change with time.

So, I can say the very next step is start keeping a journal containing all my personal achievements, big or small, so I can refer later on and find encouragement to keep going.

Thanks for asking!

How’s that getting along?