Shannonangto’s Weblog

Chapter 6

Getting real is to make the real thing running. Everything that you do is nothing if you cannot deliver running program to your client. So, if you can minimize the features of the applications to make it run do it. Don’t expect to have a perfect application in the launch period but rather you can perfect it on the iteration stage.

First thing that you do is to brainstorm and sketch it on a paper so that you would not forget you ideas. After sketching you can already create the HTML and code it after. Know all the things that your customer wants and decide what the important things that are really needed are.

Remember that decision is nothing without action that’s what I’ve learned in this chapter. After coding it let your application be use by the people who will use it because in that way you will see the improvements that you need to do. Remember to breakdown your project time so that you would finish it earlier.

Chapter 5

Building a web application first you should think what are the essential things that it need to make it work and will make the users impress about it. You don’t need to build an application that has many functions but you cannot finish it on time. Building an application means figuring out what are the matters the most in the application and not building an application that has full of functions/features.

Being a developer means we need to practice to say no to our client because if don’t we are building a application that we might not finish. To say no to all non-necessary feature means that you are giving yourself and your client a great application. If the request keeps coming back to you then it is time for you to make that feature.

Before building a feature in an application you should consider and analyze deeper because if you do you see different cost that it might occur in building that feature drop it. If you do a feature on an application and you launch it, it should do what you said to your client it should do. If you said something to your client you should do it or else your reputation will be ruined.

Build an application that can do general problems of the people using it because if you do they can use it to solve their specific problems. Building an application will be always means of the functionality that your client wants but you should say to them no if it is not necessary. Remember only the important things what your client wants because it will come up every now and then. Remember also that no matter how many people said they wanted that feature you are still not obligated to do that feature.

The most important thing that I learned in this chapter is for you to figure out what your client does not like in his/her application is much important than knowing what his/her want in the application.