OP should bold the headers. If he doesn't understand how to make an article readable, it makes me question whether he understands how to make code readable. A

OP should bold the headers. If he doesn't understand how to make an article readable, it makes me question whether he understands how to make code readable. Anyway, the fact that he thinks these need to be stated is interesting in and of itself. Points 1-3 just come down to judgement that you develop as your career progresses. You start to know when a problem should be googled, when a library is necessary, or when something should be rolled on your own. There's no way to feel this in your bones without practicing and running into what it feels like when it's been violated. Making quick fixes vs. permanent ones should be dictated by how corner-case the fix is and the time that would be consumed to make an abstraction to handle it cleanly. It's about striking a balance between over and under engineering. Again, this comes down to judgement and experience. It's seemingly easy to understand this on an intellectual level. Getting on an experiential level is another thing altogether. Ignoring warnings is an obvious no-no.