Java is twenty years old, or older, depending on who you ask and how you count. Despite its age, Java is still number one. Practicality, performance, and backward compatibility are all contributing factors.
Enjoy the paper here.
Thanks Simon Ritter !
This paper is about TDD, how convenient it can be in development cycle, Here we can see how TDD is not a technology instead of that this is a culture and good practice (discipline) that must to be encouraged for the project sponsors and the management people. Other important thing is how testability can contort the code because the code must to be tested and could be worse if you work with high code coverage.
Attention point of development performance, Usually with TDD it could be less than usual.
Very good point of view by Pete Preston. You can read all this paper here.
Is very important when we are refactoring or fixing bugs or doing some improvement to know who is the guy that created thi class.
Eclipse has a javadoc auto generator and it put the author automatically. The questions is that some times we want to update this author (normally Eclipse put it from current user machine). Here is the tip to get it according like we want.
We have two solutions (i recommend the second one):
1.- We can overwrite it passing the correct author in Eclipse shorcut as bellow.
eclipse.exe -vmargs -Duser.name=”Christian Oscar Tejada Pacheco”
2.- Se second way is editing the eclipse.ini and adding in the footer of the file the new line bellow.
-Duser.name=Christian Oscar Tejada Pacheco
In all of cases when eclipse will user the author, the name in user.name will be used.
How have some experience delivering projects can understand easiest this chart where honest payment worth it to get the final product with quality and in a short time. In the other hand, we can have low quality with cheap price or for free and fast, for example.
Let´s be honest, in TI nothing is really cheap without consequences.
After some months without creating new Eclipse project not using maven I had two problems and here I’m documenting that with the objective to do not more see this problem in front of me and trying to help someone with the same problem.
The first is when you build the project and the assembly doesn’t work fine, your deploy structure is not understood for the eclipse and as least one dependency is not found in runtime. You can try to resolve as follow:
Right click in project —> properties —> Deployment Assembly —> Add —> Java Build Path Entries —> Next —> select jar or library —> next —> finish.
The second is when you build a Spring MVC project in eclipse and and run it onto Servlet/jsp container and for some reason it doesn’t works. Maybe you need to check your spring configuration file and see if the follow ViewResolver are ok.
<value>/WEB-INF/[your jsp directory or just WEB-INF]</value>
This piece of xml set the viewresolver, it means, where and wich one extensions your view tier (jsp) will understand.
Very nice article for
In coming years, It will be no surprise to see it growing at a level in which software engineers will be using monolith for just prototyping. Who would not want to have a modular, highly performing and easy to scale application in the deployment in the time of Internet of Things?
The microservics architecture is not a new approach; its soul was always there for years in the form of SOA (Service Oriented Architecture), web services, and in a modular and layered architecture.
You can see all post from Kumar here, enjoy!