Getting Real (Chapter 7)
Chapter 7
When doing a project you should not break it down into different groups but rather make it in a whole because if you don’t the project will become more complicated to finish. Rather than breaking the project down into smaller groups you should hire an employee who has multiple expertise so that he can mange the different groups while making the project.
Remember that give some space to every person in the group to have their own time and finish their task on their own. Giving time and space is important it builds the mental peacefulness and the person can recuperate from working too hard.
Having meetings is such a waste of time that’s what I had learned from this chapter. Instead of having a meeting you should explain and discuss the things to be done via email, im, or campfire and make it simple so that everyone can understand it easily. A meeting is a waste of time because you can already accomplish something during that time.
The most important thing that I had learned in this chapter is to give motivation to your worker. Giving celebrations in between the project is a good way to motivate your employee and that’s a good thing.
Site90.com (csszengarden)
Please, see my site that I’d got from csszengarden.com by clicking this link.
Getting Real (Chapter 6)
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.
Getting Real (Chapter 5)
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.
Getting Real (Chapter 4)
Chapter 4
Chapter 4 begins with telling us that what we need to think about the purpose of our application and we should see the big picture of it because it will guide us to finish our application on track. This chapter also tells us to make first the functions of the application and don’t worry about the details in the beginning of the project because if you do you will have a hard time finishing your project.
We should think first what we have and we are capable doing today instead of thinking already the next year’s impact of your software. It is necessary to think now than tomorrow because you cannot have what you can have tomorrow today. You don’t have to think the problem of the future but rather work with your problem today.
We should also find our target market because if we do, we can easily determine what is our application is all about. Finding your target market now a days is easier with the use of the Internet.
Scaling is what is important when you are beginner and a starting group in creating application. If you have a small scale you have less problems that you will encounter. Like what I have said earlier think about now don’t think about tomorrow because you cannot have tomorrow today.
In making software you cannot please all the people and have their entire request in your application. If you want your software to be successful you should have a vision if that vision doesn’t agree other person’s vision then find another person that will agree with your vision.
Getting Real (Chapter 3)
Chapter 3
In building software, I learned that you should build the features that are really needed while put on the other add-ons features later. If a programmer or a team tried to fit in a lot of a features in one software the tendency is that it will take a long time to finish and it will be costly, While, in having less features the programmer/s or team can adjust/change quicker and deliver the demands of the customer in earlier time and this also mean less cost to the customer and effort to the programmer/s or team. If a company has a fast phase in improving or creating software this means that they are efficient not only in time buy also in their cost and this is an advantage in a business.
Less mass also applies on having a small team. Based on what I had read it is better to start in a small team because you can communicate well about the project and the team members will be force to work hard on the project to finish and deliver it on time. A small team can only be effective and efficient if the team members are competent enough to do the job.
Based on what I had read this quotation bothered me “Constraints are often advantages in disguise” at first my opinion about this statement was that what the hell constraints are usually the one that makes the project hard because you obligated to follow it. When I thought about it deeper I realized that having constraints will give you ideas on how will you solve the problems that was given to you and if you know what were the solutions to your problems it will be now easy.
I learned in this chapter that having a small company has also an advantage against the huge companies. The advantages of the small companies is that they can deliver quicker to the client so if they deliver quicker the clients will response quicker and this will give the programmer/s more time to improve their product. Having a small company will also give the team freedom in communicating with each other not like in the big companies they have procedures that they need follow. Having good communication in a clearer and faster phase is an advantage to the small companies.
2nd term easy or not???
Kala namin walk in the park lang itong 2nd term kasi naman yung first day sobrang bait ng ibang professor namin. Sa sobrang bait kala namin ok na pero hindi pala.
During the second day dun na nag simula ang tunay n hirap. Hay sana kayanin namin ito.
Good Luck! sa atin lahat.
Getting Real (Chapters 1-2)
“Every once in a while, a book comes out of left field that changes just about everything. This is one of those books. Ignore it at your peril.”
-Seth Godin
Getting Real is a technique in making applications based on the customers/users needs, ideas, and how they will use it.
As I read through the text I learned that getting real is used to make the web application building easier. In what I have read people that have already experienced using this technique had an easier time in their projects. The 37signals had developed different application for different task, so this is an advantage for us the users.
From what I had read the 37signals built their applications based on how the users usually used an application that they can easily navigate. Their methods have many advantages like in cost, time, customer relations and etc.
Getting Real is about giving the customers what they want in a faster phase while at the same time getting feedback’s from your customers about your product to improve your product and give them the updates through the web/net.
I also learned that in the planning stage details should not be given all at once because in the developing stage you can reveal things that you need to know about the project. I think that this is true because based on my experiences the more detailed you are in the beginning of any project the more problems that you will have because you will have more constraints in making the project.
Getting Real is creating while thinking other people. Creating while thinking other people because you create programs not only for your self but also for others.
Having Big and Costly software team is a gamble instead we should ask our selves if we use less people in the project could they accomplish things that many people can.
I learned that having a fix time and budget is not the problem but it is your scope. If you need to adjust then adjust your scope make it smaller. Ask first your self which is your priority in making the software and put other needs after you have launch the software. If you are starting on a new software you shouldn’t go after what your competitors have but rather what your user needs and wants.
The most important thing that I’ve learned in this article is that give passion to whatever application that you will do because your application will represent you.
Shopify.com
Are you looking for a new mac gadget???
Look no more here at my shopify site you can see the latest mac gadgets.
Here you will see the new iPod nano and iPod touch and other mp3 players of apple.
Are you looking for a new laptop?
Here you can also choose from different laptops that apple has to offer. (MacBook, MacBook Pro, MacBook Air)
Hope that my shopify site will satisfy your needs.
Please, take a look at my shopify site: http://gadgetsplace.myshopify.com
shannon