4 ms·
I have to agree with this. You're either writing assembly code yourself, or you're using code that was invented by someone else (and even the assembly code will
by tommymachine 8y ago
I have to agree with this. You're either writing assembly code yourself, or you're using code that was invented by someone else (and even the assembly code will have been invented by someone!). If using libraries/frameworks is something you do consistently, you can absolutely reach a state of deep work while working with them.
Libraries should help keep the flow going at a high level by keeping one from being bogged down with having to reinvent the wheel. In fact, if they didn't contribute to flow, I don't think we'd use them!
- hinkley 8y agoI think you're confusing using a library you've already been using (in which case I agree) and introducing a new library. Most people engaging in NIH aren't removing a library that is already being used in your build process. They're deciding it's easier to implement URL processing (spoilers: it's not) than to use a library that already exists. The exception to that is when the existing library turns out to be a dumpster fire and you rip it out and replace it with something else or a custom version.
- mlthoughts2018 8y agoEither way, the decision to (usually wrongly) believe that writing it all yourself is easier/better has little to do with flow.