Let`s create something beautiful. -- That has been my approach to designing and writing software. I have been creating solutions on complex communication systems that handle millions of sessions per hour, billions of minutes a day. I wear several hats as a software developer, systems architect in crafting requirements for the entire solution, interfacing with the product management and customers to identify actual problems, solution architect for various features and so on. My attitude and approaches can be pointed as: Don`t just jump to solve the problem but understand the problem. Don`t speak to the problem with a solution but let the problem speak to you and then will come the solution. Don`t just create a solution for the problem but rather create something that can also handle the evolution of the problem itself. Let the software solution be as natural as possible, closer to the problem. Do not be concerned about who gets the credit for any solution but rather make sure the solution, if a good fit, makes it to the field. That is the credit. Introduce a mind-share of the solutions where all people who have participated get the understanding that all together made it happen. Don`t just settle with a solution. Always ponder over it but when it is time, recognize it and make a swift decision. Help others to understand the problem through questioning the problem and thereby enabling them to come up with fitting solutions. There are no bounds for one with imagination. There is always something beautiful behind a problem scenario. The question is, how much sincere, excited and committed am I in solving it. Also how much nerve do I have in doing things all the way from scratch when other similar systems exist but are not good enough. These thoughts (and others :) ) define the way I do things.
©