Programming standards
Java
Style, Maven/Gradle, Spring, exceptions, tests and clean code.
- 0110 minStyle and conventions (Google/Sun style)intro
Naming, formatting and automatic Java style in the ProfessNet standard.
- 0211 minMaven vs Gradle — buildingcore
A comparison of Maven and Gradle, build structure and dependency management at ProfessNet.
- 0313 minSpring Boot — fundamentalscore
Controllers, dependency injection, layers and configuration in Spring Boot per ProfessNet.
- 0411 minExceptions and logging (SLF4J)core
Exception handling, a hierarchy of custom exceptions and logging via SLF4J at ProfessNet.
- 0512 minJUnit 5 + Mockito testscore
Unit testing in Java: JUnit 5, Mockito, AssertJ and Spring Boot tests.
- 0613 minClean code and SOLIDadvanced
The five SOLID principles and clean-code practices illustrated with Java examples.
Check your knowledge — quiz
5 questions · pass mark 80%. Score saved locally.
1.Following Google Java Style and the ProfessNet standard, how do we name an interface and a constant in Java?
2.Which build tool will ProfessNet choose for a simple, typical service, and which for a large, multi-module monorepo?
3.Why in Spring Boot do we prefer constructor injection over field injection with @Autowired on fields?
4.Which way of logging through SLF4J is correct and efficient?
5.Under the Liskov Substitution principle, what does it mean when a subclass must throw UnsupportedOperationException from a base method?