We talked a lot about Monod lately, but we did not share the way we were using it at TailorDev. Today, we want to let you know how you can use Monod on a daily basis as well as a few tips and tricks about it!
Two months ago, we announced the upcoming venue of crick.io, an online service that helps you track and report your activity. As we did our homework, we decided to benchmark our idea with the Running Lean method. At first, I was skeptic, but curious.
After a successful first session, we are happy to share the results of our second Le lab session, which happened a week ago at TailorDev. We worked a lot (a bit too much to be honest) on Monod to make it usable in real-life.
As former academic people, we know exactly what research looks like in (French) universities or national institutes. Despite our past, since the moment we have created our company, we lost our legitimacy in front of our peers. This open letter intends to explain our motivations.
Since we decided to open source Watson — our internal tool to track and report our activity — we had great feedback and contributions from the community. Some contributions are not documented nor shipped with Watson, so let’s enlight them today!
When Julien and myself decided to start TailorDev, our main wish was to create a remote-first company, even though we were only two. In this article, we describe the tools we chose, as well as the workflows and the processes we decided to follow.
In a previous blog post, we introduced a React-based application called Monod, our Markdown editor. During our Le lab session, we spent half a day optimizing loading time of Monod. This blog post sums up our work on improving initial loading time of React components.
Subscribe via RSS