Re:Programmer problem solving sequence: should it be like this?
by alphamerik on Monday February 28, 2011 @09:28AM
(#2271270)
It amazes me that people would put coworkers second. Those people can be very annoying because I feel like their only purpose is to leech knowledge rather than do any real work. OP's list is the lazy programmer's list. Taking breaks to think about the problem is good, my order of operations is something like:
Even going to IRC can be dangerous, was told to read the f-ing kernel source when trying to ask questions about the darwin kernel API documentation once.
[ Parent
| on HN ]
Re:Programmer problem solving sequence: should it be like this?
by TillE on Monday February 28, 2011 @09:58AM
(#2271383)
I like that order. Don't waste your time or anyone else's if it's a simple problem that can be solved with a direct Google search. But definitely think before asking.
Re:Programmer problem solving sequence: should it be like this?
by wccrawford on Monday February 28, 2011 @09:00PM
(#2273905)
I go to coworkers when I think it's a problem they've dealt with before. Otherwise, it's much easier to just Google it.
I would put 'Think' first on my list though because I really enjoy it, and tend to do it whenever I can. Google comes in when I hit a dead end thinking.