I'm 82% through my intermediate level coding textbook (pretty sure it's intermediate) and there's still no mention of "SDKS". How recent is this term. Trying to get recent (aka relevent) textbooks in coding is more difficult than any other skill I've acquired I think.
So "SDKS" are my new "Abstraction".
Pretty much everything (if not everything) you see, or the average person sees on a computer screen is an "Abstraction"
coders will say things like 'then you can abstract it out', and you'll hear about abstraction everywhere, but it's kind
of meaningless in that everything is. It's used colloquially in specific contexts to communicate something, but
it almost always means 'write some code to do a thing'. Only recently am I starting to understand it in the context of code...and it's always used in a "this is the way to not deal with some other BS" context.
So yea, SDK's I get in theory, and I expect I'll be using one specifically soon for my project. It's simply "A software development kit"....but to be frank there's a reasonable chance it's simply an "uncompleted distribution" (or package). It could simply be a "UD", or "UP". But the culture has run with "SDK".
Software still moves more quickly than anything I've seen.
#dev #python #nix
Login to reply
Replies (1)
I'd define an SDK as a library of abstractions for working with a system.
A good example is Android development. Anyone writing apps for Android will use the Android SDK. This SDK abstracts away the low-level system calls needed to make the phone hardware do what the developer wants it to do. Rather than writing a bunch of Assembly, the developer can just, for example, call something like `sendNotification()` and call it a day.