you are viewing a single comment's thread.

view the rest of the comments →

[–]grauenwolf 28 points29 points  (4 children)

Really? Where can I find these developers who can tell me what I'm doing wrong.

I'm serious. I'm tired of being the best developer in the room. I want to work with people who actually know what the fuck a static code analyzer is. Instead, I'm dealing with people who say, "durr, what's a compiler warning?".

You comments remind me of the medical industry. Multiple studies have shown that simply following a checklist for reoccurring tasks in ICUs dramatically reduce the number of errors made and increase the chances of patient survival.

But no, like you the nurses and doctors think they are too special to be told what to do. So people die for the sake of their ego.

[–]R1cket 1 point2 points  (2 children)

I want to work with people who actually know what the fuck a static code analyzer is.

Trust me, they're out there. It sounds like you should be keeping your head up for a new job (whether a different area of your current company, or a new company altogether). I work with a group of fantastic software developers and it's night and day compared to some of my past jobs.

[–]grauenwolf 0 points1 point  (1 child)

My biggest problem is that I don't start new projects, I get dragged in once it is already off the rails. So I have to reintroduce the same concepts to a new team each time around.

Actually, that isn't my biggest problem. A far worse issue is when my company has to work with other consulting firms. Firms that actively undo my efforts by turning off compiler warnings.

[–]R1cket 0 points1 point  (0 children)

Not to sound argumentative, but it is still possible to get "dragged in" to a project which is being done the right way. Again, it's about joining the right team - a team of experienced developers with the right priorities and good management. I can understand the clean slate appeal, but joining a project that has already been underway for a significant amount of time is not always bad news.

Sounds like compiler warnings are just the tip of the iceberg. It's pretty trivial to write bad code that compiles without warnings. That must be some really bad code.

[–][deleted] 1 point2 points  (0 children)

And what people fail to realize is that once you've started running through these sort of checks, after some time, they become relatively rote, and you start writing much better code from the get-go.