“Thoughts” is (will be) a weekly roll-up of my mastodon feed with some notable thoughts collected into a long-form blog post. “Long form” is relative here, as I will only expand a little on some selected subjects, not write screens and screens of text on each of these subjects.
If you think I toot too much to follow, this is an alternative to follow some of my thoughts.
This week (2021-06-26– 2021-07-02) I thought about (finally) moving away from github and how tests can be, or rather should be, abstracted in code.
I am now on vacation for two weeks. That's actually the perfect time for deleting my github repositories.
With the introduction of Github Copilot, I had enough. That's why I will delete all my github repositories. I will continue to collaborate and maintain repositories I was invited to (namingly and most importantly config-rs and shiplift, but I will no longer host my own repositories on github.
Code duplication in tests
I recently thought about how much code duplication in tests is good or when it turns bad.
The reason for this is that I am developing a software for my employer (opensource) that needs more testing, but more testing would introduce more abstractions to write tests in less code, because there's quite some effort involved in getting the objects constructed the algorithms to be tested on need to have.
That's why I thought about that subject. I know that TDD would automatically yield code that is tested nicely and abstracted in a way so that there is no need for additional helper-code for tests, but TDD is not a topic here, because the code to be tested already exists.