Using External Code Libraries

So programming is one of the hobbies I have.  I don't consider myself a good programmer, but I'm a decent one (or so I think).  Most of what I have done lately is pure Objective C and Swift stuff (mostly Obj C but I have toyed around with Swift).  I have written apps that were published in Apple's iOS App Store, but I have never depended on my programming ability for my actual income.  Everything I do now is mostly hobby stuff, but it may one day end up leading to a new app.

One thing I have always strived to do is not to use any external libraries or resources outside of official APIs.  I always try to write my wrappers, classes, and everything on my own.  Even though I know there are TONS of libraries and code examples on GIT Hub, StackOverlfow, etc, it still makes me uncomfortable.  I'm worried about unexpected bugs I have to troubleshoot, code no longer being maintained, code I didn't write becoming obsolete, etc.  This can make for a frustrating experience.  I mean what happens if your app bases itself off of a library someone random maintains, they decide to stop all work on it and pull it offline, and now you are up a creek without a paddle (see the whole Parse situation, even though they at least tried to help the situation).

Recently I've actually thought about using two different external libraries because I honestly don't have the time lately to really sit and deep dive into a new topic (having a newborn baby can have the effect on you, but man she is awesome).  I want to be able to use CloudKit outside of the App Store and the only way to do is that is to use the CloudKit web services or JavaScript  frameworks for CloudKit.  Now I have NEVER written JavaScript before and honestly, didn't want to learn how. It's not that I don't think learning JS would be useful; I just have had to pick and choose what I want to learn.  I have looked at Agilebit's AgileCloudSDK and I like how it works.  I've also looked into using some sort of wrapper for the FSEvents API.  Mainly that's because I don't want to really dig into a C API.  While I would love to spend a lot of time learning everything, I just honestly don't have the time.  I'm lucky to just be able to write anything I already know!

While the apps I released in the App Store were all 100% my code and not dependent on others resources, I can see myself using a few libraries in the future.  I try to truly vet the libraries to make sure they are "future proof" and at least have source code available for me to use.  Anything closed source I won't use because I can't change something in it, and I am not sure what all it does (outside of what's documented).  

Hopefully my future does not involve using many of these libraries or code snippets.  I honestly believe buggy and bloated software has increased because people carelessly use unknown code and snippets.  Just because something works that you copied off StackOverflow does not mean it is the right solution.  Let's hope I don't get that lazy and undisciplined as I continue my coding adventures.