When it comes to debugging, I know of an excellent, top-notch guide for general debugging tips, tricks, and techniques. It's "The Pocket Guide to Debugging" by Julia Evans, available at wizardzines.com. I think it's geared towards more junior devs but there are some expert-level techniques in there that I wasn't even aware of until I read it. I'd highly recommend checking it out, and all of Julia's work for that matter.
I haven't always been a proponent of the "build first" mentality, but I agree with it wholeheartedly. Another way to put it might be "just do it". Or, as the Taoists would have it, "wei wu wei", which translates to "do 'not-doing'".
The latter may sound confusing, as a lot of the concepts in Taoism don't translate well. In my mind, "wei wu wei" generally means to act without attachment to outcome, to take action in accordance with your nature or instinct without pontificating endlessly about this or that choice or consequence. In that sense, I think it applies perfectly here.
I've been guilty of ignoring this principle at my own peril. As you know, I tend to pontificate and ruminate and navel-gaze quite a bit when it comes to getting things done, especially on new projects. I think tonight I'll do not-doing instead, and start my own newsletter.
Everyone is guilty of navel-gazing at times. Even the best doers let "what ifs" get in the way of doing. I wrote this as much for myself as general advice for other doers.
I hear you, I do the same thing writing advice for myself in that way. Any advice for achieving that "just do it" mentality? Is there some magic ingredient or secret to getting going? Or is it just a matter of putting one foot in front of the other?
I'm sure it's different for everyone. For me, I often run into situations where my instinct is to validate an idea before building. I get into a mindset of trying to convince other people that an idea has legs.
That process can be frustrating because the more people you talk to the more they try and pull you in different directions. It can feel like you are just spinning your wheels trying to please everyone.
Then there is this wonderful aha moment where you realize "wait a minute...I don't need anyone's approval here. I can just build it and see if it works!"
I'm not saying you should intentionally silo yourself and ignore external input. Feedback is great. Just don't be blocked by needing someone to give you the go ahead.
When it comes to debugging, I know of an excellent, top-notch guide for general debugging tips, tricks, and techniques. It's "The Pocket Guide to Debugging" by Julia Evans, available at wizardzines.com. I think it's geared towards more junior devs but there are some expert-level techniques in there that I wasn't even aware of until I read it. I'd highly recommend checking it out, and all of Julia's work for that matter.
I haven't always been a proponent of the "build first" mentality, but I agree with it wholeheartedly. Another way to put it might be "just do it". Or, as the Taoists would have it, "wei wu wei", which translates to "do 'not-doing'".
The latter may sound confusing, as a lot of the concepts in Taoism don't translate well. In my mind, "wei wu wei" generally means to act without attachment to outcome, to take action in accordance with your nature or instinct without pontificating endlessly about this or that choice or consequence. In that sense, I think it applies perfectly here.
I've been guilty of ignoring this principle at my own peril. As you know, I tend to pontificate and ruminate and navel-gaze quite a bit when it comes to getting things done, especially on new projects. I think tonight I'll do not-doing instead, and start my own newsletter.
That's great to hear!
Everyone is guilty of navel-gazing at times. Even the best doers let "what ifs" get in the way of doing. I wrote this as much for myself as general advice for other doers.
I hear you, I do the same thing writing advice for myself in that way. Any advice for achieving that "just do it" mentality? Is there some magic ingredient or secret to getting going? Or is it just a matter of putting one foot in front of the other?
I'm sure it's different for everyone. For me, I often run into situations where my instinct is to validate an idea before building. I get into a mindset of trying to convince other people that an idea has legs.
That process can be frustrating because the more people you talk to the more they try and pull you in different directions. It can feel like you are just spinning your wheels trying to please everyone.
Then there is this wonderful aha moment where you realize "wait a minute...I don't need anyone's approval here. I can just build it and see if it works!"
I'm not saying you should intentionally silo yourself and ignore external input. Feedback is great. Just don't be blocked by needing someone to give you the go ahead.