data
jQAssistant extracts to structure of java applications and writes them into Neo4j, a native graph database. This blog shows how to use these tools to analyze java package dependencies. It follows up Analyze java dependencies with jQAssistant.
algorithm
When it comes to algorithms, performance is the first non functional requirement that comes into mind. Besides efficiency of the algorithm itself (complexity, branches, multiplications,…), there are a lot of things that can be done during implementation. Some optimizations might lead to higher code complexity, reduced readability and overall decreased maintainability. In this article we’ll take a different approach to implement the convolution algorithm in C/C++. It should be fast (enough) while being as maintainable as possible.
data
automation
Looking for new versions of libraries and updating them can be a tedious task, especially if you have to deal with multiple dependencies and many repositories. Renovate is a tool that can scan your dependencies and update them to the latest version. But can this also be utilized in a C++ project with CPM.cmake?
build
Continuous Integration [1] goes far beyond testing and building code nowadays. Test code coverage and other reports might get created, documentation might get updated and metrics and statistics might get refreshed. This article shows how these results can be pushed back into the repository using GitHub Actions [3].
data
jQAssistant extracts meta data of java applications and writes them into Neo4j, a native graph database. This blog shows how these tools can be used to analyze java jar dependencies e.g. for version updates.
build
Whereas there are numerous guidelines on how to setup specific tools like npm, combining all components to a build assembly line can be a tedious task. This article is intended to be a starting point, that gets you up and running with selected tools and references for vanilla JavaScript development. You can take it from there, exchange parts, add some more and dig into their configurations.
testing
One thing, that leads to many discussions, is how and if equals and hashCode methods should be tested.
Most of the time these methods get generated.
It doesn’t seem right to test generated code.
On the other hand, not testing these methods leads to poor test coverage statistics.
In rare cases, when these methods are not regenerated or edited manually,
they might cause bugs, that are very hard to find.
In this post, I’ll show you an effective way to test all equals and hashCode methods within one single test class.