I will write an article on Qiita for the first time. I would like to start posting after knowing all about Qiita's functions, etc. in detail, but I feel that even if I hit Ishibashi 100 times, I can not take a step, so studying Ruby I will try it for the time being at this timing when I started. For the time being, I wrote a record of what I learned as a memorandum. It is still unclear how to write an article from now on, but I would like to brush up the writing style and contents little by little. I would like to write about myself little by little every time I have a great opportunity.
Start studying using the "Ruby study course" of "Progate". This time, I finished "Ruby Learning Course I".
Immediately after you start learning programming, you will be made to think and study, "Let's do this here to avoid troublesome things and duplicate work, and to reduce unnecessary mistakes as much as possible." You might be told, "Because that's the cornerstone of programming, right?", But I'm fascinated by such a natural place.
Even in the workplace where I used to work, I took on the challenge of simplifying and automating various tasks using my spare time. ――Try to improve analog and manual work by making full use of Excel formula etc. ――Every time you use a newly created Excel sheet or Word material as a template, you can make improvements every time you use it. ――Every time someone asks me about work procedures or work methods, I don't like to teach them how to take steps, so I make a work manual (I ask people until I'm satisfied with any questions I can't solve, but I hear from others. It's painful to be done ...)
Well, the point is that the main motivation was to stop spending a lot of time on simple tasks every day and to produce output with added value as much as possible. As a side effect, I also thought that it would be good if the benefits of that effort would eventually spread to the teams and departments and everyone would benefit. At first, I spent a lot of time studying Excel on my own, but as I hit various walls, I learned about programming and RPA. Especially if you have some programming knowledge and skills, I learned that you can automate work across different software and build a simple web application that can be used within a team or department without buying an expensive ERP package. It was.
Even when I was studying business at graduate school, I was overwhelmingly lacking in technical skills and knowledge (software and hardware), although my ideas were pitched, so I could create an abstract image just by arranging desk theories. I couldn't realize it, and I felt a lot of regret. (All the ideas that came up at that time were only those that were finally completed by incorporating digital and IoT into the system ... After all, the ideas that were rejected when selecting issues were later marketed as almost two business models overseas. I found out that it appeared in the system and made a fair profit ... This is already a Columbus egg.)
Creating something by programming is a means and work that ultimately pursues convenience and efficiency. Even now, I'm always thinking, "Oh, I wish I could do something like this. If there was such a service, it would be more convenient in the world." I decided to seriously learn programming software, which is also a means to realize such inspiration and thoughts more easily. I will write about this story little by little whenever I have a chance.
――Why use variables in programming --The same element can be used repeatedly ――It will be easier to respond to changes later ――It becomes easier to understand what the elements are
--Variable name rules --Write in English --For 2 words or more, separate blank areas with underscores. --Unwanted variable names => Romaji notation, Japanese notation, etc ... --Variable name where error occurs => Number start
--Variable expansion in strings --Variable expansion is possible with "# {variable name}" in the character string
Recommended Posts