Getting Real is the book suggested to me at my boot camp. It is a book by 37 signals (a web application company) revealing the secret towards its success and growth. As I dig into the pages, I find out how useful it is to new beginners:- designers, programmers and businessmen.
The book starts with the meaning of getting real. Let me remind you again, getting real is written by 37 signals so the examples, story and plots mostly tilt towards the company procedures and IT sectors. But the main gist of the book is applicable to everyone in real world.
The book mainly focus on how to extract more from less. It justifies the point "Less is more" throughout. Start with whatever you have, not waiting for client to pay. Fund yourself. The book gives an example of "The Three Musketeers" :- developer, designer and a sweeper (someone who can roam between both worlds). A good software requires enthusiastic people willing to give their best, whose action speak more than words.
It's not necessary to have the perfect CSS, necessary features should be focused first. If any feature is already available, just integrate it in the system. Do not waste much time. Designs and specification does not give clear view to client so working software is preferred. Build it soon and optimize accordingly.
Meetings and discussions are boring. Team members can have get-together, short chats, enjoy on drive and with coffee. Most of the celebrations are done on the completion of project but it's necessary to celebrate small victories. Just target on a simple process and celebrate on its completion. Do not wait long. Developer should have alone time to code perfectly.
In design, paper sketch but prefer html sketch or use wire-frame. Design the main core of the product. Do not worry about header and footer. Always look for regular(when client are using it with data entry), blank(when no data is entered) and error(when data is entered but error appears) state solutions. In case of errors, get defensive about product. You need not be consistent but whatever you do on that time, do it fruitful. Be intelligent. Be fast.
Code lesser lines. Use less software. Use the tools which are interesting to use, which brings happiness to the programmers and excites them. Listen to your codes. They are always locating where the errors are. The client should always be able to use the software to check if the requirement is met or not even in preliminary phase
Do not write documents neither build a wire-frames if it is not turning real. If ask, just give simple brief of what it does, do not dive into technical explanations directly. During the system testing use the words what the user uses. Fill the form as like the users. Using real values help to find out the inadequacy on software. Treat your product as a person.
Suppose you are a singer and making an album, drop a song for free. Similarly give the user some free features. The registration and sign-out form should be as short and simple. Never try to make extra charge for preexisting users. Always deliver the unpleasant and uncertain messages without demotivating developers.
Promote in holy wood style: teaser, preview and launch. Make a interactive promo site like blog. Tell what's happening. Start early. Share your knowledge which make people always wanting to see the final product. Track the viewers, make lists and respond to them. Catchy name are preferred over technical terms for the project.
Responsive product is preferred with less manuals and training to use. Create a forum for the users where they can share and talk to each-other about the products, Appear on the forum whenever it is necessary.
Admit the problem yourself even if the customers are unaware of it. Track what people say about the product after launch. Always appreciate the writers and comment back even if negative. Do not release the beta version. It destroys the trust of users toward original release. Prioritize the bugs. All bugs are not to be treated. One that destroys the database should be treated first. Always be prepared for the storm. Go with the flow. Do not panic.
As the book ends, I realize what we can do with what we have, how less is enough, how being honest work and how a successful company is build. I really want to thank 37 signals for this amazing book. It will really help me in my career. And I want to suggest all the beginners to read this book once to know how things work.
