Tests should help you release code faster and with confidence. Yet, for many developers, testing has the opposite effect, creating delays and frustration. Here, I’ll explore common pitfalls in testing and suggest better practices to make tests truly beneficial.

We have all heard that we need to have more tests and that we should have as close to 100% tests coverage as possible. Despite this effort, we still encounter bugs. We still do manual testing and overall a lot of developers do not trust their tests to actually catch anything useful. Why is that?

In this post, I’ll explore the SuperH instruction set and its relevance today, along with a tool I created to navigate it.

A few years ago, I met some of the members of the team behind the development of the J-Core, a SuperH clone, and had some really interesting discussions with them. Using this resource, I created, for my own understanding, a JSON file and the dynamic table below to help me navigate and understand the SuperH instruction set. I also added J2-related instructions that were not present in the initial material. As I turn off my AWS account, I realized I could just share it via a GitHub page. Here is a bit more context about SuperH.