akshaynathan
An introduction to end-to-end testing
Shorten Your CI/CD Cycles
Building a CLI in Typescript
Partnering Effectively with Designers as an Engineer
The Five Most Common Bugs You Should Be Writing Tests For
Towards a Fully Programmable Inbox
Decision Fatigue Is Killing the Engineer
Ruby 2.7 New Features in Production: Pattern matching and numbered block args
Delightful Goodbyes: Fully Deleting User Data
Getting Started with the Sorbet Type Checker in Rails
Running Effective Bug Bashes That Your Team Won't Dread
Fail Fast and Fail Often: Handling API Errors at Scale
We're working on a Gmail integration right now so we'll pull in any emails you actually read automatically, and let you label/organize/snooze/bundle/reply all without leaving the feed.
Our eventual goal is to replace Gmail for any work/transactional emails. We're taking the approach of doing that one integration at a time, and providing a richer experience.
We do think that there's a world in which both of them are useful though. The problem as we see it right now with Gmail is you may receive a notification about a pull request or whatever, but you can't do anything with it and the data gets stale. Monolist will keep it in sync, and let you approve/merge/comment on it inline so you don't have to switch between 10 apps.
Monolist Founder Series – CoinTracker
Monolist integrates directly into the tools you use and surfaces things that you can act on inline in the app (missed Slack mentions, Asana tasks, Calendar invites etc.). We're actually working on a GMail integration right now and would love to hear from the community what kinds of Inbox features we could replicate successfully.