Here's an interesting tweet from our friend Felix Krause. Of course it applies to our whole industry, not just iOS development and not just tools like fastlane.

It's hard to solve this problem because documentation systems generally don't allow updates to be easily seen. That famous saying comes to mind, "If a tree falls in the forest and no one is around to tweet about it, does its Klout score increase?" πŸ˜‚ Obviously I'm being a little sarcastic there, but the discussions that happen after a post is published are part of the reason people blog.

But there's another thing to take into consideration too. Official documentation isn't always the top search result, and web search is how people solve problems. Take for example this popular stack overflow question which appears much higher in search results than the actual documentation for the feature. Even this tweet from Felix appeared higher in most of the searches I did when playing with this. As long as people find the information, does it matter how?

Well yes, it does. Documentation gets spread out all over the place and the open source libraries and tools we have are harder to use. Documentation is also a really great way to quickly judge the quality of a library/tool. It's important.

So to finish this week's rather random thought, I'd just like to echo the original point that most documentation for open source libraries and tools is also available for editing. In many cases you'll also find that maintainers are even happier to see documentation pull requests than code ones! It's also a great way to get involved in an open source project you love. So what are you waiting for?

Getting involved in open source doesn't always need to be about writing code.

Dave Verwer  





Business and Marketing


Sponsored Jobs

And finally...