Skip to main content

Posts

Showing posts with the label development

Be A Good Developer - Introduction

After many years of coding, debugging, designing and improving applications I came to this point that being a good developer is the key for an application as well as the development team to success. As for an application, good developers make it less problematic and easy to maintain as for the development team, they help others to learn efficient code. This helps to reduce the cost of application maintenance as well as the time of getting new developers up to speed. Many have got this wrong impression that a good developer knows more about design patterns and knows how/when to use them. But that's not the case. In fact, a lot of developers with a good knowledge of OOP and design patterns end up in overengineering the application. No matter what framework or solution you are using, a good developer still worths a million! They are the real assets of a software company or a development team. Now the question is who is a good developer and what makes them so special? Plea...

Unit Tests - Why are they so important?

Why do we need Unit Testing? There are two important reason : To test different scenarios and making sure the logic we have just written works as expected In case a developer is changing the logic in future, they notice whether they have broken the existing logic or not What Should Be Tested? Different scenarios: E.g. each if-else statement can be taken as a separate scenario Data that we expect to be changed within a method Possible exceptions that may be thrown What Does Not Need to Be Tested? Mocked data that we created as input data Any result from a third party API. E.g: Hibernate, Spring etc. Results from classes that are already tested in their own unit tests. Example public Employer save(Employer employer) { if (employer.getActivateFlag() != null ) { if (employer.getActivateFlag()) { employer.setStatus(Status.Active); } else { employer.setStatus(Status.Inactive); } ...

JSF or GWT?

I have worked with JSF for almost 4 years. First time when I had a chance to work with GWT, I was very excited. Like many Java developers I was like 'Wow I don't need to play with those bloody tags and elements and now it's pure Java code!!!'... I was so happy but my happiness didn't last very long. Programming is my passion. I hate writing codes that become a mess later and unfortunately this is what will eventually happen with GWT. The thing is you can't rely on reviews and features of a software or an API, in action everything goes different way. Specially when it comes to large scaled application and in an environement where everything is urgent and importnat... well, I think all software companies are the same in this regard... The fact is that in a team of developers not every one cares about best practices, design patterns and even if you have very experienced designer, solution architect etc, still you can't force the team to deve...