[JAVA] Six thank-you technical books that I desperately read because I wanted to be up

Introduction

I was amazed at my writing and joined the SES company at the top of the job vacancies.

Death marches are rampant at the site where they are driven out, and every day they go to work continuously on Saturdays and Sundays.

On New Year's Eve, when I was working on a secondment

** Why am I weak in position and technical ability? I want to grow up **

I vowed firmly and desperately read the technical book and hunted.

As a result, I was able to change jobs to the web-based company I wanted, and I was able to meet wonderful members there.

Currently, I am reading technical books while working as a lead engineer at Startup.

I would like to thank the technical books that changed the life of I and introduce them here.

Thank-you technical book ① Readable code

A thank-you book that I read with high expectations for the future while everyone was taking a nap during the lunch break.

I noticed that the code of the project members was terrible, Even more than that ** I was strongly reminded that my code was hard to read **.

I want people who do not have the habit of reading technical books to read it.

Since I read the readable code, I scribbled it Is wonderful.

Thank-you technical book ② Introduction to JUnit practice

The book I bought when I first wrote the test code. A SIer customer said, "Be sure to write a unit test for this project." I didn't even know the existence of the test code, so I bought this book for the time being.

`If you pass 1 and 1 to the function that adds, then 2 will be returned. Does it make sense? `` I thought, but as I read it, I couldn't help writing a test. It was an opportunity to think, "It's good to write a test for a new job!"

Thanks technical book ③ Perfect Java

"To write good code, you have to know the language itself! (It's better to know a lot!)" I thought, and bought it under the name of Perfect. The more I read it, the more I felt that I could make a difference to other colleagues, so I read it on the train.

It's a good memory to learn reflection here and write a black magic code saying "Can you do that!".

Thanks technical book ④ Ruby on Rails 4 application programming

I decided to use Rails at my new job, and bought it with a rush of "I think it's from a book at first!" A book that became "Rails is awesome!" Because it contains many practical usages.

I recommend it to anyone who wants to get started with Rails. I think there is a Rails 5 book now.

Thank-you technical book ⑤ Effective Ruby

I wanted to go one step further, so I stretched out and read this book.

Most of the content is concrete.

I was able to know that I could write better code and patterns if I knew it.

Thank-you technical book ⑥ 97 things programmers should know

A book with many columns of transcendental programmers. I was excited just to read it, so I read it when I wanted to raise my motivation.

Actually, it seems that you can read it for free on the Web. I did not know. ..

97 Things Programmers Should Know

[Boy Scout-Rules](https://xn--97-273ae6a4irb6e2hsoiozc2g4b8082p.com/%E3%82%A8%E3%83%83%E3%82%BB%E3%82%A4/%E3%83%9C % E3% 83% BC% E3% 82% A4% E3% 82% B9% E3% 82% AB% E3% 82% A6% E3% 83% 88-% E3% 83% AB% E3% 83% BC% Good memory such as E3% 83% AB /).

in conclusion

What did you think. Technical books are great books for sharing knowledge and experience. If you haven't read it yet, please find your favorite book.   Also, @y_tsubuku belongs to Ulysses also employs, so if you are interested By all means.

Recommended Posts

Six thank-you technical books that I desperately read because I wanted to be up
Four technical books that I regret that I should have read when I was a newcomer