What does prototyping mean in practice?

Question

When I recently asked about using Ruby, someone told me that this is good for prototyping. I basically know what it means to quickly get the main base of your application and work, see if there are conceptual problems, and then add the rest.

• Do I understand correctly how I understand prototyping?
• What will be a concrete example of prototyping a Snake game in Ruby or any other language?

Answer 1

Yes, prototyping serves as a proof of concept to ensure that what you want to build is doable. Something can be left in the prototype, it can be like exception handling, registration, etc.

Often a frequently occurring error occurs: the teams switch from the prototype to the real code "on the fly", i.e. just continuing the so-called "prototype", except that it now becomes real code.

Answer 2

, , , , , . . - , "" , .

, , . , - Ruby/Rails, , Javascript, . , , , .

, , , - " " - .

Answer 3

, . , , , .

An example of a game prototype Snake will have a snake so you can move up, left and right, something is eating, maybe one block in the middle of the board maneuvers around, and the snake grows when it eats something. Thus, you would not have a splash screen, or track high scores, or have different levels. Just the basics of the game.

Answer 4

“Good for prototyping” a polite way of saying “ It's hard to maintain ”