Breaking beliefs with AWS Amplify

Fondness is a bit of a loaded word in this subtitle. I was, am, and will always be fond of tech — especially the development and architecture aspect of it. However, although frontend technologies have made me curious to explore them, I have always stayed careful of not falling into that rabbit hole as the backend wonders took over.

Apart from a short stint with AngularJS back in 2015, I have no experience in fronted dev till date.

As opposed to the last week’s update — where I worked on setting up the backend infrastructure DevOps pipeline — this week I deterministically spent time in finding a similar solution for the frontend. To me it is like designing a spacecraft to safely land on the surface of Mars, as I am not familiar with frontend dev stack and best practices, let alone the pipelines.

But the push was real this time, and I am glad to have spent this week familiarising myself with AWS Amplify. It has been able to answer ‘most’ of my naive questions about approach towards building frontend and integrating the same with backend.

Some of my questions were:

1. Where to begin?
2. How to adopt modular development for reusability?
3. How to enable fellow developers for parallel development?
4. How to review and promote…