Category: Craftsmanship

This is Part 6 of 7 part series inspired from the book Pragmatic Programmer, read Part 5 here: Use Exceptions for Exceptional Problems: Exceptions can suffer from all the readability and maintainability problems of classic spaghetti code. Reserve exceptions for exceptional things. Minimize Coupling Between Modules: Avoid coupling by writing “shy” code and applying the Law… Continue reading I am a Pragmatic Programmer Part 6

This is Part 5 of 7 part series inspired from the book Pragmatic Programmer, read Part 4 here: There Are No Final Decisions: No decision is cast in stone. Instead, consider each as being written in the sand at the beach, and plan for change. Prototype to Learn: Prototyping is a learning experience. Its value lies… Continue reading I am a Pragmatic Programmer Part 5

This is Part 4 of 7 part series inspired from the book Pragmatic Programmer, read Part 3 here: Don’t Use Manual Procedures: A shell script or batch file will execute the same instructions, in the same order, time after time. Coding Ain’t Done ‘Til All the Tests Run: ‘Nuff said. Test State Coverage, Not Code Coverage:… Continue reading I am a Pragmatic Programmer Part 4

This is Part 3 of 7 part series inspired from the book Pragmatic Programmer, read Part 2 here: Use Blackboards to Coordinate Workflow: Use blackboards to coordinate disparate facts and agents, while maintaining independence and isolation among participants. Estimate the Order of Your Algorithms: Get a feel for how long things are likely to take before… Continue reading I am a Pragmatic Programmer Part 3

This is Part 2 of 7 part series inspired from the book Pragmatic Programmer, read Part 1 here: Always Use Source Code Control: Source code control is a time machine for your work—you can go back. Don’t Panic When Debugging: Take a deep breath and THINK! about what could be causing the bug. Don’t Assume… Continue reading I am a Pragmatic Programmer Part 2

This is Part 1 of 7 part series inspired from the book Pragmatic Programmer: Care About Your Craft: Why spend your life developing software unless you care about doing it well? Provide Options, Don’t Make Lame Excuses: Instead of excuses, provide options. Don’t say it can’t be done; explain what can be done. Be a… Continue reading I am a Pragmatic Programmer Part 1

Some rules for functions: First rule for function is they are small. Second rule they are smaller than that. Lots of smaller function with better names will help you and your team because they will help you like a sign board and navigate you through your code. Don’t worry about function call overhead. It is… Continue reading Clean Code : Functions

Some rules for name: Choose your names thoughtfully. Communicate your intent. Avoid Disinformation. Pronounceable Names. Avoid Encodings (Eg: ucp) Choose parts of speech well. The Scope rules. For variable name with larger scope have larger name and variable name with smaller scope have smaller name. With method and class names it is opposite for method/class… Continue reading Clean Code : Names

During an project in Insurance domain, I faced a weird problem in the month of February. In our system every day the application runs a premium due date job which creates a list of insurance premium account with current premium value, to debit it from customer’s account. On the last date of February the application did… Continue reading Every one faces leap year issue

Email is an integral part of a developer, It’s a must to have tool to communicate to your customer, status report to leads, off shoring model etc. Below mentioned are few tactics that worked for me: When some one asks a question on email. Make sure you reply in stipulated time line. If you don’t… Continue reading Email know how for young developer