Test-Driven Development is an excellent way of writing code but many people push back against it. To convince your team to adopt it, lead by example. Don't preach. Let the quality of the code your wrote with TDD talk for itself and only suggest TDD when people ask about it.
My current thoughts on which merge strategy to use on GitHub. "Create a merge commit" will help you make sense of how code changed over time without removing the option for a high-level overview of the changes on the main branch.
How to establish a workflow that minimizes unscheduled, unstructured communication and maximizes focus and productivity.
My latest post on mobile.blog explores two simple conventions Automattic uses to remove the need for synchronous meetings in their app release process.