distracted828

Yea, I've only had about 4 years since I got out of school. Trying to be better able to break the task down is part of why I want to do the studying

Well the things I listed in my OP are my concrete ideas for how to approach these working on these things. If you have other concrete suggestions, I would love to hear them.

As an example: The reason why I focus on studying rails is that all of the debugging techniques I know about involve getting a better idea of the system at some layer of abstraction. I suspect that my best shot at getting better at debugging is to know the framework the code is written in very well and thereby be able to understand the codebase more easily.

For a problem like "I can't get clarity around what we are trying to do here.", it seems like there aren't any books on the topic. Thats why I figured that finding a mentor would be good.

What I mean is, how do you keep it from catching up with you a week later?

Sure, but at a certain point, you need to learn a method to writing a maintainable codebase. Otherwise you never become capable of building a successful project.

It is something I've wished I could do. In fact, I am considering only working at a company that does pair programming.

Here is something I don't understand: How does one effectively deliver on a project while writing crappy code? Doesn't trying to do that result in the codebase becoming so confusing that you don't know how to add things to it without breaking other things?

Having been part of a technical organization that was a democracy: no.

I'll take a monarchy over 5-hour meetings where nothing is decided and the room hates each other any day.

> failure teaches you which mistakes to avoid next time

As a recent grad who has been fired from two jobs, I would be afraid to join a poorly written project because I would worry that I would fail and then be fired.

Learning how to be successful is pretty important and teaches you things you cannot learn from lurching from failure to failure.