HomeGroupsTalkZeitgeist
Hide this

Results from Google Books

Click on a thumbnail to go to Google Books.

Getting Real: The smarter, faster, easier…
Loading...

Getting Real: The smarter, faster, easier way to build a successful web… (original 2006; edition 2009)

by Jason Fried, Heinemeier David Hansson, Matthew Linderman

MembersReviewsPopularityAverage ratingMentions
2441347,176 (4.09)5
Member:apostlion
Title:Getting Real: The smarter, faster, easier way to build a successful web application
Authors:Jason Fried
Other authors:Heinemeier David Hansson, Matthew Linderman
Info:37signals (2009), Paperback, 194 pages
Collections:Your library
Rating:*****
Tags:None

Work details

Getting Real: The smarter, faster, easier way to build a successful web application by Jason Fried (2006)

  1. 00
    Founders at Work: Stories of Startups' Early Days by Jessica Livingston (timspalding)
  2. 00
    Hackers and Painters: Big Ideas from the Computer Age by Paul Graham (timspalding)
    timspalding: The recommendations for this book are too heavy on programming, and too light on creating great websites and web applications.
None
Loading...

Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

» See also 5 mentions

Showing 1-5 of 13 (next | show all)
Very quick read, but not a particularly good one. The advice is extremely simplistic, bordering on platitudes, and much of it is not particularly actionable. A lot of it simply does not apply to *many* companies: e.g. building for yourself is all it takes to find a market (tell that to the many engineers who built something that *only* they would want), everything can be self-funded (many business cannot), everyone should give away all of their data for free (unless, of course, data is your differentiator, which it is for many companies).

It's not all bad, of course. The advice on design is actually quite good, mostly because it sticks with very concrete details: e.g. avoid too many preferences/settings in an app, design for regular, blank, and error states, copywriting is part of the design, and that your app has a voice. And some of the quotes from third parties are decent too.

Overall, there is some good stuff in this book, but it doesn't do a very good job of presenting it.


Some quotes that I liked:

Build half a product, not a half-ass product

The best designers and the best programmers aren’t the ones with the best skills, or the nimblest fingers, or the ones who can rock and roll with Photoshop or their environment of choice, they are the ones that can determine what just doesn’t matter. That’s where the real gains are made. Most of the time you spend is wasted on things that just don’t matter. If you can cut out the work and thinking that just don’t matter, you’ll achieve productivity you’ve never imagined.

Another reason to design first is that the interface is your product. What people see is what you’re selling. If you just slap an interface on at the end, the gaps will show.

Design for regular, blank, and error states.

The customer decides if an application is worthy at this blank slate stage – the stage when there’s the least amount of information, design, and content on which to judge the overall usefulness of the application. When you fail to design an adequate blank slate, people don’t know what they are missing because everything is missing.

Copywriting is interface design. Great interfaces are written. If you think every pixel, every icon, every typeface matters, then you also need to believe every letter matters.

Encourage programmers to make counteroffers.You want to hear: “The way you suggested will take 12 hours. But there’s a way I can do it that will only take one hour. It won’t do x but it will do y.”

Lorem ipsum changes the way copy is viewed. It reduces text-based content to a visual design element – a shape of text – instead of what it should be: valuable information someone is going to have to enter and/or read. Dummy text means you won’t see the inevitable variations that show up once real information is entered. It means you won’t know what it’s like to fill out forms on your site. Dummy text is a veil between you and reality.

Think of your product as a person. What type of person do you want it to be? Polite? Stern? Forgiving? Strict? Funny? Deadpan? Serious? Loose? Do you want to come off as paranoid or trust- ing? As a know-it-all? Or modest and likable? Once you decide, always keep those personality traits in mind as the product is built. Use them to guide the copywriting, the interface, and the feature set. Whenever you make a change, ask yourself if that change fits your app’s personality. Your product has a voice – and it’s talking to your customers 24 hours a day. ( )
  brikis98 | Nov 11, 2015 |
The game changer. ( )
  sturmer | Oct 25, 2015 |
One of the best books, which cut the crap, and is to-the-point from Page-1. Shed the fat, and start lean, and just-do-it approach is the crux of this book. ( )
  ashutosh.kumar | Jan 19, 2014 |
An easy and useful read. It doesn't apply to web application but to all of our life. Select to what we really want to do and execute it. Don't need much document, meeting and so on, just focus and do it! ( )
  xuelian | Jul 12, 2012 |
The software industry has seen many incarnations as far as project development methodologies with its first account of a true leap in flexibility when some teams abandoned waterfall and spiral for the ideas presented in the agile manifesto. This brought for a whopping number of agile methods ranging from SCRUM, extreme programming, lean and many more. Years later, evangelists still clamor how their methodology is better in every single way than the rest (despite the fact that most of them are founded on the same principles) and this has started many fruitless discussions in the same manner people argue over religion.

Now enter Getting Real. Getting Real is more than simply a software methodology. It is an opinionated manifesto of what should and shouldn't be done not only in software development but in business and projects in general. It takes the agile manifesto and pushes it to such an extreme that other agile methods seem slow and bloated in comparison.

The tone of the book is so strong that you almost feel like the writers are saying "fuck this" and "fuck that" even though they never actually say it. You WILL question why things aren't being done the Getting Real way. Some of the principles in Getting Real can seem pretty revolutionary, specially if you've worked in software development. It says no to specs, no to meetings, and no to pretty much everything you've been doing in the past. On the flip-side, some of the ideas in Getting Real can seem pretty irresponsible; like saying no to specs, no to meetings and many more. The whole purpose of this book is not to blindly follow what 37signals has done to achieve success, but to see software development and business from their perspective and figure out what could actually work for you.

While I do agree with some of the ideas in this book, some of them I don't. Yet the reason why I won't give this book five stars is not related to the ideas presented in the Getting Real process, but the meaning of the process as a whole: it implies that by following this formula (or rather process) you'll gain success. The whole idea of following a script in business is preposterous. You will not be successful just by following what this book says. People think that just by following Getting Real, Rework, The Lean Startup (and many similar books) they can be as successful as the people who wrote them and that is statistically wrong. You cannot assume an absolute outcome from initial variables in business for the simple fact that business success is relative to the competition. This book is part of the plague that roams around in startup circles who are more interested in processes than strategy or vision, thus narrowing their focus of business to the complexity of the Ten Commandments.

There are many things that this book will achieve: it will inspire and motivate you. But more important, it will force you to question why things are done the the way they are in order for you to draw your own conclusions and adapt. Read the book, but take it as a grain of salt. Read it assuming this books subtitle is "how we do things at 37signals, yet it may not all work for you". ( )
  guiscard | Jul 2, 2012 |
Showing 1-5 of 13 (next | show all)
no reviews | add a review

» Add other authors (6 possible)

Author nameRoleType of authorWork?Status
Jason Friedprimary authorall editionscalculated
Hansson, David Heinemeiermain authorall editionsconfirmed
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Series (with order)
Canonical title
Original title
Alternative titles
Original publication date
People/Characters
Important places
Important events
Related movies
Awards and honors
Epigraph
Dedication
First words
Want to build a successful web app? (Introduction)
Conventional wisdom says that to beat your competitors you need to one-up them.
Quotations
Last words
(Click to show. Warning: May contain spoilers.)
Disambiguation notice
Publisher's editors
Blurbers
Publisher series
Original language

References to this work on external resources.

Wikipedia in English (1)

Book description
Haiku summary

No descriptions found.

No library descriptions found.

Quick Links

Swap Ebooks Audio
25 wanted1 free
1 pay

Popular covers

Rating

Average: (4.09)
0.5
1 1
1.5
2 5
2.5 1
3 10
3.5 2
4 25
4.5 6
5 30

Is this you?

Become a LibraryThing Author.

 

You are using the new servers! | About | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 113,177,855 books! | Top bar: Always visible