Posts

Showing posts with the label beginner tips

Code Design - Choosing Abstract or Interface - Level 100

More often we wont get a chance to work on these aspects in early stage of your career. Even at the time of mid career getting a work related to API designing/Development is bit difficult. Unless you have a very good mentor in your initial career you will never get to know the real time. And you will end up in theoretical knowledge if you are computers academics. Others need to witness nightmares :-) Always try to implement good design in your day to day work. Never try to concentrate on these concepts for the matter of career growth. Only the passion to write a good code lets you to remember things. Design patterns are not meant for only senior programmers. You need to have a little bit knowledge on nitty-gritty of OOP/OOD concepts. And I need to say that continuous practice only lets you to excel further in OOP/OOD concepts irrespective of your experience levels. Here are some basic recommendations to help you to decide whether to use an interface or an abstract class to provid...

Part– II : Coding standards

These are the main checklist I used to follow in day to day code development and maintenance. Hope this might help some of you new people. If there is any mistakes/typo please do not hesitate to comment. Coz these are my personal views and opinions 1. Need to avoid unnecessary comments especially while releasing a build 2. Reduce as much lines of code as possible 3. if a variable is used only once then declare it locally if possible 4. Follow the naming conventions especially in DB layer. This helps a lot I promise :) 5. Method name should tell what it does. Do not use miss-leading names. If the method name is obvious, there is no need of documentation explaining what the method does 6. Make a note or summary at top of the page if the code was developed my multiple persons. it helps to track when and which kind of development started 7. Make sure that the required input values gets logged while logging the error message in catch block 8. Avoid ...

Part– I : Coding standards

Coding practise defines the developer awareness of writing a good code. but not his technical expertise..... I mean a little :) As of my experience with different projects across the domains and technologies & tools I got  a chance to work on enhancements, bug fixings, code reviewing, code development from the scratch level, enhancing my own code which was written years back by myself  :) , reading and preparing documentation on reviewing the code base from the client..... and many more. I got realised few points which i would like to blog.