This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.
Hide this

Results from Google Books

Click on a thumbnail to go to Google Books.

Getting Real: The smarter, faster, easier…

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

by Jason Fried, David Heinemeier Hansson

MembersReviewsPopularityAverage ratingMentions
2601464,231 (4.13)5
  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.

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 14 (next | show all)
This was a great book, and anyone thinking about building a webapp should read it.

Essentially boils down to Nike's moto: Just Do It. ( )
  simonspacecadet | Jul 29, 2018 |
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 |
Showing 1-5 of 14 (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
Important places
Important events
Related movies
Awards and honors
First words
Want to build a successful web app? (Introduction)
Conventional wisdom says that to beat your competitors you need to one-up them.
Last words
(Click to show. Warning: May contain spoilers.)
Disambiguation notice
Publisher's editors
Publisher series
Original language
Canonical DDC/MDS

References to this work on external resources.

Wikipedia in English (1)

Book description
Haiku summary

No descriptions found.

No library descriptions found.

Quick Links

Popular covers


Average: (4.13)
1 1
2 4
2.5 1
3 11
3.5 2
4 26
4.5 6
5 32

Is this you?

Become a LibraryThing Author.


About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 131,736,697 books! | Top bar: Always visible