Hello.
What would your advices be concerning the architecture, planning
and crafting a new library - sdk for public use?
Hello.
What would your advices be concerning the architecture, planning
and crafting a new library - sdk for public use?
For further actions, you may consider blocking this person and/or reporting abuse
I like to start with the README (README driven development), define the API of the library I'm going to build and how Is going to be used (basically document it), then I just code it to follow that API.
E.g. I'm going to create a JS module to sum N amount of numbers, so I create a README and define it's going to be used this way:
Then I code it so it works as expected.
Actually, I discussed this with one of my developers in a podcast a few months back: MousePaw'dCast Ep 2: Accents and APIs (skip to 14:50, which is the start of that part).
One takeaway (of many from that conversation): please document the API! (Also see Your Project Isn't Done Yet.)
Thank you for your response. I will checkout those links as soon as possible :)