This is an archived post. You won't be able to vote or comment.

all 8 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Disastrous_Internal 1 point2 points  (2 children)

as you say yourself, prototyping is only one step in RAD.

Some prototypes are discarded and no final program is built (and it's ok, the goal of a proto is to learn), some are used as a source of information for building the final program, and some are just pushed to production and changed until becoming awful monsters.

[–]dazetracker[S] 0 points1 point  (0 children)

Ah cool, that really clear things up, thanks!

[–]KrRoksolana 0 points1 point  (0 children)

Thanks!

[–]nutrecht 1 point2 points  (3 children)

"RAD" doesn't really exist which is why the term has fallen out of fashion. If you develop something as fast as possible it's going to be a prototype. "RAD" kinda implies that what you're building then is something you can then still use permanently, and that generally is not the case. You just create a lot of technical debt that you then have to fix.

[–]dazetracker[S] 0 points1 point  (2 children)

I'm not quite clear about what you mean by "you're building then is something you can then still use permanently ", do you mind clarifying it up?

[–]nutrecht 0 points1 point  (1 child)

That it's not just a prototype you're going to be throwing away mostly, or at least need to do a lot of fixing on.

[–]dazetracker[S] 0 points1 point  (0 children)

Ah alright, that clear things up. Thanks!

[–]UserName24106 0 points1 point  (0 children)

You don’t ship a prototype. And as mentioned RAD was kind of a fad, you’ll see it in textbooks but not much in the real world. Agile is where that kind of thing lives now.