Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I both agree and disagree with her sentiments here. Not in a right/wrong sense, but just what I found works for me.

I agree with having helpers to understand how tooling works. Any resources that increase understanding of how to use a tool to it's full capability is productively beneficial. (Hat-tip to anything that unpacks all the `curl` switches.)

Here's where I have disagreement: an old boss of mine once said "don't worry about the tricks of the trade; learn the trade." That's very contextual, but sometimes understanding the core first makes the rest of it easy. And understanding the core takes both effort and increases cognitive load, so I understand why one might not go that route.

So, for me, I always try to keep a balance between trying to back my way into execution via those helpers, and recognizing when I need to take a step back and learn at a bit more core level.

Her down-to-earth approach is refreshing, that's for sure.



> Here's where I have disagreement: an old boss of mine once said "don't worry about the tricks of the trade; learn the trade." That's very contextual, but sometimes understanding the core first makes the rest of it easy.

Seems like you might agree more than you realize! From TFA:

> And much like when debugging a computer program, when you have a bug, you want to understand why the bug is happening if you're gonna fix it.

It sounds a lot like "don't worry about how to fix the bug; learn what the bug is."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: