Comments on: How to deal with jerk programmers http://www.scottberkun.com/blog/2009/how-to-deal-with-jerk-programmers/ Management and Creative Thinking Fri, 19 Mar 2010 16:40:08 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: Romeo http://www.scottberkun.com/blog/2009/how-to-deal-with-jerk-programmers/comment-page-1/#comment-522294 Romeo Sun, 22 Mar 2009 04:21:49 +0000 http://www.scottberkun.com/?p=1444#comment-522294 There are those who hate the upper management which then makes them the pain the arse for PMs. But then, you'd have to put up with some developers who are way over their head and have absolutely no reason to be angry about. Guess there is. Insecurity, not concerning with management, but personal insecurity. This particular of programmer deserves a wake up call. There are those who hate the upper management which then makes them the pain the arse for PMs. But then, you’d have to put up with some developers who are way over their head and have absolutely no reason to be angry about. Guess there is. Insecurity, not concerning with management, but personal insecurity. This particular of programmer deserves a wake up call.

]]> By: Marius http://www.scottberkun.com/blog/2009/how-to-deal-with-jerk-programmers/comment-page-1/#comment-522051 Marius Sat, 21 Mar 2009 21:18:08 +0000 http://www.scottberkun.com/?p=1444#comment-522051 “what I do (write specs), what you do (write code), what we both do together (triage bugs). Invariably there will be disagreements as to who does what work” At my work, the people who write specs are not project managers, but product managers (a different PM). But if you separate those things (specs and code), you are actually not getting the most out of your programmers. A programmer should be part of the process of creating a specification. It is them who know more about the technical restrictions anyway, and can also give valuable input. “what I do (write specs), what you do (write code), what we both do together (triage bugs). Invariably there will be disagreements as to who does what work”

At my work, the people who write specs are not project managers, but product managers (a different PM).

But if you separate those things (specs and code), you are actually not getting the most out of your programmers. A programmer should be part of the process of creating a specification. It is them who know more about the technical restrictions anyway, and can also give valuable input.

]]> By: Viraf Karai http://www.scottberkun.com/blog/2009/how-to-deal-with-jerk-programmers/comment-page-1/#comment-520988 Viraf Karai Fri, 20 Mar 2009 05:38:11 +0000 http://www.scottberkun.com/?p=1444#comment-520988 Most of the PMs I've worked with have been pathetic morons barring one or two. This job involves marginal creativity and is certainly not management as far as I am concerned. PMs should not be paid more than 75% of the median salary for experienced developers. I'm sure there are some very good PMs out there, but they contribute only marginally to the finished product (if you count schedule jockeying as an intellectual activity). Most of the PMs I’ve worked with have been pathetic morons barring one or two. This job involves marginal creativity and is certainly not management as far as I am concerned. PMs should not be paid more than 75% of the median salary for experienced developers. I’m sure there are some very good PMs out there, but they contribute only marginally to the finished product (if you count schedule jockeying as an intellectual activity).

]]>