What I learned in Software Life... Find Solutions!

In my previous post What I learned in Software Life... Develop yourself! I talked about developing yourself in order to find better solutions.

It is only imperative, that our job is to find solutions to customer's problems. That is the primemost reason why customer goes out and seeks help.

Good design can deliver miracles.

This is true for any field. Be it Engineering, software, Medicine... what ever. Creating a good design is definitely a challenging job. It is a bridge between 'requirements' that are only stated and 'implementation' that realizes the solution. Any flaw in design will always show up at some stage or other.

Practical ideas make more sense in business world.

There is a distinct difference between Scientist's world of perfection and idealism and Engineer's world of realization of solutions with available resources. To be able to deliver in given resources which are always limited, tools, processes and competency become essential. Having a practical idea to solve a seemingly complex technical problem, always finds real solutions.

Code is the last point to instruct computer. 

This is the key fact many of us forget. You cannot do much after code is baked into binaries and delivered. Settings and configurations cannot alter much of the behavoir. They only choose a route already coded. One has to have a feeling of 'this code will never come back' attitude while coding.

If customer reports a defect, THERE IS A DEFECT! 

People argue with customers on how a behavior is not a defect. But mind you, if customer is reporting a defect there IS one. The cause may be any thing; a bug in software, customers understanding of new system, lack of documentation, undocumented work around, hardware problems, or even out-of-scope case. Instead of arguing with customer, if you find a route cause and provide logical explanation, customer will agree more than you think!