Another true principle of our craft is YAGNI - You ain’t gonna need it.
One of the key principles we devs violate way too often. We devs love complex systems too much.
For those unfamiliar with the acronym and principles. It stands for Keep it simple, stupid.
I am a firm believer that anyone should have a side-project. It does not matter if it is for pure learning purposes, fun or with the goal of making money.
Sometimes, we have to measure the execution time of certain code blocks. The traditional way would be to capture start and stop time with System.nanoTime() and print out the difference.
Works, but gets messy when you try to capture more than one time.
I bet your answer will be something like “yes, definitely, or are you crazy?”.
I’ve started helping out on a pretty old legacy system. It’s in its second decade and probably not far away from 20 years of existence. It went through many developer hands, everybody leaving its mark on it, myself included. There have been several attempts to reinvent it or at least parts of it, but none has been really successful so far. It is a mess, but it still works.
That’s the most common error when starting with Spring. Most of the time, it is an error made by us and Spring complains rightly. Sometimes, however, it is not one simple, stupid error caused by us. Reader Mark did have one of those rare exceptions last week.
Did you ever come across a piece of code and you though “wtf??? which idiot did write that junk?”.
Microservices are not the holy grail of software development as many devs and managers see them. They don’t solve all your problems at once, not even the tech ones. Yet, they follow a fad blindly again. Yesterday it was Agile and SOA, today it’s still microservices and cloud. Instead of solutions, many find themselves facing new problems; worse problems.
I published in a recent newsletter how I learn. Today, it’s moving from the secret labs to the open space.