Talk in English - US at php[tek] 2024
Short URL: https://joind.in/talk/565ec
(QR-Code (opens in new window))
I've got plenty of engineering experience. I'd inherited an SDK at Vonage: so what? It's just like any other code, right?
Except, of course, it isn't. Coding an SDK is a -very- different animal to tame. You have API versioning to consider, razor-tight semantic versioning to stick to and a -ton- of banana skins presented to you for everyone to see if you fancy a Laurel and Hardy tumble.
Coding for a product used by developers is an interesting ballgame, so after doing it for two years I'll go through how to make sure you delight your engineers instead of getting into another fine mess.
Comments
Comments are closed.
Not only was this a solid talk born from real-world experience, but it touches on both general design patterns and library design that make this applicable to a much larger audience than attended this talk.
So my feedback would be to tweak the title and abstract, and make slight tweaks to the content, to still focus on SDKs but note that normal libraries work similarly, 'cuz more people need to see this!
Really solid talk, even if the voice work was...well, something.
Echoing Ian's sentiments, this talk could easily be re-branded to address all sorts of libraries (not just SDKs).
Engaging speaker and pretty funny. Learned a lot about SDKs.