A story about a new engineer reading a passion programmer

A story about a new engineer reading a passion programmer

He became a new engineer and is now involved in application development at Rails. If you work as an engineer, read this book! I found a "passion programmer" in a typical article and read it, so I will write my impressions and summary. I will not touch on the details of the book, so if you are interested, please read it.

Passion programmer

The content of the book barely touches on the details of technical matters. No code came out.

Not just making money through the profession of a programmer It ’s not about getting ahead in the company The idea of being happy and happy is I was reading a book and it was very clear.

Among them, I would like to list two topics that left a lasting impression on me.

Already you are out of date

Is it okay to do Ruby if I eat as a web engineer? Is it true?

If you say something like this You may get angry at the programming school.

This topic was one of the topics that touched my heart the most. Technology will eventually decay. And in this industry the speed is very fast, It may expire soon.

Even COBOL, which is treated like an ancient language, must have been a really cool language at that time. Ten years later, "Ruby, which is treated like an ancient language, should have been a really cool language at that time." (I don't want that to happen)

** What do you do? **

To make an investment. The word investment is important. When new technology is born, it disappears every day. It's hard to know exactly which ones are left in ten years, It is important to learn (invest) such technology.

How many people could feel the potential and invest in the language Java when it came out? There shouldn't be that many. But those who could invest there could become cutting-edge people.

That's why let's invest. The investment may be successful. But you can get the experience of failing to invest. That is why I felt that I should think about and learn about the future of my technology.

The author said that he should learn at least one language a year. If you're doing Ruby this year, what should you do next year?

** Always invest in yourself **

Fat man in the mirror

If you are on a diet, you will be worried about yourself in front of the mirror. And when I see myself who hasn't changed at all from yesterday, I feel depressed and stop dieting.

The same goes for engineers, and I feel like nothing has changed compared to yesterday's self. This can happen in both good and bad ways.

For example, every day I get used to work and repeat the same work Even if growth has stopped, it cannot be noticed by looking at the daily changes. And after a year, I notice that growth has stopped. Then it's too late

** Find a companion who will evaluate you objectively ** That person may point out your mistakes and It may acknowledge your growth.

It can be a colleague at work or a community on the Internet does not matter. You should not only have your own scale, but somewhere else.

The end

I read it all right away, I would like to read it again after gaining a little more experience. It would be great if I could grow and discover new things at that time.

Recommended Posts

A story about a new engineer reading a passion programmer
[First post] A story about a second new graduate of PE becoming a programmer with no experience
A story about changing jobs from a Christian minister (apprentice) to a web engineer
A story about Java 11 support for Web services
A story about the JDK in the Java 11 era
A story about a very useful Ruby Struct class
A story about Apache Wicket and atomic design
A story about making a Builder that inherits the Builder
Side business x AWS talks about a life-changing engineer
A story about trying to get along with Mockito
A story about trying hard to decompile JAR files
A story about reducing memory consumption to 1/100 with find_in_batches
A story about introducing Evolutions into the Play Framework
A story about developing ROS called rosjava with java
A story about starting a Java-related book club for newcomers
A story about making catkin_make of rosjava compatible offline