developerjackHowdy weekly readers!
This post comes drafted from #AlterConf in Melbourne and published (exhausted) from my couch at home. As a result I have just three interesting reads to share with you this week and they are short and sweet and to the point.
How to answer questions in a helpful way
This excellent read speaks to coaching and knowledge sharing in a constructive and encouraging manner. It’s an excellent addition to any variation of ‘Asking good questions’ that you have probably read only now the boot is on the other foot.
Read the post.What API Providers Can Learn from the Lego Developer Experience
Cristiano Betta’s post is an excellent exploration of celebrating success in developer experience. It’s the delightful experiences that make a platform or API memorable (and its the confusing or ambiguous experiences that will stick with a developer for even longer). While I’ve linked to the original post on Cristiano’s blog this post first came across my radar this week when it was summarised in this programmable web article of the same name.
Read the post.Why on earth would developers want to write documentation?
The excellent Heidi Waterhouse published this post as an extension of a talk she presented. Her point to use docs as the test cases for QA checks is an excellent idea! I’ve started using doctest in my python modules and it forces me to write intended usage docs prior (or during) the implementation and I’ve seen the notable difference it has made to my code. Onward on doc-ward I say!
Read the post.Open source forks and splits
It’s been an arguably tumultuous week or so in the open source web with hhvm announcing it won’t target/support php7 (it’s forking, again…), WordPress backed away from ReactJS and then over the weekend Facebook shared they’re renouncing ReactJS’s patents BSD+patents license in favour of MIT. And naturally that means we’re all guessing what that means for WordPress’s announcement. I mean it’s all been very busy in the FOSS web world. I recommend giving each post its due time to read and process as they each make an excellent point and commentary on the state of the web.
Until next week!
@developerjack
