The first thing I did when I started building Savoir was not to write code, but to plan my sprints with a tool called Codetree. I highly recommend them by the way, if you're looking for a good GitHub powered project management tool. I planned my entire feature set through epics, and I would break things down into smaller issues on a bi-weekly basis. I personally really like working in more structured environments.... - Source: dev.to / over 1 year ago

Very much agree, most projects I work on these days have components in multiple repositories and trying to coordinate work among them is challenging. We use Github Issues as a source of truth but have resorted to using third-party software on top of them to help get a bigger-picture view. Currently we're using Codetree: https://codetree.com/. - Source: Hacker News / almost 3 years ago

Because I want to assess the modern landscape of technologies that enable screenshot rendering. And I want to rethink some architectural choices I made for ScreenshotOne back at times. - Source: dev.to / 3 months ago

If you don't want to read the post and want to jump straight away into the code, I open-sourced the Tail Worker code I use for my screenshot API product. - Source: dev.to / 5 months ago

There's a market for it: https://screenshotone.com/. - Source: Hacker News / 8 months ago

I am bootstrapping html rendering API. Is it a good business? What do you think? Source: over 1 year ago

If you don't have time to implement and generate animated screenshots and deal with video streaming infrastructure, you can rely on ScreenshotOne API. - Source: dev.to / over 1 year ago