4. Ditch team building gimmicks (see #3 for what's important).
I'd say gimmicks aren't going to save you, but consider morale events and other subtler stuff to help build team cohesion. Things like going to lunch regularly together, for example. When people are more comfortable with each other it makes it a lot easier for them to collaborate, rely on each other, ask each other questions, mentor each other, etc.I think the important aspect is for people to interact in different contexts. Lunch is already different to the usual office context. Playing games is great in general (board games, paintball, rpg, team sports, whatever).
In that way, I would rather stay there as savy engineer for as long as it holds.
What impresses me the most are,
8. When you need a bad guy/gal, you're it. 9. When you need a good guy/gal, your people are it.
It is natural for good leader to think for engineers. But also thinking in the position of users/productivities wise is important.
16. Always do the right thing.
Some of these I either misunderstand or contradict each other, e.g.: 1. Be nice.
8. When you need a bad guy/gal, you're it.Being nice means not being ruled by your emotions and not slipping into pettiness. If you have a disagreement with someone, do it nicely. Give people the benefit of the doubt. Etc.
But on the other hand, sometimes it's necessary to do or say things that are unpopular or difficult to accept. The difference is doing the unpopular thing that is necessary vs. being mean because you can't control your temper or you're just a jerk or you're trying to "win" some stupid technical argument. Don't be a jerk, don't yell, don't belittle people, but absolutely call people out on their shit when necessary.