The following kinds of problem lend themselves well to simple solutions that do a 1:1 mapping of the solution to the problem being solved (aka the 100 line scri

The following kinds of problem lend themselves well to simple solutions that do a 1:1 mapping of the solution to the problem being solved (aka the 100 line script) - a) Problems that are simple b) Problems that are well defined, static and not expected to change over time c) Problems about which the implementor knows so little that a more elaborate solution would be premature d) Problems that appear complex but lend themselves to asimplistic solution (usually underpinned by some beautiful mathematical truth) e) Problems that dont require long lasting solutions. eg ones where you are trying to cash into an ongoing meme which could run out at any moment Problems that dont fit into the above categories require more thought to be put into identifying the underlying abstractions and for these great software solutions emerge from a) Understanding the problem being solved b) Identifying the abstractions which underpin the problem c) Identifying how the problem is expected to evolve over time and verifying that the abstractions hold up for expected changes. I think you are drawing too much from your experience of a single problem and code from a single programmer.