13
How do ya'll choose what tool to get things done with? (programming.dev)
submitted 1 year ago* (last edited 1 year ago) by andioop@programming.dev to c/learn_programming@programming.dev
3 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments
[-] zmrl@lemmy.zip 3 points 1 year ago

For the first question, I would base my search on things like the extensiveness of the results, authentication, pricing, usability, etc. If you don't have any specific criteria right away, try making a few calls and playing with it to see if it will be what you needed. Some APIs I'll find its missing this one thing that makes another api a better choice. This is something you'll get better at with experience.

And no youre not expected to know all the tools, there are about an infinite out there. Generally youre expected to be familiar with some of the tools of the job but knowing more can't hurt either. Take things one thing at a time and make some simple project with what you've learned. That's how I do it anyways, but everyone is different.

this post was submitted on 19 Aug 2025
13 points (100.0% liked)

Learn Programming

2242 readers
1 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 3 years ago
MODERATORS
Ategon@programming.dev
JaumeI@programming.dev
bugsmith@programming.dev