I want to get into API´s whats a good starting point?
Posted by Impressive_Suit_2963@reddit | learnprogramming | View on Reddit | 24 comments
as i said i want to learn web protocols and inter-process communication but when i try to find a starting point i get lost in the endless Abyss, my friend recommended i C# using .NET since i have a background C type languages but even then it feels endless
Asleep_Wrangler_7789@reddit
REST APIs are pretty solid starting point 💀 just pick one language and stick with it for while, switching around makes it worse
Tricky-Isopod2742@reddit
Haha, this way you'll understand nothing just syntax of the language (e.g fetch for js)
fiddle_n@reddit
Think you missed the point. They aren’t saying just learn the language (at least I hope they aren’t saying that) - but rather, stick with one language for the projects you do, rather than jumping around different languages at the beginning.
Tricky-Isopod2742@reddit
Oh, then yes they are right. Thank you
FigStunning252@reddit
You’re getting overwhelmed because you’re trying to learn the whole ecosystem instead of just starting small.
If your goal is APIs, you really only need to focus on a few core things first:
Don’t try to “learn .NET” as a whole. Just learn enough to build a simple API.
Start with something like:
No database, no auth, just in-memory data. Test it with Postman or curl.
Tricky-Isopod2742@reddit
What do you already know?
Impressive_Suit_2963@reddit (OP)
thanks for advice, i have an understanding of TCP/IP but id call it cursory (as much as they thought it in university & what I've read on the side) when i comes to these subjects i basically know nothing. As to what i know in general its C++, HTML, CSS and PostgreSQ trying to expand my knowledge as i saw i was severely lacking to say the least
Tricky-Isopod2742@reddit
Alright, then what's your goal?
Impressive_Suit_2963@reddit (OP)
I want to use what i have to build something more then just a university project, 2 things that i have in mind is a small messaging app or a forum where people can post their study materials, but these are just hair brain ideas to practice. I want to learn how i can build these pipelines and how inter-process communication works (i know its really broad thanks for bearing with me)
acnicholls@reddit
I’d suggest LinkedIn Learning or Pluralsight. Search for the topics you’re interested in “building pipelines in github actions” and “inter-process communication in c#” or whatever the languages/platforms are.
Before either of those tho, search YouTube, there is a lot of content already freely available.
Tricky-Isopod2742@reddit
That's a great idea. I'd recommend (if you have time) to write it from scratch in C/C++, this way you'll gain 99% of knoledge that so called web devs don't even dream to have
IoriMikazuki@reddit
Start with consuming APIs before building them. Grab a free public API, something like the weather API or a Pokemon API, and just try to fetch data from it using whatever language you already know. Don't worry about understanding everything yet, just get data to appear on your screen. That first successful response hits different and makes everything click faster than any tutorial.
Once that feels comfortable, then start building your own simple API. One endpoint that returns some data you made up. From there everything else, authentication, databases, proper structure, builds naturally on top of something you already understand.
Your friend's C# and .NET recommendation is solid for learning the concepts properly since it's opinionated enough to teach you good patterns without too many choices overwhelming you early on. Just don't try to learn the framework and the concepts at the same time. Learn what an API actually is first, then learn how .NET does it.
Effective_Promise581@reddit
Start with something very simple. Like a call that returns the time or some basic piece of data. Then build from there. There are many languages you can use. Maybe Python would be easiest to get started.
barockok@reddit
Pick one API you actually want to use (weather, GitHub, Pokemon, whatever) and build the smallest possible thing that calls it. Forget REST theory until after you've made one curl request work and gotten JSON back. Once you see a real response come back, the abstractions click way faster than reading docs in advance. Postman is nice but raw curl teaches you more.
Express-Channel-1686@reddit
pick one public API and try to actually build something with it. github API or openweather are good starters. forget tutorials. you learn way more debugging a real call than reading 'what is REST'. the auth, rate limits, and error handling parts are where APIs actually click for most people.
Tricky-Isopod2742@reddit
Hey!
I guess you shouldn't listen to your friend, because that's not true. The lang doesn't matter.
I'd recommend to understand the OSI model and then TCP/IP.
What I did was to create my own http(s) library to practise this stuff without any kind of abstraction.
Good luck!
dkarlovi@reddit
If they want to create a web API, going for OSI is a "to bake a cake, first you must create the universe" style approach. Those are important when you're already comfortable with HTTP and similar app level protocols and now want to understand the plumbing better.
Tricky-Isopod2742@reddit
Well, for me is always better to see the big picture and then learn the details
dkarlovi@reddit
Agreed, but I'd argue going on networking doesn't help with building APIs, you just need to think about "HTTP request in, HTTP response out" and that's enough networking to get started. I've working with web developers with 10+ YoE who never got past that.
If you're learning to play a guitar, start by trying to play a part of a very simple song you like. That gives you a very tangible goal to work toward, you don't get bogged down with music theory and amps and whatever, that will only make you want to quit.
Tricky-Isopod2742@reddit
Not at lunch, but then they are not developers but just users. Yes I agree with you about the guitar abstraction. But in addition when you learnt how to play that part of a song you wouldn't be able to go ahead of this
Express-Level4352@reddit
API is quite a broad term, so could you clarify what you want to do/learn? What kind of project are you interested int?
C and C# aren't really similar.
Impressive_Suit_2963@reddit (OP)
You`re right sorry for the confusion, I have an idea of what might be useful like RESTapi and some websocket stuff but as to a project i could build i really don't know how much i can accomplish, a messeging app is the first step and the easiest i think
EliSka93@reddit
Your friend is wrong on the similarity of C and C#, however C# is a pretty good language for APIs.
The newer-ish MinimalAPI approach in .Net gets you pretty far pretty fast - you have to understand the language a bit though.
Chaoslordi@reddit
I recommend reading content like https://restfulapi.net/ and try to build a simple crud API with the language of your choice, be it C# or whatever