So I got a technical job and don't want to talk too much about it because everything is ~*PrOpRiEtArY*~ and I want to respect that. So far they've been good to me, but I hope at some point I can learn an acceptable way to continue to blog about tech in a specific way. I'm referring to my job as "data choreography" for now and maybe someday will be able to expand on how those systems work.
IN THE MEANTIME.
I've always heard about "libraries" that are used for programming languages. To myself I think: "Holy sh*t, there are already so many instruction manuals to look through, how could I possibly go through a whole library?"
Like with most things I'm afraid of, it doesn't seem to be too horrible.
Library (programming) definition: a collection of precomiled routines that a program can use.
So say you're working with Python and want to download a library for it. You download Python if you don't already have it, then you download a library, Pandas, for instance. It comes with an easy enough Pandas Instruction Manual just like anything else. Being good at this programming stuff if all about reading the instruction manual, then having the guts to experiment. And, I guess, also finding the time to do such things. Another little library example, Apache Arrow. This and the more famous NumPy are downloaded to get data types for Pandas.
Then you use these things to make instant charts, like the one below:
Pretty neat, and I never really understood what a "library" was for and what it would be used for.
