How to Design Great APIs - Parse Developer Day 2013

แชร์
ฝัง
  • เผยแพร่เมื่อ 5 พ.ย. 2024

ความคิดเห็น • 34

  • @jwavess
    @jwavess 9 ปีที่แล้ว +1

    I've watched quite a few videos on api's, read articles, books, asked in the Q&A forms, and everyone was giving me the wrong impression, until now! Thank you man, this was great!

  • @bkboggy
    @bkboggy 7 ปีที่แล้ว +1

    I want more talks from this gentleman. What a fantastic talk.

  • @stefainex99ming
    @stefainex99ming 9 ปีที่แล้ว +5

    great in-depth talk about designing API! thanks

  • @hann3r
    @hann3r 10 ปีที่แล้ว +2

    Awesome explanation of APIs, examples, and in-depth analysis!

  • @AhmedAdelRadwan
    @AhmedAdelRadwan 8 ปีที่แล้ว +18

    Well, that escalated quickly, Parse is shutting down in Jan,2017.

    • @jinxblaze
      @jinxblaze 5 ปีที่แล้ว +1

      atleast the talk still stands :)

  • @Ugotsta
    @Ugotsta 11 ปีที่แล้ว

    This talk is both funny and informative and thus totally entertaining. I love it! One great example of good API design I came across recently is Paper.js. Great API and great docs that are rife with relevant examples.

  • @vladanulardzic5859
    @vladanulardzic5859 4 ปีที่แล้ว

    Brilliant presentation ! Really, really brilliant. Keep on !

  • @zaccomusic
    @zaccomusic 4 ปีที่แล้ว

    amazing content
    I hope you keep update :)

  • @nbamj88
    @nbamj88 10 ปีที่แล้ว

    kudos for the speaker Kevin Lacker

  • @AlNewkirk
    @AlNewkirk 11 ปีที่แล้ว +1

    Saw this video a few days ago. I love watching tech presentations. The presenter here has real stage presence. Yeah, also, I categorically disagree with almost everything said.
    Specially, the notion of "Intuition-Driven Development". Intuition-Driven Development is the reason why I end up with screws and fixtures left over when I try to assemble Ikea furniture without reading the manual.

  • @YoungGrizzly
    @YoungGrizzly 6 ปีที่แล้ว

    He took shots at the PHP string library...TRIGGERED!

  • @nedvedyang
    @nedvedyang 9 ปีที่แล้ว

    nice talk, agree on the laziness and doc parts.

  • @johnlocke5363
    @johnlocke5363 8 ปีที่แล้ว

    did he mention that he works for parse?

  • @carelspoor8816
    @carelspoor8816 8 ปีที่แล้ว

    Laziness is beautiful, that’s why mathematicians call a ‘lazy’ proof ‘elegant’.

  • @i_am_ashutosh
    @i_am_ashutosh 7 ปีที่แล้ว

    That's really Informative. Thanks :)

  • @netaneld122
    @netaneld122 7 ปีที่แล้ว

    saveInBackground and saveEventually don't sound like good names, I can't quite guess the difference between them

  • @AbhishekVaid
    @AbhishekVaid 11 ปีที่แล้ว

    Very good tutorial

  • @lucasterable
    @lucasterable 11 ปีที่แล้ว

    Well, laziness is the most powerful emotion for most human beings after all

  • @adityasanka
    @adityasanka 6 ปีที่แล้ว

    Great examples

  • @jee_warriorz
    @jee_warriorz 11 ปีที่แล้ว

    great talk..

  • @AlNewkirk
    @AlNewkirk 11 ปีที่แล้ว

    The blurb about Perl is funny, seemingly true to people that don't know any better, but ultimately kinda lame. E.g., The length function in Perl is a function not a method, because everything isn't an object, and as-such, expects a particular input (string), not whatever you want.
    Protip: RTFM.

  • @donnaryan4939
    @donnaryan4939 11 ปีที่แล้ว

    Thank you

  • @TheMraptor
    @TheMraptor 11 ปีที่แล้ว

    lame comparison... CONTEXT is very important thing in Perl... the presenter took LAME approach instead of LAZY approach...

  • @Mr4thdimention
    @Mr4thdimention 6 ปีที่แล้ว +1

    This is not a very deep analysis of API design.

    • @gappergob6169
      @gappergob6169 4 ปีที่แล้ว

      What did you expect from 30 minutes talk?

  • @shihailuo6755
    @shihailuo6755 7 ปีที่แล้ว +2

    没国人?

  • @James-op6ls
    @James-op6ls 10 ปีที่แล้ว +2

    To laziness!

  • @mohammedalzamil7191
    @mohammedalzamil7191 4 ปีที่แล้ว

    TH-cam

  • @StuartLoria
    @StuartLoria 11 ปีที่แล้ว

    Funny

  • @rschmidtzalles
    @rschmidtzalles 7 ปีที่แล้ว

    4 years later (2017), parse has been shut down.
    Probably for "bad API design". What an irony