Once at a magic gathering, when talking about Chinese medicine, it was surprising to find that 80% of colleagues believed that Chinese medicine was a scam. Little Master was shocked.
Later, Little Master talked about this with a magician from Red Hat. Little Master thought that treating a disease is like going to war, with both sides having different strengths: me 5, enemy 8.
Install Jenkins with brew install jenkins in the shell
Then start Jenkins, enter 127.0.0.1:8080 in the browser
Install the xcode related plugins in Jenkins
The steps are available in other blogs, Google “ios ci continuous integration“, for example:
Throughout the book, there is a pervasive sense of aging.
Regarding the passage of time and the decline of physical ability, there is a sense of helplessness.
Unlike resisting and refusing to accept old age, the author gradually accepts this fact and uses it as a rule to deal with.
Many questions that I am curious about, the author has also reflected on and delved into more deeply.
This is probably:
I’m the kind of person who likes to be by himself.
This book is really inspiring for me.
However, a few days ago, our CTO picked it up and said, “The illustrations are so ugly, how can you call this design?”
Oops.
I bought it on Amazon at a discount, and the rating on Douban is not low, so I decided to give it a try.
The first principle is quite surprising:
Never work on the computer yourself.
As a programmer, all I can do is laugh.
When this book was written, object-oriented programming was still niche, but now functional programming has begun to become popular.
Until today, most programmers have heard of the ideas and methods of refactoring. If you are a Java programmer, it is even harder not to know about it.
As time has elapsed, refactoring has become a part of coding.
Chapters 1, 2, and 3 of this book explain what refactoring is and when to refactor. They should be read carefully.
Chapters 4 to 11 discuss specific methods, so if you are familiar with Java, you can refer to them accordingly.
The following chapters can be skimmed over.
When I was on my Gap Year, I came across this book while practicing on codecademy. I only looked at the chapter on Ruby, and at that time I thought knowing Go was already quite geeky.
A year later, when the company I am currently working for was refactoring the backend, we considered using Scala. One of my friends, thinking that game development had higher salaries, decided to learn Erlang. I attended a sharing session at a Thoughtworks event and heard about Clojure.
Upon revisiting this book, I suddenly realized it covered Ruby, Io, Prolog, Scala, Erlang, Clojure, Haskell.
I felt like I had been looking at the sky from the bottom of a well. Upon flipping through this book again, I realized that I don’t really need to read it.
So if you are just curious and want to satisfy your curiosity, you can take a look, but if you want to seriously learn, it’s better to skip it.
There was a time when I always thought my parents were stubborn and unwilling to try new things. Out of ignorance, I even used to ridicule them.
Today, when I spent half a day changing from Windows 8.1 to Windows 7 just for the sake of using IE8 (as a side note, I only needed it for online banking), and I thought to myself, “I hope I never have to use a new system again.”
I recently bought a Filco keyboard with red switches, which is perfect for both gaming and coding.
Previously, I used System Preferences -> Keyboard -> Modifier Keys -> Select keyboard -> Opt-Cmd Cmd-Opt to change the key layout to match Apple’s.
However, I had to change it back every time I played Starcraft, as the process mentioned above was quite tedious.
As for the F1 - F12 keys, there was simply no way to change them, and locking the screen was also an issue.