I looked for APIs to do something. I found a bunch of APIs that will do the job I want. How does one pick between them when all of them will do the job in the right language/framework?

This also made me think of another question. I’ve heard of interviews for tech jobs asking people what tools they’d use to solve a certain problem. I figure the way I’d do that is exactly how I tried to find an API. Just directly look for a tool that can do your job online, see what the options are, and only click the ones that actually do what you want. I am very entry-level (recent CS grad, wish me luck) in the learn-more-by-doing stage, and am wondering if you’re expected to have a deep knowledge of most of the tools out there or what, and how one does that.

  • NochMehrG@feddit.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Some things to check:

    • does it do what you need?
    • license
    • Who is behind it, company, org, some person?
    • liveliness? How often is it changed, released?
    • how do they handle security?
    • who is using it? Community?
    • cost (for commercial use)
    • previous release notes, what has been changed, breaking changes?
    • history, how long does it exist?