How much time are you spending in meetings? And are you sure you needed to be in these meetings?

If you can draw, this approach will work really well! But, even if you are like me and cannot really draw, it will still save you a ton of time if you manually drew out the UI pages to share with your development team.

While it would save time (which is priceless for everyone, not to mention smaller startups where it is even more valuable!) to use UX designs created for the Web for Mobile Apps, and vice-versa, it is hardly ever possible (if a seamless User Experience across devices is at the top of your priority list).

Well, as technology improves, we get smarter as humans. But, so do bots. There's any number of things you can, and should, do to ensure your app is not hit with bot (aka: fake) sign ups.

We use our own product (obviously!) to give us a federated view of all the projects that our ecosystem comprises of but at a code repository level, we use GitHub's Project feature to manage repo-specific issues. Here's how we do it.

While it's important to not be bogged down by terminologies, it is also imperative that there is consensus within any given team so there is no confusion.

It is hard to overstate the value strong typing brings to the table, especially in the context of teams that move real fast (and have fun doing so)!

If you upgraded to heroku-20, and ran into SSL errors, this quick video (less than 2 minutes is very, very quick for someone for who brevity ain't always a forte!) may help you. It took me 3 hours to figure this out, and if I can save you that time, it would be worth it, right!

Refactoring your code periodically is a good idea. But, when you do, exercise some caution.