I am sorry but you didn't convince me. I can agree that for some complex projects with a large team an API layer can provide some useful guardrails, but for 95% of the web apps, I believe that an API layer is just an unnecessary burden.
In my original comment I mentioned long term and there is our different in mental approach and probably our professional engagement.
long term
There is no argument against the context you describe but I consider them under the classifications of "quick and dirty", "fire and forget".
I'm not trying to convince you. Just sharing experience: ) :) . I probably wouldn't have convinced my younger self as well.
I won't bet you're older than me. :)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am sorry but you didn't convince me. I can agree that for some complex projects with a large team an API layer can provide some useful guardrails, but for 95% of the web apps, I believe that an API layer is just an unnecessary burden.
In my original comment I mentioned
long termand there is our different in mental approach and probably our professional engagement.There is no argument against the context you describe but I consider them under the classifications of "quick and dirty", "fire and forget".
I'm not trying to convince you. Just sharing experience: ) :) . I probably wouldn't have convinced my younger self as well.
I won't bet you're older than me. :)