-
Core Java
Many parameters and lost information
The less code, the better? The fewer objects, the better? Is it true? As usual, it depends. There are cases…
Read More » -
Core Java
Conjunctions we… hate
Recently I’ve written about implementation-related names and I’ve presented a few examples where the method name was incorrect because of…
Read More » -
Software Development
The name should express the intention
This time I will start with a code sample. Take a look at this: if (code.isComplexOrUnreadable()) { refactor(code); } Can…
Read More » -
Software Development
Should you follow the rules?
In the last article I wrote that I’m a big fan of tools for static analysis. Those tools help you follow…
Read More » -
Software Development
Code Review and Single Responsibility Principle
According to the Single Responsibility Principle each unit in our code should have only one reason to change. Code Review, on the…
Read More » -
Software Development
First for test, second for implementation!
Test-Driven Development is a great technique, isn’t it? Today I want to propose you an experiment that may help you…
Read More » -
Enterprise Java
@Autowired all the things!
Recently I have written that @Autowired annotation make our lives easier in that it allows us to write less code.…
Read More » -
Core Java
@Autowired and optional dependencies
@Autowired annotation makes our lives easier. It also can result in decreased amount of code if we are using it…
Read More » -
Core Java
Constructor or setter?
It goes without saying that every object needs to be created before it can be used. It does not matter…
Read More »
