Nice post! I feel that this stack is indeed a good starting point for almost any new project. And not just as a starting point, but often something you can stick to until you get very specific requirements.
Cool that you wrote down your thoughts after really having seen it work time and time again for new projects that deliver business value in a professional context.
I agree that having the same programming language and concepts on web, mobile or on the server really helps. More often than not developers get a label (frontend or backend developer) and then stick to that comfort zone, while it's so much more interesting to be more all-round.
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.
I love how JavaScript / TypeScript allows a full stack developer to use the same language all over their stack, nice example about how it was even possible to move logic from the web to authentication layer by simply copy and pasting!
I’ve found another effect of using a single language is that it becomes easier to build teams, there’s less speciality needed and communication and sharing of ideas within a team becomes easier. Is this something you’ve seen too, and do you see the other parts of the Sjgar stack (e.g. due to the size of the React and AWS community) help with this?
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.
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.
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.
Cool that you wrote down your thoughts after really having seen it work time and time again for new projects that deliver business value in a professional context.
I agree that having the same programming language and concepts on web, mobile or on the server really helps. More often than not developers get a label (frontend or backend developer) and then stick to that comfort zone, while it's so much more interesting to be more all-round.