Thoughts on solving a programing problem & building software

1. The code does not behave arbitrarily – The problems in logic that make the code behave arbitrarily 2. Don’t give up and say a solution is wrong – look for the remaining part of the solution to make it right. 3. Always learn to pay respect to the professional work done by others 4. Always treat yourself as a learner – lowest guy in the totem pole – enables you to look at code with enthusiasm and an attitude to learn/understand. 5. Always try to find the simplest and most durable of the solutions that solves the given problem – you are not in the software engineering world to create complexity – it is the other way around. We are here to simplify. (We need to learn to balance simplicity and complexity). The simplicity is prioritized. The Simplicity should be for the user (User should be able to very easily & quickly perform intended work, reliably each time). 6. Each computer system is built with some key primary quality attributes in focus. All other attributes are secondary. The architect’s job is to decide which are primary and which are secondary. He/She should then build a system that is able to realize this goal.