Category / Newsletter

    Loading posts...
  • Speaking into a microphone

    Work On Tuesday I did something new for the first time. And I feel like I failed miserably. I hosted a webinar. Back in the beginning of the year, I sent out…

  • Journaling

    I am writing again. Mostly for myself. As a journal. In the future I’ll try things a bit differently around here: I want to share what I am thinking about, how I…

  • Inspecting changes locally before pushing

    If you work on your branch you run into the situation that you would like to push your changes to the remote repository. CI will then pick up your changes and run the linting and code quality checks on it. Afterwards, you will see whether you improved the quality. But perhaps there are some new violations that crept into the code? Happens to all of us!

    I usually like to see and check if any new issues might come up on CI. This lets me improve them before I push.

  • Why you should use linters

    I don’t only publish these newsletters, I write articles on my website as well.

    Last week I published an article on “why you should use linters”.

    Wanted to let you know, just so you don’t miss this.

  • Avdi Grimm’s view on deleting tests

    A few weeks ago I wrote about deleting your tests. Yesterday I received the weekly email from Avdi Grimm, where he touches on this subject. Some premises about my relationship with unit…

  • External forces

    I am occupied with learning these days. Learning on my own about visualizations of data among other topics. But also learning about learning. For that I read what other people think about…

  • Complex conditionals

    The other day we dealt with code coverage and gnarly conditionals. I promised to offer a way to be able to test them properly. THERE IS NONE. Ha, what a bad joke.…

  • Code coverage can be misleading

    During the last week, I had two discussions about code coverage. Code coverage is the metric of how many lines of code are covered by your automated test suite. Many test frameworks…

  • Quick wins, part 2: Method names revisited

    Yesterday, we had the first part of this series on quick wins and simple steps to improve your code quality. It was about naming — specifically variables and method names. Two things…

  • Refactoring without a care

    Before I get to today’s topic, I would like to say thank you, to you. My little poem yesterday seemed to resonate with you. At first, I planned to write about it…