[rartichoke]

A beginner with a passion and goal to improve will eventually become a professional. You don't get to professional status by just research and reading, you have to actually do things and figure out first hand what works and what doesn't.

Then you eventually learn to see things on your own. I don't need to read a popular programming pattern book to know how to structure my code. I know how to structure it based on feedback of using it on a regular basis while having a solid base of information to work off of.

If something feels off, I fix it where the solution is it no longer feels off. Until it feels off I'll likely leave it as is because at this point I haven't experienced the problem.

If something isn't a problem to me then it's not a problem. It's only a problem when it causes me to react in a negative way or is causing the system to react in a way that is bad.

I wouldn't recognize first hand that red on green is a problem for color blind people because I'm not color blind. If this hypothetical app had to work for color blind people then I would open a ticket and flag it as a feature request and then get feedback from someone who is color blind.

That's a good example of it's not a problem until it's a problem.

You can still constantly learn and keep up with things while taking DHH's advice btw. I have been coding and working with his mentality for quite some time now despite working with rails for only a year.

[karmajunkie]

Yeah, look me up when you've been cleaning up Rails code from developers who didn't bother to understand solid design principles for several years... that whole "wait til its a problem" thing falls apart pretty quickly in non-trivial domains.

[rartichoke]

You can't ignore things until it's a huge problem, that would be a mistake no matter what.

Do you have a real code example from a non-trivial domain?