https://www.facebook.com/tuxdaily/videos/391780458238065/&show_text=1&width=560
Every time I try out Linux
1.
Not only my program, but also myself need a stack, to put current job status, before jumping to another job. And as the stack pointer go deeper into the stack, it is likely you cannot get back in time.
2.
Jumping to other task means you dump your current working stack with full of information gathered at the same time. So normally I try not to jump out from the thing I am doing at that moment, but leave a quick memo for the task I need to visit later.
3.
If I have to jump out, then I try to catch and summarise as much as I can, and store them in a memo, or even in the code, by marking with /* HERE !! */ to come back later. I know it's quite primitive way, but useful when you get back.
4.
At times, I found other people's mark in the shared code. They left /* HERE !! */ kind of mark, and never came back, so the mark is left unfinished. And I don't have much idea about those things, so I just leave there. So the marking in the code is absolutely not a good idea.
5.
I am still looking for better way of Stack Operation in my task flow. And one thing frequently happening with me is about reading codes, when I have to jump around code segments without stack. I also looking for a better way of doing this. See Code Navigating Tool, The Human-centric one.

No comments:
Post a Comment