Skip to main content

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?

Please read "Be A Good Developer - Part 1"
Labels:

Comments

Post a Comment

Popular posts from this blog

CI/CD Automation: How to wait for Helm deployment into Kubernetes cluster

 So I created this post because with Helm v3 , if you use --wait option and the timeout is reached and the deployment isn't successful, Helm marks the deployment as failed . The problem is that subsequent deployment (upgrade) that may contain the fix won't work as expected and it will end up in error like this: [some-name] has no deployed release   The only way to fix this is manual intervene and deleting the previous failed release. This is not only scary but also against the automation process. If we remove --wait option, Helm will mark the deployment as successful regardless. My solution to this that works nicely is as per below: Remove --wait option from helm deploy Use this command to retrieve the list of deployment for that namespace that you are deploying against: kubectl get deployments -n ${namespace} -o jsonpath='{range .items[*].metadata}{.name}{","}{end}' You can use split to turn the comma separated list above into an array Then you can run mul...
Post a Comment
Read more

Hibernate And Mapping enum to customized values

With Hibernate, enums can be easily mapped either by enum item name or the position of each item but what if you want to map it to a customized value? In my case, we have so many one-character long columns in our tables, representing flags, statuses etc. We have heaps of them. Writing UserTypes for each enum field is very boring and nasty job. As every where you see in internet, you need to keep a Map for each user-type in order to map those values to enum elements. So to avoid this, I ended up with something more clean, easy and more generic. Now imagine you have following enum: public enum PaymentFrequencyEnum { WEEKLY("WK"), FORTNIGHTLY("FN"), MONTHLY("MT"), QUARTERLY("QL"), YEARLY("YL"); private String value;     private PaymentFrequency(String value) { this.value = value; } } I've chosen two-letter code as value so that you understand m...
2 comments
Read more

Migrating from OJB to Hibernate

Okay now I have to migrate a dozen of domain objects from OJB to Hibernate entities and since we still have to use hbm files as opposed to Annotation, this is no enjoying task... I found this XML Stylesheet from this website below but had to make some changes in order to get it working... so I thought it may help someone: Download XSL file here Original file can be found here but so far at this time which is 16th of December 2013 and 6:37pm, it's not working properly :) martindavidsson blog
Post a Comment
Read more