Hi Marc, I love this forum; it shows that developers all over the world (Canada, US, UK, lots more) are all dealing with the same issues. I personally feel that software development is the trickiest profession - lots of hidden traps, and not much common wisdom offered by colleagues/companies. In regards to your frustration about code reviews, style guidelines, I can relate directly. In my last position, the quality of a programmers code was determined by one programmer, who was a brown-noser to management. Not only did he not have as much development experience as I did, but he also emphasized speed and time to completion! "Code Complete" by Steve McConnell? Who/what is that? Comments? What the !@#$ do you need those for? Extra functionality that would be a boon to user productivity, and that I dreamed up while implementing? Why did you write and test that code, when we didn't ask for it? Team code reviews? Only in one company I've worked for in Canada, and that was mainframe development back in the early nineties. I take a lot of pride in my work - I do think style and thought put into coding is still relevant. I hate it when management says that your code should be indistiguishable from other developers in the project, especially when there are often no coding standards at all. I personally believe that a programmer will produce better work when: - His/her name is in the code - He/she feels they aren't just writing code, but is involved in a group process and that the whole group needs to learn - There isn't just an emphasis on code, but an emphasis on thinking, and - Each developer is recognized as a unique person, that their contributions are diverse, and conformance to an arbitrary rule is ridiculous. I find it naive to believe that many companies who pay lip service to coding practices and forward thinking policies actually work this way. In virtually every company I've worked, there is a big gap between what management says, and what the programmers reporting to those managers actually are told to do. Management walking the talk? More like management enforcing coding practices that bolster short term financial objectives! If houses are all about location, location, location then code is all about minimal time to write, the least possible number of bugs, and definitely not about modularity, extensibility, simplicity to understand, performance, or elegance. In regards to how emotionally involved I am/have been at work, I offer these points as evidence: - Waking up at 4am in a cold sweat,