3 ms·
I made an async work collaboration app: https://github.com/async-go/asyncgo https://github.com/async-go/asyncgo I had been working at GitLab, pre-pandemic, for
by synu 4y ago
I made an async work collaboration app: https://github.com/async-go/asyncgo https://github.com/async-go/asyncgo
I had been working at GitLab, pre-pandemic, for several years and I saw how writing things down was almost like a super power to enable async work. If you start with time zone distributed teams, writing things down in issues/docs just becomes the natural way of working. I also saw that lots of other companies didn't really get it - and there was a leap of faith required to try it, because it didn't logically follow that if you write things down more you can have less meetings.
My idea was to build something that provided a really natural place to write things down, and I built and tried to sell AsyncGo as a place for making decisions in a written way. You'd set a topic, a context, and a due date, and then the magic would happen. In theory. The problem I had was that I couldn't find anyone to take the leap and try it. Companies who were interested in async already had some similar process, and the ones who really needed help writing things down didn't get it and I never found a way to communicate it to them clearly.
In the end I shut down the hosted version and put an MIT license on it. I don't regret it exactly, I learned a lot making it, but I wish it had helped more people. There's other stuff out there now that's sort of similar, and it seems they are struggling a bit as well, so I don't think the market was really there (yet). Now I'm working on a collaboration app for regular people/teams who want to get better at making videos/streams (https://www.synura.com https://www.synura.com) and I hope to apply a lot of the lessons there.