You've built your app and think you are good to go. But there's one more step. Deployment!

It is quite natural to feel overwhelmed when someone gives you 90 minutes and a long list of requirements. Here are some strategies that might help you be successful.

It’s sometimes compelling to try and get every question answered before you start working on coding a feature (regardless of which part of the stack it belongs to). But it may or may not be a good idea. Find the right balance. Here’s how we do it.

Well, there's a lot to learn here, and I've hardly scratched the surface. But my hope is that it at least gives you a starting point.

When I am sitting in front of my machine, I want to be coding (or doing something that I really need the machine for). Design work doesn't necessarily fall in that category for me - at least not all the time.

I knew we would have engineering challenges and that didn't bother me (having done this for a while). But what kept me awake were the roadblocks that were bound to be there that I had little clue about!

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.