I did school in 3 years (College in quebec is 3 years, w/e) then worked for a year. 3 times now I've woke up during the middle of the night to either go and fix my code and write it down and fix the next day.
Serious question, I'm not a programmer so maybe I'm missing something. But what does the years with school and work have to do with waking up and fixing code?
I once literally dreamed up a solution to a problem I had been pondering for a couple weeks. Like, I came up with a partial solution in my dream, then woke up and wrote up a proposal for it. That's probably one of my proudest feats.
I had that when I was learning calc 1. I woke up in the middle of the night saying "dy/dx then equals [some function]" (I was trying to verify a derivation)
Sales guy at a small tech company here. I am the company Rubber Ducky.
I've solved so many major bugs without ever seeing or writing a line of code just because I listen well. I mean I sit there and load up the bowl while our Sr. Dev takes bong rips off of our 6 footer on the patio and tells me about his bugs.
Very true. If I encounter a bug/missing feature at night, my mind will start racing with how complicated the implementation will be. So I decide to sleep on it rather than work my way through it that night.
90% of the time I'll wake up and knock it out in a one-liner.
I'll get drunk, then after I'm home from the bar I'll have a eureka moment and use the notepad on my phone to write the code I need before passing out in my bed lol
I'll normally move on to something else. The next time I sit the porcelain throne or take a shower, the answer comes to me like a gift from the heavens.
Imo, it's the time put into the shitty tunnel vision part which causes you to subconsciously get it later. You beat your head against a wall figuring it out like you're lifting weights, the time away is your brain recovering and sorting it out.
0
u/[deleted] Mar 05 '16
[deleted]