Startups tend to grow and expand, and successful startups tend to propagate this progress. I see this variety of possible ways mainly from the engineer's perspective, from the point of striving to create technically reliable, automated, simple to use, and supportive applications, which can be called "alive." I am calling them "alive" here because I see those apps as living beings with their own lifecycles. And now let me elaborate on how this quite abstract idea can be applied to the real world.
I became a member of my current team at the moment when one crucial question had to be addressed. The question was "How are we going to make our product easier to develop and use?" Originally, the company agreed to deliver integration with a large third-party system, but there was one obstacle: it is hard or even impossible to integrate the system into the larger one (and I am talking here about medical, financial or similar areas) when the product is a mere web app, without a backend (AWS Lamdas are not included here) which should provide an easy way to scale and customize the app, without CI/CD flow, without profound data store (which DynamoDB is not) to effectively aggregate and analyze data (which is becoming a crucial requirement) and, moreover, without a clear and easy way to administer the application itself (and I mean here a customer's onboarding mostly). Considering the fact that this integration is extremely determinative in terms of clients' and the development company's success, all these impediments were defined as a "dragon" that should be defeated to make our product "alive."
from DZone.com Feed https://ift.tt/2JoU7Zy
No comments:
Post a Comment