I’ve always meant to write down a programming “stucklist”. It’s a list which you consult when you’re stuck. Maybe it tells you that you’re solving the wrong problem. Maybe it provides inspiration to fix the problem in a different way. Either way, when you’re under deadline pressure and your brain is dribbling out of your ears, a stucklist might just provide a way out. So, without further ado, here’s my initial stucklist:<\/p>\n
Avail yourself of more facts
\n Can you solve a different problem?
\n Get out of the office and go for a walk.
\n How can else you make the problem go away without coding a fix for it?
\n Could you make the endusers avoid the problem area?
\n Go home and do something less boring instead.
\n Look at a more general version of the problem.
\n Or consider a more specific version of the problem.
\n Is it actually so bad not to fix the problem?
\n Fix one or more of the variables to simplify the problem
\n Grab someone, say “I’m a bit stuck” and throw some ideas around
\n Get someone else to fix it (evil bonus: they have to fix the fix too)
\n Can you buy in a solution, or spend money to make the problem go away?
\n Tell your manager that you’ve hit a problem and see if you can have more time, or redistribute work.
\n Get everyone else to workaround\/avoid the problem area
\n Code a solution using a different style – recusive\/iterative, stateful\/pure, push\/pull, table-based\/computed.
\n How would you solve the problem if you had infinite memory or a super-fast CPU?
\n Can you put any supporting framework in place which makes the problem easier to fix?
\n Draw a diagram – I find it’s easier to walk through examples when you can look at something and point at it.
\n Assume that there’s a way to progress which doesn’t involve solve this problem – can you find it?<\/p>\n