Getting Real – Chapter 11

In general, this chapter discussed about Words. It explains and illustrates everything from documentation and specifications that should be processed in making web applications.

In paperwork, developers who develop web application should learn this – and the end, most customers won’t read a thing with that documentation. So, it is more important for them to know exactly what the products they are buying. Too much organized works would make your client confused and indecisive. What matters most is how well the application should run smoothly.

Authors suggested that developers should learn to explain customers that are comprehendible for them. Avoid too much ‘geekish’ talk. Instead, talk with them in a common language. Too much technical stuffs could eventually drained up their minds. As a developer, you present your features that can be easily detect by your clients. Be normal and stay normal. You don’t present specifications that are not feasible enough to make. Make your program work at its finest – not to impress your customers from your ‘written’ works.

Lorem Ipsum. It’s been a common thing for almost centuries now, yet it is infamous. Funny thing is that developers are too lazy to change that ‘default’ information. The chapter explains that developers should utilize ‘real’ words than using Lorem Ipsum. Web developers should learn, not to copy-paste the information, but they should learn to acquire information from their clients or customers. Developers should learn to think – think of what customers would think on their applications. Interaction between the client and the developer is important to come up with a better and pleasing interface for the end-users like them.

Web developer must learn how to personify their products. Their application represents themselves. It reflects their attitude and character. Each developer must learn something deeply about their product – making it a subject, not a mere object. They must seek this ‘inner’ information so that developers could come up a better strategy to build their application. Knowing more about your product means learning more. Through proper learning and guidance, developers can create their web applications effectively and productively. What people see is what you get. Developers must understand and reflect from the features they’ll be using – designs, functionality or whatsoever.

Getting Real – Chapter 10

This chapter tells us how we should manage our codes – on how we should implement it and making it simpler for us to understand. There are different ways and techniques to utilize your codes efficiently. Just make sure, that every time you code, you remember this quote:

“The palest ink is better than the best memory.”

As human beings, our memories are not precise and can fade without notice. Memories could die eventually. Sometimes, best memory could still lack some elements, which is something unavoidable. It is more reliable to write something, which could remain intact for a long time.

Something that written down is far more accurate. It is something that will be firm and will stand the test of time – something that would last a lifetime.

To write it down is to record it. Just like our history, some facts were written down and not easily forgotten. You have taken the big picture – it is something that you could still recall for a long time. However, some information may not be accurate; the contents written down will be remaining unaffected. Unlike facts that were just stored in memories, they can’t be preserved for a long time.

Just like in any business transaction – you need to write everything down. You don’t just take anybody’s word for a fact. You need to write it down.

Good programmers always document their codes in a way that they are understandable. This would also help you to track down your progress – whether your program/apps is working fine or not.

Knowing your codes would help you lessen time to overdo managing time. As long as you write information that is helpful for your projects, you don’t have to worry so much in making them.

Getting Real – Chapter 9

In this chapter, the author discussed how we should design our interfaces. It is ALWAYS a GOOD PRACTICE to know first what is the BIG PICTURE of the project/application you are going to make. Determining how your program will look like would give you already the idea on what will be your scope – whether you need a full-blown project or a simple app to make.

Keeping the idea of knowing what will be the outcome of your design would help you focused more on the functions that you will be adding or creating. The designing of your program would also limit yourself – avoiding the idea of making projects that are not feasible to make. In designing, start first to what is really INSIDE your application. At this stage, you may eventually have the knowledge of what will be the primary purpose of your program/application.

What people see at your application/proect is what you get. Always start a good impression in making designs/layouts for your project. These designs would serve as blueprints for your work. As for the impression you’ll be getting from others, there are three ways, or should I say, three types of first impression – 1. regular, 2. blank, and 3. error. Having a ‘blank’ impression from your viewers would serve as an advantage, since it would help you more to motivate or to convince your viewers that your project/application is one of the best they could even see. Talk about marketing your apps to people for the first time!

Always remember that changes, even problems, are inevitable. Now, it is up to you whether you want to change you app – good or bad – which will eventually reflect you character as a developer of that program/app. Know what are your real capabilities and skills to develop and create an application. In every program/application you make, you learn more and you became mature – you now understand and experience what it feels like to create your own apps.

The author suggest that in making web sites, it is more advisable to focus on what customers or users REALLY NEED. Avoid DESIGNING too much on your website/s – thinking that compelling stuffs would help you. As you can see, too much design means too much maintenace to managed. The author recommends to use small-scale websites, which will help you and your customers navigate websites/links smoothly and efficiently.

Think before you act. To avoid too much cost or breakdown of your project/app, learn to analyze first what would help you as an individual – and what others can benefit with. By understanding what are ‘real conversations’ coming from your customers, this would aid you plan ahead to make and to design the specific needs of your customers. By managing what probable risk/s might happened, you can assure yourself that you are ready and prepared for it.

Getting Real – Chapter 8

Chapter 8 talks about staffing – on finding the right and suitable person to do the job for you. In staffing, you hire people which has the best standards for the job. You choose people – at the right time and at the right place. Finding the right people is not an easy task. You must know how to pick out people who are potential for the job.

I remember what I’ve learned during our PERMANA (Personnel Management or Human Resource Management). In hiring an employee, two processes or steps must be consider – recruiting phase and selection phase. In recruitment, employers would find people who would meet their requirements, such as the character, skills, and attitude of the person. On the other hand, selection phase seeks for picking out the right person. You have to break down the list of potential employees. In this process, proper decision making is vital.

Hire less and Hire later. The author explains that we must hire less people when it comes to starting out a project. Finding less people to work the job but being good enough for it would be fine. In this way, your company you’re working with will reduce its cost.

It is important for people to know everyone else – more. In this way, you cannot afford to lose people who are deserving for the job. You interact with them and you participate with them. Communication between two people make them healthy – especially in social aspect. In conversing, you stay connected with your peers- you know more about them.

Get well rounded individuals. You should learn to adapt with new people around your organization. You show them your experience and let it inspire them. Be a role model for them. You must learn to connect with them. Connect. Connect.

Passion. It is important for everyone who will make a project. Without passion in work, you cannot appreciate the works you’ve done. Passion makes thinkgs spiced up. It gives more meaningful to your project. By staying commited at your work and prioritize things you should prioritize, you can finish your project smoothly – without hesitations or worries. By staying optimistic, you would surely enjoy working with your apps, and in the same way, you build healthy relationship with the team.

Getting Real – Chapter 7

Many companies nowadays have employees who are specialized in a certain field of work. Everybody have their own little world. In creating applications, the author emphasizes that

“As much as possible, integrate your team so there’s a healthy back-and-forth dialogue throughout the process. Set up a system of checks and balances. Don’t let things get lost in translation. Have copywriters work with designers. Make sure support queries are seen by developers.

Even better, hire people with multiple talents who can wear different hats during development. The end result will be a more harmonious product.”

It is more commendable to create healthy relationship with everyone involve in your work. A diverse community would probably work effectively that those who are not. Different people needs different people to interact as well. They must learn how to adapt others, just like how others would adapt you.

In communication, it is important not to waste too much time in meet-ups. Everything should be on fast paced. Not only that you are conserving time and effort for meetings, you also stay focused as possible. Lengthy discussions would sometimes hides the real deal. Time management must be done to avoid ‘productivity-killing interruptions’.

Lastly, it is important that you are kept motivated on your work. Without that motivation, that passion of working with your application – what’s the use making the in the first place? You must love what you’re doing. Stop being pretentious and act as normal. Be a professional. Being motivated gives you the way with the right direction.

Getting Real – Chapter 6

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

and

evolve.

With web-based software

there’s no

need

to ship

perfection.

Design screens,

use them,

analyze them,

and then

start over

again.

-37signals

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.

Getting Real – Chapter 4

In this chapter, 37signals started by informing us that in every application that we will be building or developing, we must look for the big picture.

“What does your app stand for? What’s it really all about? Before you start designing or coding anything you need to know the purpose of your product — the vision. Think big. Why does it exist? What makes it different than other similar products? “

– 37signals.

What the author wants to pin-point here is that we should learn to create vision among ourselves. This vision will direct your decisions, which will also and keep you remain on a certain goal.

“Are we staying true to the vision?”

– 37sginals

We should also remember that functionality is the more concern when it comes in creating an application/software.

I remember one experience of mine during my second year college. Yeah. I remember that experience, or should I say, that err- disaster.

It was our IMPROG3, a programming course, when we were tasked to make a particular system along with the database features for our final project. Shannon Angto and Evan Severino were my group mates during that time. We started to make a Human Resource Management system.

After set of meetings, I was tasked to make a layout of what will the systems looks like. So I made it – from buttons, forms, etc. I was proud of myself that I was able to make a layout that may look compelling for the users who will actually use it.

Here’s some screen shot of what I actually spent a lot time working out:

Talk about being nostalgic! Yay! Stop reminiscing ~X(

Now here’s come the sad part. It almost took me a week to make the user interface. It’s almost the deadline when I haven’t started to fix it’s functionality. Aarrgh. Sleepless nights!

We sooner found that the ones were actually building is almost a full-blown HR management system. Our only task was to make an attendance tracker, plus, a system that will create, edit, and delete employee information.

Here comes the more sadder part. We weren’t able to run the system completely, we were still lacking a LOT of validations, and we were still experiencing error problems along the way. We end up making the UI more likely to be 110%, while functionality – 40% to 50%.

Because I did focus too much in designing the user interface, the group ended up cramming – even on that last day of submission of projects. I have I also remember that time when we stay the whole afternoon in the class to fix a lot of bugs. Aarrgh. I can still remember that time when I haven’t eaten my breakfast – even my lunch.

What the chapter wanted to say is that we should learn to prioritize ourselves in building application that should be needed in the first place. One thing I’ve learned in that experience is that I should stay focus on what is the scope is all about. I was focusing too much on improving the system more, rather than focusing myself on what was really needed to do. I admit it – I was poor in scope management that time. I didn’t realize that we were actually gone too far.

Do things smarter – not harder. I will always remember that. You should learn to appreciate first in making smaller projects than focusing too much for bigger ones. Once you have done your part in making that small project, you could start improving it and later, face yourself for more challenging task.

Don’t waste on time figuring out a certain problem that isn’t existing yet. It is better to stick first on what was really happening. Once you resolve these problems, learn to respond on other problems that you’ll be encountering, one by one.

The chapter also explains that we should learn to choose our customers – people who will put an interest of using the system. I know that we cannot please everyone. Choosing the right people is the next step of developing your character and your systems as well, to be on greater heights. I learned that you should be doing things because you just want others to please your work. You do things because you will benefit on it. You work on things because it represents you.

Overall, there is one thing what the author want us to understand – seeing the big picture maintains our focus in setting our goals and decisions directly on one side. We keep on the usual phase that we are doing – no distractions or whatsoever. Everything is on track.

Set your priorities first. Before anything else, you should learn to set things which comes first and which comes last. Take one step out of time. Never skip on things that are important. You must follow on a certain steps so that everything is in order.

Abram. Will you stop it already? Haha.

Thanks for reading. God bless you all.

Getting R-E-A-L

Time check. 10:32 AM

I was about to cram myself up posting this blog.

It was almost 11 AM when I finally read the first two chapters of ‘Getting Real’ by 37signals.

Alas! After reading and comprehending them, I’ve decided to make a so-called reaction paper for this.

After clicks of browsing several web pages, I suddenly remember something.

Something about

User

Experience

Let me share you something on what I’ve learned from Microsoft few months back.

The term User experience, often-abbreviated as UX, is used to illustrate the overall experience and satisfaction a user has when using a product or system.

It most usually refers to a mixture of software and business procedures, such as selling over the web, software usability, etc., but it applies to any result of interactive design.

To understand better we have here a simple metaphor on displayed below:

If you are the one to open the can what will you choose between the knife and the mechanical can opener?

Definitely you’ll choose the can opener because you’ll consider which is faster, easier, and more reliable to use.

This implies the quote, saying,

If something is

hard to use,

you’ll just

use

it less.

Most software designers and developers of today are focusing on the goal of creating an application that will create desire for the user to discover and learn to use the system efficiently and effectively.

The user has four resources to expend in discovering, learning, using, and hopefully becoming efficient in your application.

The more of these the user must spend to learn and operate your app, they less they have to apply to their actual goals.

More than being user friendly, your application should be people ready!

The

experience

is everything

because everything is part of

the experience.

Just like Microsoft, this is how a privately-held Chicago-based company is committed to building the best web-based software products possible for their users.

This is 37signals.

37signals made a book called Getting Real – a book which describes their business, their design, their programming, and their marketing philosophies.

Getting Real is like a strategy. A technique. A practice in making applications based on the customer needs, ideas and how they will able to utilize it. It is how UX should be experienced.

Good thing about 37signals is that they were able to come up with set of applications that allows users to handle them effortlessly. And I must say that having this kind of applications is a BIG ADVANTAGE for them, productive-wise and efficient-wise.

Getting real gives you that EDGE of doing things in fast phase – doing things at the same time. Users usually make use of application which has the capability of easy-access or should I say, the capability of navigating different functions of the application.

In every project you do, you must determine different constraints, such us the TIME, COST and SCOPE. I personally experienced them. Good project management should be able to help you in handling them. You should learn to prioritize in small things first before handling big ones. You must think of an achievable goal. Something that is doable. Something that is possible.

Expect things that everything will happen, negatively and positively. With these, you learn more. You became more mature.

Doing projects is like a game. In everything you do, you may actually make a risk out of it.

Competition is also a key to improvement. With this, you could actually improve your applications by comparing the similarities of your product and of your competitor’s.

When you solve your own problem, you create a tool that you’re passionate about. And passion is key. Passion means you’ll truly use it and care about it. And that’s the best way to get others to feel passionate about it too.

– 37signals

I totally agree with this one. If you’re really up to something, let others know about it too. Later, these things that you feel passionate about will be appreciated by other people as well. It is something that represent yourself – you whole being.

It is almost 12.30 PM. (I’m still thinking of adding some stuffs here later.)

Though I’m still at the first few chapters of this book, I would recommend this for everyone, especially for people who wish to create compelling web applications without having difficulty of understanding and applying concepts in constructing applications. It would also change their thinking on how to build applications.

Thanks for reading.

Comments and suggestions are much appreciated.

Have a nice day.