Polyglot, autodidact. OSS author and contributor. Addicted to writing code, seeking my next 'fix'. Love communicating with an audience whose eyes don't glaze over when I get to the 'good parts'.
ProTip: If you're not under the gun of an urgent deadline. It doesn't hurt to take a few weeks to marinate on how the API should be structured.
IMO, the mark of a really well-written project is one where the API rarely -- if ever -- changes.
Historically, JS has been pretty bad about this b/c there was no way to define public vs private API endpoints prior to ES modules. Either way, the 'best' projects were those that seemed to 'just work' despite constant improvements and frequent feature releases.
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.
ProTip: If you're not under the gun of an urgent deadline. It doesn't hurt to take a few weeks to marinate on how the API should be structured.
IMO, the mark of a really well-written project is one where the API rarely -- if ever -- changes.
Historically, JS has been pretty bad about this b/c there was no way to define public vs private API endpoints prior to ES modules. Either way, the 'best' projects were those that seemed to 'just work' despite constant improvements and frequent feature releases.