I've heard the phrase "Think high, work sober" and I basically agree with the premise.
If you're on a deadline or have to immediately release production-ready code, it's probably not a good idea to put yourself into a state of "impairment" before working. You should be as clear as possible to do your best and most diligent work.
However, if you're merely thinking through an issue or approach, changing your perspective and mind-space might put you into a more creative flow. It's likely that you'll make connections or go down a different path than you would have otherwise. This is ideal when you're on your "own time" and have the time to implement any ideas you might have later.
I did the "think high" thing quite a bit when I was younger. I'm not much of a smoker these days, but I appreciate how it "trained" my brain. Not long ago, I was watching how the water flows in a creek - just zoned out on it. I got back to my desk and refactored a massive golang backend into 4 micros tethered by rabbit topics that can hold up to any chaos monkey.
From watching the water.
It's the same way things would click in my think high days, and it still happens pretty often - what, 15-20 years later.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've heard the phrase "Think high, work sober" and I basically agree with the premise.
If you're on a deadline or have to immediately release production-ready code, it's probably not a good idea to put yourself into a state of "impairment" before working. You should be as clear as possible to do your best and most diligent work.
However, if you're merely thinking through an issue or approach, changing your perspective and mind-space might put you into a more creative flow. It's likely that you'll make connections or go down a different path than you would have otherwise. This is ideal when you're on your "own time" and have the time to implement any ideas you might have later.
I did the "think high" thing quite a bit when I was younger. I'm not much of a smoker these days, but I appreciate how it "trained" my brain. Not long ago, I was watching how the water flows in a creek - just zoned out on it. I got back to my desk and refactored a massive golang backend into 4 micros tethered by rabbit topics that can hold up to any chaos monkey.
From watching the water.
It's the same way things would click in my think high days, and it still happens pretty often - what, 15-20 years later.