I wish all newbies would read clean code. I feel if you understand the concepts you can more easily join an established team and contribute more quickly with less do overs. I realize writing elegant, testable code is like making good whiskey. It takes time.

The problem with that, is knowing if the code is truly considered clean code.

@results that the problem. There is so much disagreement.

@georgelynch even standards that are set can only tell you so much.

I guess my rant is about seeing spaghetti by the juniors that other senior devs thinks is ok. I ask them to refactor but people say only people who have done enterprise code care about that shit.

@georgelynch: I'm with you. Although I take pride in my work and like other people to be able to look at it and easily follow what's going on. You need to be dispensable as bad as that sounds. Being dispensable is a good thing to me, it means if you leave, you won't screw the team and someone can come in and pick up where you left off with little onboarding.