Make sure you understand this
This link has been bookmarked by 77 people . It was first bookmarked on 24 Feb 2007, by tenthead.
-
19 Mar 15
-
Getting Real starts with the interface, the real screens that people are going to use. It begins with what the customer actually experiences and builds backwards from there.
-
-
09 Nov 13
-
starts with the interface,
-
egins with what the customer actually experiences and builds backwards from there.
-
etting Real is all about launching, tweaking, and constantly improving which makes it a perfect approach for web-based software.
-
deal with reality.
-
A functional spec is make-believe, an illusion of agreement, while an actual web page is reality.
-
How 2002.
-
-
06 Jun 13
-
Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences
-
-
26 Feb 13
-
29 May 12
-
he importance of
-
-
15 May 12
-
Getting Real is about skipping all the stuff that represents real (charts, graphs, boxes, arrows, schematics, wireframes, etc.)
-
Getting real is less. Less mass, less software, less features, less paperwork, less of everything that's not essential
-
Getting Real is staying small and being agile.
-
Getting Real starts with the interface, the real screens that people are going to use.
-
-
02 Feb 12
-
07 Jan 12
-
The focus is on big-picture ideas. We won't bog you down with detailed code snippets or css tricks. We'll stick to the major ideas and philosophies that drive the Getting Real process.
-
-
21 Dec 11
-
19 Dec 11
-
16 Dec 11
Jacques Bosch"2
Want to build a successful web app? Then it's time to Get Real. Getting Real is a smaller, faster, better way to build software.
Getting Real is about skipping all the stuff that represents real (charts, graphs, boxes, arrows, schematics, wireframes, etc.) and actually building the real thing." -
06 Oct 11
-
27 Sep 11
-
20 Feb 11
-
Getting Real is about skipping all the stuff that represents real (charts, graphs, boxes, arrows, schematics, wireframes, etc.) and actually building
-
the real screens that people are going to use.
-
Getting Real is an approach ideally suited to web-based software. The old school model of shipping software in a box and then waiting a year or two to deliver an update is fading away. Unlike installed software, web apps can constantly evolve on a day-to-day basis.
-
we're-doing-this-to-cover-our-asses process.
-
a lot of these ideas are applicable to non-software activities too. The suggestions about small teams, rapid prototyping, expecting iterations, and many others presented here can serve as a guide whether you're starting a business, writing a book, designing a web site, recording an album, or doing a variety of other endeavors.
-
-
07 Feb 11
-
-
Getting Real starts with the interface
-
because it forces you to deal with the actual problems you're trying to solve instead of your ideas about those problems
-
-
23 Nov 10
-
31 Aug 10
-
This lets you get the interface right before you get the software wrong
-
while an actual web page is reality. That's what your customers are going to see
-
You need to build, launch, and tweak. Then rinse and repeat.
-
-
17 Jun 10
-
web app
-
faster
-
web app
-
Less mass, less software, less features, less paperwork, less of everything that's not essential
-
It begins with what the customer actually experiences and builds backwards from there.
-
get the interface right before you get the software wrong
-
web-based software
-
A functional spec is make-believe, an illusion of agreement, while an actual web page is reality. That's what your customers are going to see and use.
-
Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts
-
Getting Real gets rid of...
-
You don't need tons of money or a huge team or a lengthy development cycle to build great software.
-
In this book we'll show you...
-
- The importance of having a philosophy
-
The focus is on big-picture ideas.
-
You're an entrepreneur, designer, programmer, or marketer working on a big idea.
-
Distribute your software on cd-roms every year? How 2002. Version numbers?
-
agile development and business structures
-
a lot of these ideas are applicable to non-software activities too
-
-
03 Jun 10
-
This lets you get the interface right before you get the software wrong.
-
Getting Real delivers better results because it forces you to deal with the actual problems you're trying to solve instead of your ideas about those problems.
-
You're an entrepreneur, designer, programmer, or marketer working on a big idea.
-
-
25 May 10
-
15 Apr 10
-
04 Feb 10
-
- Getting real is less. Less mass, less software, less features, less paperwork, less of everything that's not essential (and most of what you think is essential actually isn't).
- Getting Real is staying small and being agile.
-
Getting Real starts with the interface, the real screens that people are going to use.
-
A functional spec is make-believe, an illusion of agreement, while an actual web page is reality.
-
- Timelines that take months or even years
- Pie-in-the-sky functional specs
- Scalability debates
- Interminable staff meetings
- The "need" to hire dozens of employees
- Meaningless version numbers
- Pristine roadmaps that predict the perfect future
- Endless preference options
- Outsourced support
- Unrealistic user testing
- Useless paperwork
- Top-down hierarchy
Getting Real gets rid of...
-
-
15 Dec 09
-
03 Aug 09
-
31 Jul 09
-
18 Jun 09
-
- Timelines that take months or even years
- Pie-in-the-sky functional specs
- Scalability debates
- Interminable staff meetings
- The "need" to hire dozens of employees
- Meaningless version numbers
- Pristine roadmaps that predict the perfect future
- Endless preference options
- Outsourced support
- Unrealistic user testing
- Useless paperwork
- Top-down hierarchy
Getting Real gets rid of...
-
- Timelines that take months or even years
- Pie-in-the-sky functional specs
- Scalability debates
- Interminable staff meetings
- The "need" to hire dozens of employees
- Meaningless version numbers
- Pristine roadmaps that predict the perfect future
- Endless preference options
- Outsourced support
- Unrealistic user testing
- Useless paperwork
- Top-down hierarchy
Getting Real gets rid of...
-
-
16 Jun 09
-
11 Jun 09
-
05 Jun 09
-
Getting Real is about skipping
-
Getting real is less.
-
Getting Real is staying small and being agile.
-
Getting Real starts with the interface, the real screens that people are going to use.
-
Getting Real is about iterations and lowering the cost of change
-
Getting Real delivers just what customers need and eliminates anything they don't.
-
Getting Real delivers better results because it forces you to deal with the actual problems you're trying to solve instead of your ideas about those problems. It forces you to deal with reality.
-
Getting Real foregoes functional specs and other transitory documentation in favor of building real screens.
-
Unlike installed software, web apps can constantly evolve on a day-to-day basis. Getting Real leverages this advantage for all its worth.
-
-
27 Nov 08
-
22 Nov 08
-
01 Aug 08
-
Why you should underdo your competition
-
-
06 Jul 08
-
skipping all the stuff that represents real
-
and actually building the real thing
-
The focus is on big-picture ideas.
-
-
05 May 08
-
Getting Real is about skipping all the stuff that represents real (charts, graphs, boxes, arrows, schematics, wireframes, etc.) and actually building the real thing.
-
Getting Real starts with the interface, the real screens that people are going to use. It begins with what the customer actually experiences and builds backwards from there. This lets you get the interface right before you get the software wrong.
-
just what customers need
-
ideally suited to web-based software.
-
Unlike installed software, web apps can constantly evolve on a day-to-day basis.
-
The focus is on big-picture ideas.
-
-
01 May 08
-
22 Mar 08
-
Getting Real is about skipping all the stuff that represents real (charts, graphs, boxes, arrows, schematics, wireframes, etc.) and actually building the real thing.
-
Unlike installed software, web apps can constantly evolve on a day-to-day basis. Getting Real leverages this advantage for all its worth.
-
Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts. This requires not that the writer make all sentences short or avoid all detail and treat subjects only in outline, but that every word tell.
-
-
22 Jan 08
-
19 Nov 07
-
03 Oct 07
-
24 Sep 07
-
13 Apr 07
-
While this book's emphasis is on building a web app, a lot of these ideas are applicable to non-software activities too. The suggestions about small teams, rapid prototyping, expecting iterations, and many others presented here can serve as a guide whether you're starting a business, writing a book, designing a web site, recording an album, or doing a variety of other endeavors. Once you start Getting Real in one area of your life, you'll see how these concepts can apply to a wide range of activities. >
-
about skipping all the stuff that represents real (charts, graphs, boxes, arrows, schematics, wireframes, etc.)
-
Less mass, less software, less features, less paperwork, less of everything that's not essential (and most of what you think is essential actually isn't).
-
small and being agile.
-
starts with the interface
-
builds backwards from there
-
This lets you get the interface right before you get the software wrong.
-
Getting Real is about iterations and lowering the cost of change. Getting Real is all about launching, tweaking, and constantly improving which makes it a perfect approach for web-based software.
-
delivers just what customers need and eliminates anything they don't.
-
delivers better results because it forces you to deal with the actual problems you're trying to solve instead of your ideas about those problems. It forces you to deal with reality.
-
A functional spec is make-believe, an illusion of agreement, while an actual web page is reality.
-
you're making software decisions based on the real thing instead of abstract notions.
-
Once you start Getting Real in one area of your life, you'll see how these concepts can apply to a wide range of activities.
-
-
11 Apr 07
Rick CallahanGetting Real foregoes functional specs and other transitory documentation in favor of building real screens. A functional spec is make-believe, an illusion of agreement, while an actual web page is reality. That's what your customers are going to see and
-
22 Mar 07
-
26 Feb 07
-
Add Sticky NoteWant to build a successful web app? Then it's time to Get Real. Getting Real is a smaller, faster, better way to build software.
-
-
yes
-
-
- Getting Real is about skipping all the stuff that represents real (charts, graphs, boxes, arrows, schematics, wireframes, etc.) and actually building the real thing.
- Getting real is less. Less mass, less software, less features, less paperwork, less of everything that's not essential (and most of what you think is essential actually isn't).
-
-
19 Feb 07
-
03 Feb 07
-
26 Oct 06
Public Stiky Notes
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.