[Ruby] [Output] Learn Ruby fastest from what you want to do, Part 1 Think what you want to make

1 minute read

Introduction

Qiita, do you have any output, engineers who are watching? The output will surely improve the learning efficiency!

“Doki! I’m just practicing problems…”

That person. All right! So I wrote this article. For you!

An effective learning method is output. Creating your own original program. It explains the flow of making an original program, so if you read it to the end you should be able to understand the basics of Ruby!

Target audience

This article is written for the following people:

  • I want to learn Ruby as a beginner in programming
  • I touched Ruby a little, but I still do not understand
  • I want to make something for the time being!

I’m going to tell those people in a way that is easy to understand.

What to learn in this article

In this article, you will learn the following knowledge about the basics of Ruby through the original program “Achi, Muite, Hoi! Game” that I created in the second month of programming study.

  • Method
  • Class
  • Various processing

In addition, we plan to explain the “Achi, Muite, Hoi! Game” in several sessions.

  1. Think what you want to make
  2. Break down functionality
  3. Write simple code
  4. Improve your code

If you read this, you should be able to make the following program! Of course, don’t forget to move your hands!

What you made

DEMO.gif

Then the following is the main story!

Operating environment

  • Ruby 2.6.6

Think what you want to make

I hear a voice saying, “What do you have to make, even if it is called an output?”

In conclusion, I don’t mind anything!

In my case, I decided to make this game with a kid, because I played with a 4-year-old child, “There, peel, whip”. Also, of your own, friends, family, and work colleagues.

  • Hobbies
  • What I would like to have
  • Worries/problems

I think it is ant to shape it from the above. I think there are some hints in everyday life.

After deciding to create “Where, Peel, Whih”, I wrote down the flow of the game process in the flow chart below.

Flowchart

Turn it over and whih! (Observation.get.png

Summary

In this article, I explained how to write what you want to make and what you have decided in a flow chart.

In the next article, I plan to explain the functional decomposition based on the transcript.

Reference book

  • Kitami-style illustration IT cram basic information engineer