I feel your pain, brother...:)

I read somewhere that only 10% of computer users will ever read documantation, 90% will stick what they learn 'by accident" and never try to learn more, only if persuaded (screaming and kicking) to do so. So no surprises your colleagues matches 90% of population.

My situation is also rather complicated. Although I have 10+ years of experience in programming, it was client/server and databases. I started with web, CGI and perl 3 months ago on my new job. I am in a team with 3 more programmers with various levels of experience (but max is about 3 years in IT), with little experience in design big multiuser systems, and even worse: they never worked in bigger teams (max 2).

So I needed to learn about perl, genetics, fix design flaws, develop common routines, while they can vote my proposals down on meetings. Or I need really to convert at least one or two of them before meeting to get my proposal through.

I understand their position: If I propose to fix something they cannot see, because it is too far away for theit experience yet, they may feel my concerns unnecessary.

But proposal about code reviews looks good for me, I'll try to do it. Any suggestions about link/books how to do it?

Thanks to perl saints, there is such a great place as perl monastery where you can express your concerns and share your pain with other perl developers, who "been there, done that" and may help with insight.

I definitelly get "The Pragmatic Programmer" book, I do not know where to get time to read it... :(

pmas