Something that's been infuriating is adding libraries to any project that I've been working on. NPM and Ruby make it all to easy to add someone else's knowledge and bad habits to your projects. I've used a few great libraries before, but recently I used a library that allowed me to raise the technical floor of my project, but also lowered the ceiling of what I could include as a feature.
Google Maps is a pretty decent API. It's easy to get started with and has some very deep features to play around with. A recent project I started working on had a strict time limit that did not allow me to learn how to build out my own implementation of those APIs in React. Enter libraries. I was up and running in less than a day. Everything was going smoothly until I needed to get into deeper parts of the API. The great library I was using started to fight me.
This is the most frustrating impotent feeling of learning something new. I could make my own tools, but it would take far too long. Since the goal is to complete a project, to ship, I've had to cobble together other code bases into a configuration I want. Sometimes those pieces don't quite exactly fit and I have to tape them together. If I had more skill I could build my own bespoke tools, but that would take me far too long. It's a complete mess and the compromise I've come to is: "I'll come back later."
Top comments (0)