Timeline for Writing code vs Figuring out the answer to a problem?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 10, 2011 at 22:39 | comment | added | kevin cline | Some do, but not EVERYONE gets bogged down in implementation details. With modern languages, there is very little difference between design and high-level coding. | |
| Apr 30, 2011 at 18:02 | comment | added | Binary Worrier | @Kevin: expressing problems isn't the issue, expressing solutions is :) I'm not saying you plan out every line of code or class, but you need to know - or have a fair idea - where your going to end up as you start writing. The biggest waste I've seen junior - mid level developers make, is starting to codeca solution to a problem and they're unaware they don't know the solution. They get confused and bogged down in implementation details, they - wrongly - equate this with solving the first problem | |
| Apr 30, 2011 at 0:35 | comment | added | kevin cline | For a lot of folks, code is the easiest and most precise way to express the solution; in other words, the second "problem" is no problem at all. No one ever suggests that before solving a math problem, we should try to write the solution "in words". | |
| Apr 29, 2011 at 21:23 | history | answered | Binary Worrier | CC BY-SA 3.0 |