Read source code and unit tests. Don’t bother documentation cause it’s outdated. Dig into the core, look where data goes in and where it gets out. Everything else is just a wrapper.

  • 4
    I like this. This is what I do, but I never thought of it like that.
  • 2
    Truth. But documentation accelerates this. You are correct most documentation is lackluster.

    I very much appreciate good docs
  • 1
    Uhmmm maybe starting with docs? At least you know what the duck the thingie is supposed to do?
  • 4
    @dmonkey I dunno, by the time I've found something via Google, I probably know what it's *meant* to do, docs don't tell me what it *actually* does.
  • 2
    @atheist fair enough, but I'd still read the docs before reading the source
  • 1
    More often than not, you stumble across small hidden gems and easter eggs that way as well..

    Sometimes you do end up writing code around an API that was never documented and just gets changed without any prior notice tho.
Add Comment