Communication should almost always be asynchronous. Meetings should be avoided whenever possible.
When meetings are required, their effectiveness can be judged by the standard deviation towards the ends of the emotional spectrum. Anticipate and embrace heated debates. Strive for inspired jubilee. Be wary of muted tones - oft indicators of time wasted.
Working too hard, for too long, precedes burnout; plan accordingly.
A smack of honesty to the face is better than a knife of deceit to the back.
Recognition, even seemingly minor, can go a long way. After all, some people will work for shiny stars on a website. However, reward should be in proportion to input, and generosity not lost to greed.
Understand your data model. Keep it clean and maintain it well.
Delivering requirements pays bills. Good design and architecture pays dividends.
Most software projects will benefit from a benevolent dictator, but if they stop delivering value, don’t be afraid to fork them.
Adaptation is natural - embrace change. Never stop learning and refine your work when time permits.
Embrace the outliers; the deviators; the delinquents. They are the keys to success - but you’ll have to find the right doors to open.
Leverage the larger software ecosystem as much as possible, but remember to be eco-friendly - give back, be sustainable.
Understand that code reviews are about reviewing the code, not the individual. Criticism should be looked at as an opportunity for improvement.