preface
Before writing notes, READ the first note is marked on July 1, read 2 months to finish reading, this book is undoubtedly suitable for programmers to see, many scenes and cases in the book often feel shot, even if it is written by foreigners can also have a lot of resonance, here is what this book says.
What is the book about?
It is about the author’s personal journey, and the author gives some suggestions to the readers with his own personal experience, which can also be regarded as the standard for the author to behave and deal with things. Of course, the good aspects are worth learning, and the bad aspects should become our experience and lessons for reflection. If I were the author at that time, what choice would I make? The above is the content of this book is so simple, you can even view it as a summary of personal experience, estimated that many people may think it is chicken soup, but from a personal point of view can see a lot of content worth reflecting, so this book is highly recommended to all students.
Why read this book?
On the one hand is the curiosity of people, even without looking at the book basically speak what content in basic understanding is much, the book can be when programmers joke is (a self-deprecating), can also act as your own list of review and reflection, of course, as a “peer” books don’t need so earnest, also don’t have to be to learn the rules of the author, But don’t make the same mistakes as the author.
Personal assessment
Sometimes to relax will choose to see this book, this book can be used as a checklist, take a look at the author described the common fault of the programmers have on themselves, of course, the book of the concept of TDD is backward, and not worth learning and recommend books many other foreigners and foreign related programming environment, In addition, from the author’s text, we can also see how painful and difficult the world was in the early days of computer programming. It is hard to imagine what kind of experience it is to DEBUG with “paper tape”.
An overview of the note
- What should professionals do
– You shouldn’t waste other people’s time
– Stick to your boundaries
– Don’t do things at the expense of others
– Software should be easy to modify
– Don’t be the savior
- Coding trap
– Code with emotions
– Bad code
– Anxious code
– Flow zone (Sage mode)
Note the
What should professionals do
Referred to in the beginning of this book, the “professionals” these four words, the author for 42 years of programming is hardcore doyen, so voice or weighty, written advice also has the very strong guidance value, the author did the CEO is also done at the bottom of the employees, or most of the technical transformation, the boss of basic code is agriculture, In fact, the book written by such a person also has advantages, that is, it is more pragmatic, this book is also very appropriate and realistic, as I want to talk about the growth of professional soldiers from the heart of the process.
Here’s another tip: To see if a boss is pragmatic, take a look at what kind of holiday gifts are given out.
You shouldn’t waste other people’s time
Introduction to the author at the beginning of time, due to a lack of sense of responsibility, to write your own code caocao is submitted after the test, the result is obvious, not only to sell to the customer’s scold, the author is directly lost his job, and this led to his next work more carefully or even a lifetime deep-rooted recollection, But in fact, such things happen repeatedly. When I read this paragraph, I believe that I will have a lot of resonance, and deeply realize how much trouble and harm my actions can cause to others.
Your time is just as important as anyone else’s! Your time should be treasured, and of course you shouldn’t waste other people’s time. But there are exceptions to the rule. If it’s urgent and unimportant, it’s best to get it out of the way as quickly as possible.
Stick to your boundaries
If you are trying to protect your own face and break the bottom line, the consequences will be terrible. If you are always in the habit of writing bad code and don’t care about the feelings of other readers, then you are constantly creating garbage in the garbage dump, and the final result is: “Look, he wrote the junk code again”, the word is like the person, the code is like the person, I believe many people will have the feeling of teasing the junk code, but the personal principle is that before making fun of the junk code, I will reflect on whether I have done it in advance, if I have done it, then this sentence will be in mind (haha).
Conclusion: People who set higher standards and boundaries for themselves will continue to improve their abilities and skills, and those who are conscientious and guilty will usually go further.
Don’t do things at the expense of others
It is easy to write code that you can only understand. I believe that every developer has come across it, or every programmer has more or less come into contact with it. Here the author puts forward an important professional emphasis: people who are willing to accept mistakes and responsibilities even though they know it is inevitable. One of the more shameful things than writing junk code is having bugs that customers can find, which is something that almost everyone touches, and if you don’t, congratulations on working for a great company.
One reality is that for example, the college course selection software often “queues up” and crashes, which only drives people crazy and makes them yell at spam sites, hoping that you will never be part of the maintenance of such sites.
> < p style = “max-width: 100%; clear: both; min-height: 1em;
Software should be easy to modify
Abroad a coding rule are referred to as the boy scouts code, mean reading in their code, every exit code than before entering clean, people try to do, after deleting comments meaningless, for example, or delete some useless crap, or the simplification of some common writing, Although most people will think it is useless, the code is still garbage and has not changed fundamentally, according to my personal experience, it is a professional thinking ability to stick to their bottom line and train themselves.
It’s much harder to train your mind than it is to train your habits, and changing your mindset is often accompanied by failure and pain.
Don’t be the savior
What is a savior? The book describes a memorable case in which a software developer developed a promotional program for a store, followed by a typical “Party A requirement”, and gave a time frame of two weeks to complete. At first, the software developer thought the project could be completed in a week. When actually writing, however, found that this is a mission impossible 2 weeks, but he had been promised each other two weeks to complete, and then their crustily skin of head, can imagine as a result, not only to stay up late to work overtime everyday, code is a minimum, code quality basic similar to all night to finish a job tomorrow.
The developers in the knock out the last line of code when everything a job, however, his heart seemed to think that their savior, considered himself to save the customer, the fragile unimaginable consequences of vanity and achievement, the developer promised to submit the test, but party a suddenly say don’t need to have even forget about it, The final result was also a disaster. After the launch, the developer suddenly realized the seriousness of the problem and found that the coupons issued by the system could not be used at all. However, after the emergency logout, he found that more than 10 people had registered and applied for promotional coupons. I can’t imagine how painful it is for users to check out with a coupon that promises nothing or works.
The above story illustrates a simple programmer rule: We’re not creating the world, we’re serving humanity, and the sense of accomplishment and vanity doesn’t count.
Coding trap
If half of the book is not written by the author, the other half is written by the author’s experience. The author has a lot of personal advice (surprisingly, it is quite practical as a foreigner). Here is what I remember more deeply. When is junk code written
Code with emotions
Different from the anxious code below, code with emotion refers to deliberately coding to divert attention when one is in a bad mood. Some people may think it strange, but people will actually do a lot of strange actions when they are in a bad mood or in a bad state.
Bad code
Bad code is about to finish their task write code, although do not deny that some people here energy better, in the evening and night divergent thinking building code, but for most people, writing code more often during the day is not easy to get wrong, not only easy to get a bad code to scold, And over time, it can make the coder lose responsibility and guilt. So remember to keep your promises and set your boundaries so you don’t get bogged down by bugs you write.
Anxious code
In a bad mood or fire when writing code, this time may be missing some key changes because of the test, it may even be a key part of write or less leakage, so don’t write any code when the mood is bad, and do something important in the early time of the day, not let time delays.
Find ways to overcome your bad mood, eliminate distractions and calm yourself down.
Flow zone (Sage mode)
Flow area usually appear in the case of coding for a long time, when the person in the case of long time code written code usually have a lot of loopholes or negligence, the explanation of the book is highly focused when coding will feel consciousness was collapsed, but at this point is similar to the “two ear not smell out of the window, read only sage with books” feeling. This feeling of shallow meditation also has subconscious movements, and this is when your computer usually slacks off.
This is also a state that TDD is easy to get into, where testing by coding tests by doing so can end up in a state of invincibleness, as if it can do anything.
So be careful to enter the flow zone, the best way is to use a timed rest mode.
conclusion
It’s also highly recommended to read the author’s unpretentious text when you’re annoyed or stressed out about work, rather than being teased by colleagues: “Look, he’s texting himself again!” .
Write in the last
It’s also a good book to read as a casual book.