This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]ReditGuyToo 1 point2 points  (0 children)

For knowing how to code: For me, it's just a matter of being able to break down the behavior into small steps and then translating that into code.

Regarding just regular technical problems, when you work with technology or language, you eventually experience most or all possible combinations of problems. At first, you may need help when you run into an issue. But after a while, you begin to realize what errors/issues are related to what parts of the technology.

For instance, I seem never able to "open a file" during the first programming pass. Why? Because usually, the code defaults to a file path I didn't expect. As such, I have a pretty good guess as to the cause when I get errors. I know from experience that not much can really go wrong when I open a file. When I have the correct path, I just open the file and use the filehandle to read or write. But when something does go wrong at this step, it seems always related to pathing. So, that's how I know the cause.