Content about writing API for versatility as principle

[Yemaneberhan-Lemma]

No description provided.

[netlify]

✅ Deploy Preview for axelerant-engg-handbook ready!

Name	Link
🔨 Latest commit	1301f38
🔍 Latest deploy log	https://app.netlify.com/sites/axelerant-engg-handbook/deploys/659e9c977eda690008dfff50
😎 Deploy Preview	https://deploy-preview-154--axelerant-engg-handbook.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[axelabhay]

Hi @Yemaneberhan-Lemma, to me the Future proofing & Versatile API sections seems sharing similar ideas. Please adjust the contents if you see applicable.

[Yemaneberhan-Lemma]

Hi @Yemaneberhan-Lemma, to me the Future proofing & Versatile API sections seems sharing similar ideas. Please adjust the contents if you see applicable.

@axelabhay, The main reason the last paragraph appears redundant is because I was trying to mention all the key characteristics of a versatile API. Though, I made changes to the paragraph.

[hussainweb]

I reflected on this and am of the opinion that this is too specific to be a principle. I do get the intent on how the word "API" can be applied here but it is still not generic enough.

If I were to rephrase this in a generic way, it would be "Separation of concerns". And I think that is also not applicable as a principle. I mean, it is hardly useful to say "Separate your concerns". I think this is more of a contextual topic under "Common areas of concern".

[Yemaneberhan-Lemma]

Noted

[hussainweb]

Closing this as it has been a long time. Reopen if required.