Re:How to start a company with no free time
by annekate on Friday November 18, 2016 @04:23PM
(#12990205)
"If I don't give myself permission I perceive all of that time as wasted just trying to get the package to do what it does and I need it to do so that I can forget it and move on." Wow this is really insightful. Also, the best and most reliable engineers I've worked with are very meticulous about reading the docs. They end up down less rabbit holes and it saves time in the end.
Re:How to start a company with no free time
by jimbokun on Friday November 18, 2016 @06:41PM
(#12990956)
Right!
Yes, there is a cost to writing code instead of using a pre-existing solution. But there is also a non-zero costs to using pre-existing code!
In the end, using the pre-existing code will be a win in most cases. But reading docs is not nearly as much fun as reading code, so the emotional and procrastination barriers can be higher.
A common case for me is 'use this library/package to complete the task to do this thing', I want to write the code that uses the package, the package API is opaque, it speaks in a language that makes sense if you have been playing with a dozen different similar packages, it isn't going to be useful for any other project there is something about this project that makes this package a requirement.
I've come to recognize that I have to give myself permission to read all the docs on the package, and then read large chunks of the discussion amongst enthusiasts of this type of package, then read the original docs again, and contextualize what they say into what I need to do in order to get the package to do what I want. If I don't give myself permission I perceive all of that time as wasted just trying to get the package to do what it does and I need it to do so that I can forget it and move on.
So painful.