[cdevs]

I've noticed a disconnect between people we bring on the team that have a heavy oop style or do brilliant things in low level code but they lack writing code for teams fresh out of college. I remember writing magic code that did convenient abstractions for me in the background when I programmed for myself but I quickly learned this sucks when I found out someone provided me with a function that doesn't follow single responsibility in a team environment. When you work in a team write for a team, I tell everyone to write for a imaginary jr developer starting the next day who's going to read your code on day one.

[nine_k]

I'd boil it down to two statements.

* Avoid magic, be idiomatic.

* If you create something even slightly non-trivial, explain it in documentation.