The body of the article gives some good tips for organizing and maintaining code, but it frames it in a way that would suggest these are the best practices, and that's it. The points given are just the tip of the iceberg taught in a typical Software Engineering 101 course in university. There's no reason to reference Google here, none of these points are original. SE is an academic field with 50 years of publishing, and while most of it is pretty stale today, it is weird to lead a discussion on it completely disregarding the body of knowledge we already have.

The introduction is also weirdly phrased, as the process of SE doesn't start with writing code - that's putting the cart before the horse. SE starts with thinking about what you want to solve, and how you can and want to solve it. Coding should probably come after these processes.