Get Up And Walk Around moments
-
I’m a 60 year old coder. I’ve been doing it since I was 20. I always knew I loved it, but I just realized I truly do it for the get-up-and-walk-around moment. That’s the moment when you fix a sneaky bug, or complete a demanding or tricky task/algorithm/approach. It’s so satisfying, that you can’t simply move on to the next thing. You have to get up and walk around to bask in the satisfaction. I’m chasing a get up and walk around worthy bug in a bit of embedded C++ at the moment. It’s a timer fringe case, or a variable the should be volatile, and it’s not. I’ll get it, and I’ll certainly need to get-up-and-walk-around once it’s dead. Has anyone else recognized the need to get-up-and-walk-around after a truly satisfying coding moment? Do you have other victory rituals?
Absolutely :thumbsup: a bit like how a deer shakes after having escaped danger the walk around gets the adrenalin out of the system.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
I’m a 60 year old coder. I’ve been doing it since I was 20. I always knew I loved it, but I just realized I truly do it for the get-up-and-walk-around moment. That’s the moment when you fix a sneaky bug, or complete a demanding or tricky task/algorithm/approach. It’s so satisfying, that you can’t simply move on to the next thing. You have to get up and walk around to bask in the satisfaction. I’m chasing a get up and walk around worthy bug in a bit of embedded C++ at the moment. It’s a timer fringe case, or a variable the should be volatile, and it’s not. I’ll get it, and I’ll certainly need to get-up-and-walk-around once it’s dead. Has anyone else recognized the need to get-up-and-walk-around after a truly satisfying coding moment? Do you have other victory rituals?
I usually make it a walk to the coffee machine :java:
Check out my blog at http://msdev.pro/
-
Never done it while coding, but a semicircular trot towards the net and back is a common follow-through after hitting a winner on the tennis court. :)
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
I hadn't noticed it but yeah I do get up and walk around after a big sign of relief. The thing about C/C++ is you can shoot yourself in the foot and the problem is so subtle that it takes special skills and a lot of cursing to find and fix.
The less you need, the more you have. Even a blind squirrel gets a nut...occasionally. JaxCoder.com
-
I did find this mornings beast. It was such a shot to the foot, that I'm not sure I deserve a get-up moment.
Congrats, always satisfying.
The less you need, the more you have. Even a blind squirrel gets a nut...occasionally. JaxCoder.com
-
I usually make it a walk to the coffee machine :java:
Check out my blog at http://msdev.pro/
-
Yea, but I'm out of this mornings allotment of coffee. I did spill a little while getting my last cup. I looked at the spill, wondering if I was irked because I had to wipe it up, or irked because I lost that bit of the morning's last cup.
I think it doesn't count as a full cup anymore, so you can have one more :java: Enjoy :cool:
Check out my blog at http://msdev.pro/
-
I did find this mornings beast. It was such a shot to the foot, that I'm not sure I deserve a get-up moment.
You don't get up and walk around if you shot yourself in the foot. Please be consistent! :laugh:
Mircea
-
I did find this mornings beast. It was such a shot to the foot, that I'm not sure I deserve a get-up moment.
You don't get up and walk around after you shot yourself in the foot. Please be consistent! :laugh:
Mircea
-
I’m a 60 year old coder. I’ve been doing it since I was 20. I always knew I loved it, but I just realized I truly do it for the get-up-and-walk-around moment. That’s the moment when you fix a sneaky bug, or complete a demanding or tricky task/algorithm/approach. It’s so satisfying, that you can’t simply move on to the next thing. You have to get up and walk around to bask in the satisfaction. I’m chasing a get up and walk around worthy bug in a bit of embedded C++ at the moment. It’s a timer fringe case, or a variable the should be volatile, and it’s not. I’ll get it, and I’ll certainly need to get-up-and-walk-around once it’s dead. Has anyone else recognized the need to get-up-and-walk-around after a truly satisfying coding moment? Do you have other victory rituals?
I think most of us can relate.:thumbsup:
>64 Some days the dragon wins. Suck it up.
-
You don't get up and walk around after you shot yourself in the foot. Please be consistent! :laugh:
Mircea
-
I’m a 60 year old coder. I’ve been doing it since I was 20. I always knew I loved it, but I just realized I truly do it for the get-up-and-walk-around moment. That’s the moment when you fix a sneaky bug, or complete a demanding or tricky task/algorithm/approach. It’s so satisfying, that you can’t simply move on to the next thing. You have to get up and walk around to bask in the satisfaction. I’m chasing a get up and walk around worthy bug in a bit of embedded C++ at the moment. It’s a timer fringe case, or a variable the should be volatile, and it’s not. I’ll get it, and I’ll certainly need to get-up-and-walk-around once it’s dead. Has anyone else recognized the need to get-up-and-walk-around after a truly satisfying coding moment? Do you have other victory rituals?
My moment was in a complicated mathematical computation. Was getting wrong results for about a week. Then one afternoon was debugging when I saw that a minus sign was keyed in as a plus sign. After that fix, all results became correct.
-
I’m a 60 year old coder. I’ve been doing it since I was 20. I always knew I loved it, but I just realized I truly do it for the get-up-and-walk-around moment. That’s the moment when you fix a sneaky bug, or complete a demanding or tricky task/algorithm/approach. It’s so satisfying, that you can’t simply move on to the next thing. You have to get up and walk around to bask in the satisfaction. I’m chasing a get up and walk around worthy bug in a bit of embedded C++ at the moment. It’s a timer fringe case, or a variable the should be volatile, and it’s not. I’ll get it, and I’ll certainly need to get-up-and-walk-around once it’s dead. Has anyone else recognized the need to get-up-and-walk-around after a truly satisfying coding moment? Do you have other victory rituals?
YES! and like you when in the middle of a particularly annoying problem. I actually begin fantasying about what the get up and walk around is going to be like. It is particularly fun when I have "budgeted" lets say 8 hours to fix something and have a moment of brilliance and solve in an hour or so. I almost always take an hour or so to bask in my walking around moment. I barely ever take the full 7 I have allotted myself. It is a wonderful feeling.
To err is human to really elephant it up you need a computer
-
I’m a 60 year old coder. I’ve been doing it since I was 20. I always knew I loved it, but I just realized I truly do it for the get-up-and-walk-around moment. That’s the moment when you fix a sneaky bug, or complete a demanding or tricky task/algorithm/approach. It’s so satisfying, that you can’t simply move on to the next thing. You have to get up and walk around to bask in the satisfaction. I’m chasing a get up and walk around worthy bug in a bit of embedded C++ at the moment. It’s a timer fringe case, or a variable the should be volatile, and it’s not. I’ll get it, and I’ll certainly need to get-up-and-walk-around once it’s dead. Has anyone else recognized the need to get-up-and-walk-around after a truly satisfying coding moment? Do you have other victory rituals?
Certainly! I recognize the feeling, and the action, very well. I'll take the opportunity to tell of two other ways of reacting to a victory. This was a math problem, but it might as well have been an algorithmic one: In preparation for the math finals, two of my University classmates, Jon and Berit, were solving problems from the finals of previous years. Berit was the undisputed #1 in academic results, less so in self confidence. Jon was the other way around - certainly so for the confidence part. For one problem, they got stuck, couldn't make out how to solve the problem. So rather than locking up each other's way of attacking it, they agreed to split, sit at separate tables apart from each other, trying to solve the problem alone. And so it happened that they both 'saw the light' at the very same moment. And Jon exclaimed: Boy, am I smart! And Berit exclaimed: Boy, have I been dumb! (Those who know them both, says: Right! - That is just like both of them.) After Jon told me of this episode, with a laugh, I asked Berit if it was true. She looked down, and nodded: I guess that is exactly what happened ...
-
I’m a 60 year old coder. I’ve been doing it since I was 20. I always knew I loved it, but I just realized I truly do it for the get-up-and-walk-around moment. That’s the moment when you fix a sneaky bug, or complete a demanding or tricky task/algorithm/approach. It’s so satisfying, that you can’t simply move on to the next thing. You have to get up and walk around to bask in the satisfaction. I’m chasing a get up and walk around worthy bug in a bit of embedded C++ at the moment. It’s a timer fringe case, or a variable the should be volatile, and it’s not. I’ll get it, and I’ll certainly need to get-up-and-walk-around once it’s dead. Has anyone else recognized the need to get-up-and-walk-around after a truly satisfying coding moment? Do you have other victory rituals?
Anymore I look out the window and thank God in heaven for helping me, then run off to facebook to see what the rest of the world has been up to, play some phone solitaire and just be "analog" for a while before perusing the bug log to see what one will be next on the pole.
-
I’m a 60 year old coder. I’ve been doing it since I was 20. I always knew I loved it, but I just realized I truly do it for the get-up-and-walk-around moment. That’s the moment when you fix a sneaky bug, or complete a demanding or tricky task/algorithm/approach. It’s so satisfying, that you can’t simply move on to the next thing. You have to get up and walk around to bask in the satisfaction. I’m chasing a get up and walk around worthy bug in a bit of embedded C++ at the moment. It’s a timer fringe case, or a variable the should be volatile, and it’s not. I’ll get it, and I’ll certainly need to get-up-and-walk-around once it’s dead. Has anyone else recognized the need to get-up-and-walk-around after a truly satisfying coding moment? Do you have other victory rituals?
BBar2 wrote:
a variable the should be volatile, and it’s not
Ah, memories of Microsoft 'C' 6.0 back in the MS-DOS days. They didn't implement the
volatilekeyword, and their optimizer would move what looked like loop-invariant code outside a loop. Made for a dandy interrupt service debugging experience. I had to disable optimization entirely.BBar2 wrote:
Do you have other victory rituals?
I do the get up and walk around bit too. I wander around for a bit and then come back and make really sure I've fixed the problem.
Software Zen:
delete this; -
Absolutely :thumbsup: a bit like how a deer shakes after having escaped danger the walk around gets the adrenalin out of the system.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
GuyThiebaut wrote:
a deer shakes after having escaped danger the walk around gets the adrenalin out of the system
I see the same thing in my greyhound. After he's run zoomies for a couple of minutes, he walks around shaking and blowing for a while. Even at almost ten years old, he can still get up to around 25 mph (racers at their peak can do 40+ mph).
Software Zen:
delete this; -
GuyThiebaut wrote:
a deer shakes after having escaped danger the walk around gets the adrenalin out of the system
I see the same thing in my greyhound. After he's run zoomies for a couple of minutes, he walks around shaking and blowing for a while. Even at almost ten years old, he can still get up to around 25 mph (racers at their peak can do 40+ mph).
Software Zen:
delete this; -
My moment was in a complicated mathematical computation. Was getting wrong results for about a week. Then one afternoon was debugging when I saw that a minus sign was keyed in as a plus sign. After that fix, all results became correct.
Reminds me of when I took the computer graphics class in college. I had been debugging a 3D clipping algorithm for a week, and it kept failing in a weird way. One night, after I'd been in the lab for almost 40 hours straight (yes, I was insane back then), I went out to the hallway with a listing and stretched it out on the floor. I looked at it for a couple hours, chain-smoking (I was also stupid back then) the whole time. I finally got up and started walking the hallways. After about ten minutes, the thought occurred to me to check my variable names against the original algorithm. I had used the names the algorithm used, which were unfortunately single lower-case characters. In one place, I had typed a 'b' instead of an 'h', both of which were variables in the algorithm. Go look at your keyboard; I'll wait.
Software Zen:
delete this; -
Of course, I'm talking about the dog, 2nd fastest land animal on Earth (1st is the cheetah). They can accelerate from a standstill to 40 mph in six strides. Retired racers make great pets; "world's fastest couch potato" is a common description :-D .
Software Zen:
delete this;
