9 books programmers need to Read in 16 years – The Sex Slap Face Guide

The book covers listed here are typical anti-patterns, but they’re so common that they’ve become commonplace

Copy and paste Programming Essentials from Stack Overflow

The programming book you need to read the most. Ironically, really have such a little book on Gitbook (tra38. Gitbooks. IO/essential – c… This thesis discusses code Licensing issues, Code Attribution, and Code Selection

 

The only way to write JavaScript properly is to rewrite it every week in a different way! It’s actually nice to have a community that’s constantly evolving and self-revolutionizing, but only if you accept that reality. Keep learning and enriching yourself, and grasp what is truly permanent and enduring through change. For more on why the JavaScript community is so vibrant and restless, see the article JavaScript Ecology that never stops churning



There are so many reasons not to write unit tests!! Single testing has many benefits, such as early detection of problems, protection for refactoring code and updating code logic, easy integration (because single testing starts at the bottom of the detail), documentation (detailed single test cases are fine), Design oriented (test-driven makes it easier to design elegant, low-coupling code) you should have enough unit test cases ready for the following code

  • The ones that are constantly being revised
  • The ones that have a lot of complexity
  • Those important features/often viewed



You said you’re going to start refactoring this spaghetti mess of callback embedded callback code next week? ! – Are you fucking kidding me? Delivery is important, but it’s not an interface that lets you write bad code.

Solve problems in a way that is not consistent with design principles/difficult to maintain/adjust/robust/aesthetically pleasing.

For example, if a pipe connection starts to rust and leak — • rearrange the entire plumbing system into pipes without joints, which is called refactor • Replace the rusted pipes as they are, which is called proper fix • Remove the pipes and put them back together with impervious tape, It’s called “monkey patch”. It’s called “hack”. It’s called “plugging the leak with gum” and “pouring it with cement”. Called dirty hack

A Dirty hack isn’t always a bad thing, unless you have a basin, welding, pipe tongs, a girlfriend, new plumbing and impervious tape, and the plumbing system is about to die anyway.



Are you still spending time fixing those tickling bugs? You’re a 10X engineer, how can you make a mistake? It must be someone else’s fault. It’s their phone, browser, it must be!! A lot of engineers do solve problems like this, some special cases, some cases that they didn’t think about in the design of the code, he just makes it go away.



### From Entry to Mastery: Resume-Driven Development So feel free to pick up this book and start reading.

This is the case with performers, who often need to pick and choose to do what seems like a big deal, but don’t want to roll up their sleeves to get into the details and do the dirty work. They also often put on their resume that they were primarily responsible for the XXX project (in fact, they probably participated in some of the functions of the limbic system). Or a resume that says, without much modesty, that you are proficient in XX (which is probably how you wrote HelloWorld). Or a resume that says “skilled in XX message queues” (which is probably just reading a shallow blog post).



### Writing Code that Nobody Can Read: The Definitive Guide

If you can’t read it yourself, even better!

They have very low requirements for the system code. The attitude of “it can run, why do you care so much” makes it difficult for the subsequent colleagues to promote the follow-up work. Such as there has always been puzzling error, swallowed like is it a black hole, which let the peripheral module developers feel aggrieved, once positioning in like a walk in the dark opaque sewers, horrified gusts and diffuse the bad smell in the air (code logic is round, variable name is look not to understand the exotic, almost no log log print out, etc.)



Master Search for Error Messages

There are always ways to make these problems disappear online!

If your project relies on less than 72 NPM packages and your code is so lonely, pick up this book and start reading. Those online strangers always write good code, don’t they?

These people are not reinventing the wheel of the tradition to the limit, may be to use a function method is add a huge dependent libraries to code in the warehouse (spend time on installation depend on follow-up, probably more than the simple function method to write), more not even dependence for download is similar to packages. Json, Bundler, requireders. TXT, etc., allows subsequent collaborators to copy dependencies directly back to the production machine (orz… PS: Use features like PIP Freeze, NPM Shrinkwrap, etc