We are living in an era in which information is freely available. Whatever may be the area, whatever may be the subject, you get the answer in a second. The trend in problem solving nowadays is to figure out where to find the information rather than building an application from scratch. We want to solve the problem quickly rather than proving our technical expertise, when it comes to pure problem solving. We need to sacrifice our personal ambitions while trying to solve problems. Searching for an information not only requires special skills but also sufficient training in handling the information source, say the Internet.
Once given with a problem, the first thing to look for is the essential steps required to solve the problem. The second one will be look for the tools to implement them. The next step would be not to start working with the application but rather looking for an already existing tool. This not only saves us time, but gives us a confidence that the problem is half solved. Later, try to modify the tool according to your application, which is possible in most of the open source tools. This is the basic principle used with the Object Oriented System Design Methodology to write softwares.
There is yet another crisis with this Object Oriented Systems Methodology. When programmers use an already existing object in their application, their Manager often questions their skill sets!! Because, he feels that they don't have a brain of their own! This problem is somewhat difficult to tackle, because it deals with the psychology of the Manager. The programmer needs to convince his Manager of his skill and expertise. So, a sufficient trade off is required between using an existing object and writing your own applications and a clever programmer always find the fine thread connecting these two.
Once given with a problem, the first thing to look for is the essential steps required to solve the problem. The second one will be look for the tools to implement them. The next step would be not to start working with the application but rather looking for an already existing tool. This not only saves us time, but gives us a confidence that the problem is half solved. Later, try to modify the tool according to your application, which is possible in most of the open source tools. This is the basic principle used with the Object Oriented System Design Methodology to write softwares.
There is yet another crisis with this Object Oriented Systems Methodology. When programmers use an already existing object in their application, their Manager often questions their skill sets!! Because, he feels that they don't have a brain of their own! This problem is somewhat difficult to tackle, because it deals with the psychology of the Manager. The programmer needs to convince his Manager of his skill and expertise. So, a sufficient trade off is required between using an existing object and writing your own applications and a clever programmer always find the fine thread connecting these two.