

They may still study at the university or not even born.

And we do not know them as they are not even selected. The reason is that the code has to be maintained by the developers who come after us. They told me to scrap the code I wrote, and keep creating the toMap() and fromMap() manually.

They were created and maintained manually. Before that, we had toMap() and fromMap() methods in all classes that needed this functionality. What I created was a single class that was doing some reflection “magic” converting objects to maps and back. (It does not stop though some of them trying even in a professional environment, which is contradictory as it is not professional.) You need a team. Not really a framework, like Spring or Hibernate because a single developer cannot develop anything like that. Solving a problem I created a mini-framework.

It may happen to you what has happened to me a few years back. They are not bad either, but they, as the name suggests, are average. And, there is a very specific feature of the average developers: they are not good. However, when you write a code you should also consider the average developer Joe or Jane, who will some time in the future maintain your program. You are well above the average developer last but not least because you are open and interested in new things proven by the fact that you are reading this article. When I talk about the “sub-par developer” I do not mean You.
