Getting Real – Chapter 6

September 25, 2008

Here’s the summary of what Chapter 6 is all about:

Race to Running Software – Get something real up and running quickly

Rinse and Repeat – Work in iterations

From Idea to Implementation – Go from brainstorm to sketches to HTML to coding

Avoid Preferences – Decide the little details so your customers don’t have to

“Done!” – Decisions are temporary so make the call and move on

Test in the Wild – Test your app via real world usage

Shrink Your Time – Break it down

The author explained that your software must operational – your first priority. Omit features that isn’t your main concern. The more accurate your application, the better. It is the finest way to complete your task in hand, avoiding any issues within clients, thus creating a good relationship with them.

Making the ‘real’ thing avoids different people from confusion. This will help you dictate what the software is and is for.

It is essential to create application that is feasible and functioning – and it must be done as soon as possible. This enables developer to collaborate work effectively and efficiently. In addition, this practice facilitates them to focus on what should be done in the first place.

Don’t expect

to get it right

the first time.

Let the app grow

and speak to you.

Let it morph



With web-based software

there’s no


to ship


Design screens,

use them,

analyze them,

and then

start over



This is a fact: Mistakes and risks will definitely come out. No matter how good you plan on something – such as creating application – it will not stay 100% of your expectations. You just have to let go on your mistakes and continue working on it. Let your works grow and speak to you. What you are facing is all part is all part of our best experience. Take a step out of time.

Your clients should not think too detailed work. In this way, you are focused on doing the real thing to be done. No burdens. No strings attached. In addition, this will help you to be more decisive when it comes to choosing the right plans for your projects. It is your obligation to know your role and meet the requirements. Decision-making can’t be passed to someone else. It must be you who should do it.

You should also remember that you cannot please everyone else. You are not made into perfection. We are made with weaknesses and strengths. That’s why we learn – to improve.

This chapter also illustrates on how we should consider things in creating a website. The authors discussed parts that would help us enhance our website strategies – and how we should set our goals in each process.

In creating web application, it is important to include important details or features, first. Inch by inch you add a little spice on your application. Ideas must be passed – one by one. Not only it would help you to become more efficient in creating them, you learn to be contented first, on what is really needed in the first place.

Don’t create applications that just can be created in only one iteration. Continuous maintenance and improvements must come along the way. You must be smart on doing things – not making them too complicated.

The chapter mainly explains on techniques to be used in making your application more constructive. By disseminating proper information, this would lessen your time and cost. You must already have the picture how the application should look like. A prototype. A skeleton of how the application will came to be. In this way, you do not have to think too much on building and assembling your application.

People who will be probably become your clients should already have the taste of using your application. A feeling. An appetizer – if you know what I mean. That’s why the author suggest you to create application that can be deployed in the Web, such as html pages. This would help them be familiar with what are you trying to build. It is alright that they can view it as ‘under maintenance’, but make sure that they already have the idea of what are you trying to build.

In this way, violent reactions or other concerns will be lessening out because as they give their feedbacks, this would eventually help your application grow more. Making your application grow more meets the expectations of their user experience.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: