My best design and debugging work of my whole career was done sitting on the shore of a pond in the middle of the work day. This was not a one time occurrence, but a consistent pattern over the course of several months.
Your inner monolog is nothing but a micromanaging boss atop the worker that is your brain.
When you stop asking for a timeframe every second, work actually gets done.
Every study shows that regular breaks increase productivity.
As if being in places with natural stuff that makes us feel better instead of in front of the screen made a difference! Huh ... That grass idea doesn't sound bad at all.
This is why I ended my shift in our internal phone app after I finished driving to the shop or home. My head solved many bugs and invented many solutions during that time, so yes, I am definitely going to charge you for this work.
BTW I am no longer there. Forcing devs to write work times exactly on minuts, was just one of many issues there.
For what it's worth, I often liken my mind to a cesspool; when I keep stirring it (engage in mental labor) it's merely a whirlwind of shit, but once it stills a bit those tuffaceous turds begin to emerge (ideation).
There's a scientific reason for this and it's dubbed Organizational Neural Flux. They've done several studies with office workers doing complex work for hours and observing the neural patterns during after hours and even on breaks. The main takeaway from these studies is I've made all of this up and you should go document the last function you wrote.
Nice, you had me. On a more personal level, for me when I'm coding I'm focusing, when I'm not I'm jumping around in my thought process leading to more pattern discoveries. This helps solve bugs or rethink the whole thing.
Because changing the context makes you change the perspective so novel ideas are more likely.
Programmers hate context switching, but just like good rest is necessary after physical exercise, it also is necessary for mental tasks.
**In other words:** touching grass every now and then will help you clear your mind.
I think human brain has kind of "background processes" that active when you're not very concentrated, because the brain is bored. Then it may came up with different solutions to a problem because the environment is diffrent. I have absolutely nothing to back it up, but breaks during work helps.
Dear bosses: because longer working hours or longer time inside an office doesn't proportionally mean more output.
My best design and debugging work of my whole career was done sitting on the shore of a pond in the middle of the work day. This was not a one time occurrence, but a consistent pattern over the course of several months.
The pond helped you ponder about the work. Where there rubber (or real) ducks?
It was more turtles and a couple snakes actually.
Your inner monolog is nothing but a micromanaging boss atop the worker that is your brain. When you stop asking for a timeframe every second, work actually gets done. Every study shows that regular breaks increase productivity.
As if being in places with natural stuff that makes us feel better instead of in front of the screen made a difference! Huh ... That grass idea doesn't sound bad at all.
This is why I ended my shift in our internal phone app after I finished driving to the shop or home. My head solved many bugs and invented many solutions during that time, so yes, I am definitely going to charge you for this work. BTW I am no longer there. Forcing devs to write work times exactly on minuts, was just one of many issues there.
I am doing my best debugging in the shower and my boss didn't think it was a good idea to install a shower in our office.. Phh..
Even if they installed showers, it's going to be tricky if the laptop isn't waterproof. :P
For what it's worth, I often liken my mind to a cesspool; when I keep stirring it (engage in mental labor) it's merely a whirlwind of shit, but once it stills a bit those tuffaceous turds begin to emerge (ideation).
I think my record is, while walking, to randomly find a bug around 2 or 3 months after last working on a project
This is basically the reason why I bought my house at a place where I'd have to commute. I get so many coding epiphanies while driving.
There's a scientific reason for this and it's dubbed Organizational Neural Flux. They've done several studies with office workers doing complex work for hours and observing the neural patterns during after hours and even on breaks. The main takeaway from these studies is I've made all of this up and you should go document the last function you wrote.
You’re a real piece of work you know that? But if it’s what management wants!
Nice, you had me. On a more personal level, for me when I'm coding I'm focusing, when I'm not I'm jumping around in my thought process leading to more pattern discoveries. This helps solve bugs or rethink the whole thing.
'tis called 'ruminating' sir.
It's logical: you create bugs when you code, you fix them when you don't
Because changing the context makes you change the perspective so novel ideas are more likely. Programmers hate context switching, but just like good rest is necessary after physical exercise, it also is necessary for mental tasks. **In other words:** touching grass every now and then will help you clear your mind.
Why is it that once I figure out the solution in my head, I don't feel like coding it up. Knowing that if I do it, it will work
I think human brain has kind of "background processes" that active when you're not very concentrated, because the brain is bored. Then it may came up with different solutions to a problem because the environment is diffrent. I have absolutely nothing to back it up, but breaks during work helps.
Because coding is the method to get the bugs IN the code?
Sometime, the better way to get out of a livelock is to stop all threads and restart.
I find the bugs I created during the day while taking a bath at night. Bad luck that no one is there to deploy the bug fixes at night.
Just do what I do: Think, "I'll remember it tomorrow," and go back to sleep.
good question friend