> most of the time the complexity for me using some frameworks, libraries, or tools has nothing to do with code but instead in the prerequisites for using them. The authors of some tools make certain assumptions about your knowledge of the whole ecosystem around the tool or supporting tools.
Somehow I feel better knowing there's at least one another person on the planet losing 6 hours at time for `just installing X piece of tech`.
Worst thing I had to figure out was that the node package on raspbian is originally related to some radio thing and I had to symlink node-js to node to make it work.
It just goes to show the utter most importance of good documentation. Good as in `human readable` not `logically correct sentences à la man GIT`.
I also felt better when two days later I met a buddy of mine (who is much smarter than me!) for lunch, and immediately he ranted about how he wasted an entire day getting Foundation's command line tools to work. He repeated nearly word for word the same issues I faced!
I'll chuck my hat in the ring here too... got a new MBA recently and it came with Yosemite which introduced one or two curveballs when setting up for web development.
Somehow I feel better knowing there's at least one another person on the planet losing 6 hours at time for `just installing X piece of tech`.
Worst thing I had to figure out was that the node package on raspbian is originally related to some radio thing and I had to symlink node-js to node to make it work.
It just goes to show the utter most importance of good documentation. Good as in `human readable` not `logically correct sentences à la man GIT`.