At one of my companies we had a long running Google meets video with a dedicated large tv that was very close to all the in-office engineers. This was good for emulating the good parts of an office while remote. I have used tools like gather.town to improve on this tooling in full remote workplaces. It is a magical feeling to be remote and alone for years, and then through Gather.town be able to walk up and poke your coworkers for a chat.
You covered a lot of the most important stuff with a focus on the documentation and making knowledge as declarative as possible. Imperative knowledge acquisition (where you need to analog step through lots of convos and get information from peoples’ heads) is the main blocker to good remote work I’ve found.
It sounds like you’re already doing it, but usually whatever the founder/leader does gets mimicked by everyone else. So if you write meh docs, everyone else is gonna write bad docs. Any remote-positive aspects you want to be mimicked must be adopted by you, else one hand is fighting the other.
I would like to read more from you on the “automation and tooling” as well as “leverage” sections you mentioned at the beginning of your article.
Thanks for the response! We tried gather.town for a bit but then it got a bit tiring haha. Thanks for the feedback though, will write a part 2 covering more around the automation and tooling :)
I wish although I'm not an engineer anymore so can't write about something that I don't have knowledge in myself. This article will serve the basics for any kind of blockchain though. Blockchains are simply state machines that are authorised via cryptography. Focus on the basics and you'll see them everywhere!
FYI we have a daily updates Slack channel where we lost what we've done for the day. Especially useful to know what to look at for those engineers who are putting stuff on staging but you aren't actively on the Linear task for, so you know what to look for and give feedback.
I generally link to the Linear issues when posting, including the Changelog posts
We do that with contractors although FTEs find it a bit annoying (they do weekly updates instead). Better to just check in Github what happened tbh since that's the source of truth.
Yes please write a second one! I have worked remotely at startups for most of the last 7 years and all of these ring true to me.
I'm glad! Any other tips or things you've found that work well?
At one of my companies we had a long running Google meets video with a dedicated large tv that was very close to all the in-office engineers. This was good for emulating the good parts of an office while remote. I have used tools like gather.town to improve on this tooling in full remote workplaces. It is a magical feeling to be remote and alone for years, and then through Gather.town be able to walk up and poke your coworkers for a chat.
You covered a lot of the most important stuff with a focus on the documentation and making knowledge as declarative as possible. Imperative knowledge acquisition (where you need to analog step through lots of convos and get information from peoples’ heads) is the main blocker to good remote work I’ve found.
It sounds like you’re already doing it, but usually whatever the founder/leader does gets mimicked by everyone else. So if you write meh docs, everyone else is gonna write bad docs. Any remote-positive aspects you want to be mimicked must be adopted by you, else one hand is fighting the other.
I would like to read more from you on the “automation and tooling” as well as “leverage” sections you mentioned at the beginning of your article.
Thanks for the response! We tried gather.town for a bit but then it got a bit tiring haha. Thanks for the feedback though, will write a part 2 covering more around the automation and tooling :)
Can you write an article on how to become a Stacks Developer.
I wish although I'm not an engineer anymore so can't write about something that I don't have knowledge in myself. This article will serve the basics for any kind of blockchain though. Blockchains are simply state machines that are authorised via cryptography. Focus on the basics and you'll see them everywhere!
+1 please write and part :-)
FYI we have a daily updates Slack channel where we lost what we've done for the day. Especially useful to know what to look at for those engineers who are putting stuff on staging but you aren't actively on the Linear task for, so you know what to look for and give feedback.
I generally link to the Linear issues when posting, including the Changelog posts
We do that with contractors although FTEs find it a bit annoying (they do weekly updates instead). Better to just check in Github what happened tbh since that's the source of truth.
* correction "where we list what we've done"