Be consistent
- > Be consistent
- Order of Lines/Elements Is Important
- Balance Planning/Researching With Action
- Sometimes in Order to Understand You Must Do
- When Teaching/Explaining Focus On the Main Topic
- Get Good at Gathering Information From People
- Be lazy (performance tip)
- Do breadth first thinking
- You will always solve it
Being consistent is important.
Use the same name for that thing, everywhere. Don’t call it something slighty different every time you refer to it.
If you use a certain style/naming/etc convention, stick with it throughout your code base.
If you use a certain idiom/pattern, stick with it, don’t use another idiom/pattern in some other places unless it gives you significant advantages.
Consistency significantly lowers the mental friction of your code base.
Even if you are doing someting not-so-good. At least we can expect you do it everywhere.
Each little “variation” of something that you do, adds a unique “mental item” to your code base. The more “variations” you have (i.e. the more inconsistent you are), the more “mental items” your code base has, thus the heavier its mental friction.