blog.hongkongcoder.com

Java 9 was the first release making the JPMS available for general use. For many developers the impact of JPMS might not be clear, since its not a mandatory thing and the benefits are often overlooked. Why JPMS was desperately needed One might think - Java strict coupling of the package to filesystem structure allows to neatly organize the code. For dependency management of other packages/modules there are proven tools available like maven or gradle....

Gradle incremental builds allow for continuous testing, which is awesome. While appreciating a feature rich IDE, for continuous testing I prefer to keep it simple and run tests directly on the console: gradle test --continuous Continuous testing should answer below questions as quickly as possible Has something failed? Why has it failed? Having many tests in the continuous run is spilling out lots of unhelpful logs for tests that completed successfully....

Tools JQassistant How about you could scan your Java,C# code and create a graph representation describing all artifacts and their relations. You could then query about your own code metrics. This is what jqassistant.org is doing. It allows to create rules for projects in the format of Cypher queries. Cyper is the query language for the Neo4j backend. The website lists below use cases: Enforce naming conventions, e.g. EJBs, JPA entities, test classes, packages, Maven modules etc....

Visualizing software has always been a complicate matter. I haven’t seen it done effectively very often. Its a field with a myriad of individual opionions were you quickly get lost. The most prominent character in the field is UML(Unified Modeling Language). However, UML serves as tactical tools, which is useless without a visualization strategy. Speaking for myself UML has always been a love-hate relationship. In school I learned howto apply every singly type of UML diagram....

Monoliths cover multiple aspects of an organization and often show unregulated growth, commonly known as big-ball of mud. They are usually to big to benefit from a cloud deployment and certainly are not separating concerns. Scaling up individual parts as needed is difficult and developers facing a high cognitive load looking at a huge code base. A remote team structure usually struggles with conflicts. Breaking up such a monolith might be a real challenge since it is often the central application for data entry....