vijairamcharan

Yep, you are so right. I understand that it is not for everybody. I have met engineers who really want to be a specialist. But what if 80% of your workforce is full stack? IMO that adds so much flexibility and thus the power to create and ship things for your customers.

Absolutely! Not only did we find that we can hire full stack engineers who take full responsibility for an application end to end. We even had front end JavaScript engineers that were kind of determined that full stack was impossible to pull off. Fast forward a few months an he is now working on the GraphQL service using apollo-server and AWS Lambda. And super happy with it. That was super nice to see.

Cool good to hear! Your comment makes me thinks of ScrumBut. Where you use a large part of something, but add a twist to make sure in fits your team or use case. Makes perfect sense.

Hi! Vijai, author of the article, here. Curious to learn if you recognise anything in the journey as described in the article. Are you or your company using this stack?

Used it before, would use it again / would not use it again. Or heard of it, would like to learn it / not interested?

I will hang around here to catch any feedback / thoughts / opinions.