This seems to be a general set of guidelines for developing web apps/APIs and it somewhat overlaps with the recent HN post “Tackling Webdev as a Bioinformaticia

This seems to be a general set of guidelines for developing web apps/APIs and it somewhat overlaps with the recent HN post “Tackling Webdev as a Bioinformatician: why is it so hard?” by Jessime Kirk: https://news.ycombinator.com/item?id=23100002 https://news.ycombinator.com/item?id=23100002 I don’t find this set of guidelines useful; it seems too Python/Django/12-Factor/BizModel specific. Web, Mobile, and Cloud has changed the world but every set of guidelines seems to start with a toolchain/language and then solves the same problems within that scope. For instance, a more generic set of choices might be: 1. static site vs dynamic 2. custom DNS domain vs 3rd party 3. github.io vs CDN vs PaaS vs IaaS 4. APIs: auth, payments, email, notifications 5. Front end framework 6. Backend architecture 7. Storage: BLOBs, files, rows, columns 8. Client platform: web, mobile, library etc.