He/she is a full-code full-stack developer who now works in no-code development.
He/she can deliver a fully functional production ready MVP in 4 days, not 4 months.
He/she can organize the development workflow for the stakeholder group so its members can better participate in the project, especially when it is not a technical group.
He/she will build product components in a way that “makes sense” for the product to work at the MVP level and be expanded later, for example, data modelling will be done in a way that any full-code developer or architect could look at the database and understand its structure.
He/she will stick to basic principles like DRY and the use of a style sheet to keep development more atomic and consistent.
He/she will reinforce the need for testing the product at various levels, from UI/UX, through data consistency, integrations and performance.
In the case of poor performance, he/she should be able to interact with the no-code platform team either in-house or from a vendor to check what could be done to improve performance beyond the capabilities offered by the no-code settings interface, for example, moving the instance to a different region/AZ, caching, etc.
He/she will configure the no-code platform in a way that it favors that particular product development and its roll-out into production.
He/she will join stakeholder roadmap review meetings to discuss how the MVP could evolve from that specific point from a technical perspective. Suggestions could be given in the sense of:
- evolving the product within the same no-code platform
- migrating to a full-code product by developing new features and integrating them to the no-code legacy
- integrating the product to online services that could provide the value stakeholders expect to see
He/she will transition his/her work to a new team or to professionals that will continue the work from where he/she has left it.