Getting real chapter 12

This chapter basically tackled about product launching. Before we could actually launch our product, there are so many things to be done. You have to promote it, giving freebies, product testings, advertise it etc. But even though you do these things, there is just 1 thing that is important, you have to sell your product so that you could earn profit. You should make your product easy to use and cost effective so that you could earn a lot or you could lose a little. It’s like gambling when you launch a product, you don’t know if people would buy it or not.

Avoiding long term contract is important because of the pressure it brings. It’s a trap that is hard to go away. Giving contracts like maintainance or warranties should have a limit. If you give longer warranty, the more cost you could get. Just give enough warranty but make sure that it is legal. Raising prices should be advice in advance so that your customers wouldn’t be shock.

So this chapter tackles about product launching and how you will deal with it.

My Exercise 8 ajaxcontact form

http://jaythree03.site90.com/ajaxcontact/

Getting real chapter 11

before doing the project, while doing the project and after the project, you should document it. It is required for every project for different purposes. I personally don’t love doing paper works but it is important so that you know what you’ve done so far and you know what are the things undone. It is also important for the side of the client so that he or she knows the progress of the project. This chapter states that we should avoid unnecessary paperworks. We should just start doing paper works when the things you want to write in the paper would be reality.

Being to technical would make your customer mad. Maybe they couldn’t understand everything that you put in your documents because they don’t know some technical terms. When writing documents, avoid technical stuffs. Just write simple words as if your just writing something in your diary.

Getting Real chapter 10

As the previous chapter deals with the physical appearance of the application,  this once deals with the soul of every application which is the codes. In our religion, we believe that a human’s body consists of 2 parts: the body and the soul. The soul is the one responsible for the emotions, thinkings, beliefs, etc. it commands our body to do what we want to do. Let’s go back to our topic. We all know that the codes make our application runs. It helps us to control our application the things we want it to be. If you want to add some functions in our application, you can code it. If you want to add some fun, you can code it.

Another important thing that I’ve seen in this chapter is that, I should make the codes simple. Why? because time will come that you have to update your application, if it’s complicated, you could have a hard time updating it. We should also choose the right tools that will suit to your skills. There are varieties of development tools to choose form. It’s just that you have to choose what best suit to you and do your best to master it. But make sure that you can still study other languages so that you can be competitive. Industry standards must also take into consideration. Example, if a company uses unix based programs, you should not use .net technologies because it will not work on a unix flatform.

Be competitive, analyze and listen to your code. It can help you work faster.

Getting Real chapter 9

This chapter is all about the project. We all know that the project consists of many parts: User Interface, the codes, etc. but this one explains us about the User Interface. Why is it that User Interface is important in a project? As we all know, U.I. is the physical appearance of an application. Without the appearance, the body will not be completed. People, especially our users often look at the U.I., without the ellegance, the beauty, the user experience of an application, the users won’t like it.

Before the codes which is the soul of an application, the first thing that we have to do is to design our application. I remember just a while ago, We design first our application before we do the coding. I’ve seen the differences. Actually before, I just do some design, and then start coding, do additional design, and start coding again. I’ve notice that it makes my coding time long. Now, I’ve realize that I really have to design first before I start coding.

When designing, there are still hindrances. The system hangs, wrong U.I design, errors in some areas, etc. But we should still have to take the necessary actions in order to have better designs. Use the technology. Be creative. That makes the difference.

my own generator

you can view the site here

Sir, I’ve posted the updated links.

my fancybox

you can see it here

my css garden edited

 my customized css zen garden here

my CSS Zen Garden

you can find the link here

my generator

http://jaythree03.site90.com/generator/

Sir this is the updated link.