gettingreal (cont.2)

CHAPTER 4

To summarize it all, basically the chapter tackles the basic steps (such as requirements and needs) in building your first program in web applications. For the past chapters the site have focused with all of the foundation you must know and much better possess as early for that time, prior for building your own web app. But then, chapter 4 I must say it really the starting line to such particular project, thus you will apply here all of your insights that you have gained within the previous chapters. By the way, parts of the chapter including your objectives, “piece by piece” tasks following the pattern of a “cone shaped” (meaning start from a general down to specifics) system of implementing your actions and analyzing things. Also included in the list is of course, identifying your problem, therefore somethings this may be the success and failure, if ever of your project because if you did come up with a wrong point of defining what is the general purpose of doing your program you have a high risk to be engaged of having hard time in accomplishing the entire application. Making and hiring your “suited” customers as well will help in a lot of ways because in this stage, you are able to distinguish what is it that your customers needs and wants up against what is it that he/she don’t need or of a minimal help with his requested program/project. By this time, you have already stated your target market. Just a reminder that the statement (especially referring to the filipino market we have) that “Customers are always right” is a big mistake to stick unto (you know why?) because every individual have his/her own needs and wants, therefore what you have created is not that relatively the same as with the perception of customer A and customer B, but then customers to intend to abuse their as such so better choose your customers of if you can’t they make it a point to have a alternative option to compensate for his/her wants. Next stop, is to address some recurring problems that could happen just like for example system or website is done because many clients and users are accessing the site, for these kinds of problems don’t you worry and bother that much because always remember that there is always a time to change and address those issues and believe that you can pass it through, be optimistic in fixing such problems! Lastly, the last section of the chapter would discuss about your set up of your some kind of a “vision mission” of your software. It was mentioned that a single consistent vision can really help you to build a better software because you have a path to pattern and follow to.