Most think that what makes remote work great is to work from a beach, or an idyllic place sipping on cold drinks.
But the best environment is the one you set with the right processes and toolset.
242 karma · joined September 11, 2007
Contact me via jpincheira at gmail.com
Most think that what makes remote work great is to work from a beach, or an idyllic place sipping on cold drinks.
But the best environment is the one you set with the right processes and toolset.
[1] https://github.com/react-native-community/discussions-and-pr...
You end up getting rid of meetings — people gathering in real-time :)
@samanthalee233 That's great! I tried to log in to suggest the change, but it did not work with my normal Gitlab account.
Sync/real-time communication is not needed for all the processes in a remote team, and you should go async by default and only use sync for cases where you _really_ have to get together. This is how companies Gitlab [1] have really become successful in doing remote work.
A remote team can be successful by using async/non-real-time communication, especially when you're pairing it with an async platform like Standups which is built from the ground up to support the async comm style. I wrote a blog article about how async is determinant to make remote work "work" within your team/org [2].
[1] https://about.gitlab.com/handbook/communication/
[2] https://standups.io/blog/how-async-communication-can-help-yo...
I'd keep sync processes limited to as few as possible, and default everything else to async.
[1] https://about.gitlab.com/handbook/communication/
[2] https://standups.io/blog/how-async-communication-can-help-yo...
Not being in the same place, at the same time, not having the kitchen conversation by the coffee machine is something that _can_ be worked around by using the right tools and implementing the right processes where those types of conversations can happen.
But to do sales, talking to users, I have to do it on the manager's schedule, with the typical slots within a day calendar schedule.
So in short, I do things on consecutive days:
* to code, I do maker's schedule.
* to sell/talk to users, I do manager's schedule.
I'm feeling like writing on the topic as well, as it can be valuable for other solo founders too. I struggled a lot in the beginning when building Standups.
This is the main reason why we at Standups don't support video recording on Safari[2]. They are on the same level as Microsoft Edge, which also does not support video recording. It's hard for me to understand they did not want to catch up with the main players.
For us at Standups[1] RN has been just instrumental. As a small team, we are able to ship features, just like Discord, vertically all across the stack. Having 1 language in common (TypeScript) all across your stack is the best for small teams/startups. We share most of our code.
For those of you interested in how to share code vertically using TypeScript[2], check out this guide by Bruno Lemos, super helpful, great value there for startups and especially tech solopreneurs.
[2] https://dev.to/brunolemos/tutorial-100-code-sharing-between-...
By the way, if you're a remote team, I'm happy to talk with you guys and get in touch [2], love what you built. Sick landing page.
[2] jp at standups.io
I coded myself a whole mobile version of our platform[1] using React Native and know the pains! It's fantastic that you could automate this and make it a SaaS company.
Hope you enjoy the podcast, there are some gems there about SEO. Ruben Gamez —the person in the podcast— was also technical and learned his way around SEO.
Mind sharing what your product is?
On the same topic, today I was listening to a podcast [2] titled "Getting traffic to a new website without blogging" which is excelent to match using Divio's guide.
[2] https://podcasts.apple.com/us/podcast/episode-344-getting-tr...
As a remote team, implementing the async communication style will allow you to never have to depend on fixed calendar meetings. No need to have to organize everybody together in a room, at a specific time, to just make a decision.
I wrote a bit about how to do this within a remote team, which is a guideline into how to set a basic async comm process for a remote team. Hope you find it helpful:
https://standups.io/blog/a-basic-guideline-for-async-communi...
Parse.ly also just released their new landing page all done with Gatsby.