Good software engineers can be found anywhere, and embracing remote working enables you to tap into that global pool. But just because you *can*… does that mean you *should*? In this talk I’ll go through some dos and don’ts, talk about some pitfalls, and hopefully guide you towards doing remote the right way. I’ll include some stories that draw on my experience working in technical recruitment for clients who have been on both sides of the do\/don’t scale, as well as Automattic’s decade-plus experience as a fully-distributed company.<\/p>\n
Length: 10-15 min
\nStructure:
\n– Hello (who I am)
\n– What remote is (flexible working)
\n– What remote isn’t (easy or simple)
\n– Do
\n— Treat everyone as remote
\n— Default to async
\n— Document all the things
\n— Build a culture
\n— Get together in person
\n– Don’t
\n— Just pick up the phone (unless…) (you then document it for everyone else)
\n— Assume
\n— Hold people to 9-5
\n— Treat it as an experiment
\n– Conclusion<\/p>\n","protected":false},"excerpt":{"rendered":"
Good software engineers can be found anywhere, and embracing remote working enables you to tap into that global pool. But just because you *can*… does that mean you *should*? In this talk I’ll go through some dos and don’ts, talk about some pitfalls, and hopefully guide you towards doing remote the right way. I’ll include … <\/p>\n