I am a Pragmatic Programmer Part 6

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

I am a Pragmatic Programmer Part 3

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

Clean Code : Functions

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

Clean Code : Names

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