So I just picked up a copy of Rapid Development...
-
...while waiting to meet with another developer and happened to open right to section 11, which is the section on motivation. And I will be dammed if it was not the best thing I have read in years! Now I want to read the rest of the book! :) I think that section 11 is something that everyone involved with software developers should read, regardless of their level of management. The parts regarding unrealistic deadlines and lack of developer involvement require particular attention. Hell, even developers themselves should read it, because it may help you understand yourself better, and perhaps one day you may be a leader and/or manager (:~ ), and need to respect and understand this stuff! Very interesting stuff, if you have never read it before, and maybe even if you have. Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFilesI have it and have read it thoroughly - the only problem is how do I get my managers to read it?
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
...while waiting to meet with another developer and happened to open right to section 11, which is the section on motivation. And I will be dammed if it was not the best thing I have read in years! Now I want to read the rest of the book! :) I think that section 11 is something that everyone involved with software developers should read, regardless of their level of management. The parts regarding unrealistic deadlines and lack of developer involvement require particular attention. Hell, even developers themselves should read it, because it may help you understand yourself better, and perhaps one day you may be a leader and/or manager (:~ ), and need to respect and understand this stuff! Very interesting stuff, if you have never read it before, and maybe even if you have. Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFilesIt is a fantastic book. I read it about 8 to 10 years ago. About time I read it again I think.
-- Always write code as if the maintenance programmer were an axe murderer who knows where you live. Upcoming FREE developer events: * Glasgow: Agile in the Enterprise Vs. ISVs, Mock Objects, SQL Server CLR Integration, Reporting Services, db4o ... * Reading: SQL Bits My website
-
I have it and have read it thoroughly - the only problem is how do I get my managers to read it?
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
I would put section 11 on a copy machine to extract the pages (it is only about 20 pages worth), then run the pages again through a duplexer and create enough copies to leave on desks or slip under doors. If you want it bad enough, you will find a way... The very act of discovering this section in their office or on their desk might be enough to kick-start the process for change. Then again, it might kick-start the process for your immediate departure. But no risk, no reward! :) Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
It is a fantastic book. I read it about 8 to 10 years ago. About time I read it again I think.
-- Always write code as if the maintenance programmer were an axe murderer who knows where you live. Upcoming FREE developer events: * Glasgow: Agile in the Enterprise Vs. ISVs, Mock Objects, SQL Server CLR Integration, Reporting Services, db4o ... * Reading: SQL Bits My website
The book lists the following as moral essentials: * Appropriate lighting * Desk and shelf space * Quiet environment * Privacy and freedom from interuptions * Access to office equipment * Up to date computing equipment * Immediate repair of faulty equipment * Applicable software * Applicable peripherals * Reference manuals and trade publications * Training in new technology * Legal copies of all software used * Flexible working hours The book is showing its age by not mentioning internet access....I'd also add: * Buffering and filtering of end users (i.e. no user should be able to come and stand behind you while you work on something for them) * Minimal beurocracy. If time managment software and teh like must be used then it must not take more than 5 minutes a week. * Break-out areas (somewhere you can sit with a couple of fellow tech heads to work through a problem without phones/email/pagers/managers) * Input in the software and hardware purchase decision making process * Input on process matters (use of agile methodolgy, pair programming etc.) * Managerial honsety. Anyone who asks me to work late because "we screwed up" or "we under budgetted" is more likely to get that extra commitment than "unforseen circumstances" or "external pressures". Any others?
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
The book lists the following as moral essentials: * Appropriate lighting * Desk and shelf space * Quiet environment * Privacy and freedom from interuptions * Access to office equipment * Up to date computing equipment * Immediate repair of faulty equipment * Applicable software * Applicable peripherals * Reference manuals and trade publications * Training in new technology * Legal copies of all software used * Flexible working hours The book is showing its age by not mentioning internet access....I'd also add: * Buffering and filtering of end users (i.e. no user should be able to come and stand behind you while you work on something for them) * Minimal beurocracy. If time managment software and teh like must be used then it must not take more than 5 minutes a week. * Break-out areas (somewhere you can sit with a couple of fellow tech heads to work through a problem without phones/email/pagers/managers) * Input in the software and hardware purchase decision making process * Input on process matters (use of agile methodolgy, pair programming etc.) * Managerial honsety. Anyone who asks me to work late because "we screwed up" or "we under budgetted" is more likely to get that extra commitment than "unforseen circumstances" or "external pressures". Any others?
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
Duncan Edwards Jones wrote:
The book is showing its age by not mentioning internet access.
Well, it does mention unrestricted access to a computer, and these days, there is not much to restrict a developer from EXCEPT for Internet access!
Duncan Edwards Jones wrote:
Minimal beurocracy. If time managment software and teh like must be used then it must not take more than 5 minutes a week. Managerial honsety. Anyone who asks me to work late because "we screwed up" or "we under budgetted" is more likely to get that extra commitment than "unforseen circumstances" or "external pressures".
Those are mentioned (somewhat) under the titles Management Manipulation, Excessive Schedule Pressure, and Inappropriate Involvement Of Technically Inept Management (
<--always a favorite of mine).Duncan Edwards Jones wrote:
Input in the software and hardware purchase decision making process Input on process matters (use of agile methodolgy, pair programming etc.)
That one is under Not Involving Developers In Decisions That Affect Them. The book is more than 10 years old and the stuff within it still applies and it still reflects today's problems! Proof that change is a very
s l o wprocess. Added: as far as break-out areas, it also mentions Up-to-date Communications Support, which specifically mentions conference rooms. This is basically a terminology difference. Peace!-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
The book lists the following as moral essentials: * Appropriate lighting * Desk and shelf space * Quiet environment * Privacy and freedom from interuptions * Access to office equipment * Up to date computing equipment * Immediate repair of faulty equipment * Applicable software * Applicable peripherals * Reference manuals and trade publications * Training in new technology * Legal copies of all software used * Flexible working hours The book is showing its age by not mentioning internet access....I'd also add: * Buffering and filtering of end users (i.e. no user should be able to come and stand behind you while you work on something for them) * Minimal beurocracy. If time managment software and teh like must be used then it must not take more than 5 minutes a week. * Break-out areas (somewhere you can sit with a couple of fellow tech heads to work through a problem without phones/email/pagers/managers) * Input in the software and hardware purchase decision making process * Input on process matters (use of agile methodolgy, pair programming etc.) * Managerial honsety. Anyone who asks me to work late because "we screwed up" or "we under budgetted" is more likely to get that extra commitment than "unforseen circumstances" or "external pressures". Any others?
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
Duncan Edwards Jones wrote:
Appropriate lighting
*flicker**twitch**flicker**twitch**flicker**twitch**flicker**twitch*
Duncan Edwards Jones wrote:
Desk and shelf space
classics too Eisenhower special!
Duncan Edwards Jones wrote:
Quiet environment
what did you say? what?
Duncan Edwards Jones wrote:
Privacy and freedom from interuptions
excuse me, can you hold on for a moment... I was expecting this and it needs to be handled now.
Duncan Edwards Jones wrote:
Access to office equipment
I think this WAS Eisenhower's! :cool:
Duncan Edwards Jones wrote:
Immediate repair of faulty equipment
:laugh::laugh: only 104 yesterday, air conditioner has been dead for 3 days, 4 today. The mice left my office to cool off outside!
Duncan Edwards Jones wrote:
Buffering and filtering of end users
:laugh::laugh:
Duncan Edwards Jones wrote:
Minimal beurocracy
:laugh::laugh::laugh::doh::doh::doh:
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
...while waiting to meet with another developer and happened to open right to section 11, which is the section on motivation. And I will be dammed if it was not the best thing I have read in years! Now I want to read the rest of the book! :) I think that section 11 is something that everyone involved with software developers should read, regardless of their level of management. The parts regarding unrealistic deadlines and lack of developer involvement require particular attention. Hell, even developers themselves should read it, because it may help you understand yourself better, and perhaps one day you may be a leader and/or manager (:~ ), and need to respect and understand this stuff! Very interesting stuff, if you have never read it before, and maybe even if you have. Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFilesI haven't read this one, but based on all the comments it sounds like he's right on the money. Unfortunetately, it's been my experience that the real difficulty is not that these problems exist but rather that, in general, most developers don't want to take the necessary action, get involved and promote change. It is without a doubt possible to address many of these issues, and I even wrote a book of strategy and tactics (Tribes) on how to do it. The problem is that most techies prefer to sit in a corner undisturbed so that they can play with their favorite toys. Don't get me wrong, that's a lot more fun than the social and political interaction required to fix the problems. However, if you do nothing, then nothing changes. Consequently, the typical cycle in shops is one of voicing irritation at reality, and then retreating to the nearest corner in order to avoid that reality. Rinse and repeat. Not surprisingly, nothing ever really changes, as evidenced by the voices in this thread pointing out that this was written a decade ago and yet the same problems still exist today. Oh, well. You can lead a horse to water, but you can't make him care. :)
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
I would put section 11 on a copy machine to extract the pages (it is only about 20 pages worth), then run the pages again through a duplexer and create enough copies to leave on desks or slip under doors. If you want it bad enough, you will find a way... The very act of discovering this section in their office or on their desk might be enough to kick-start the process for change. Then again, it might kick-start the process for your immediate departure. But no risk, no reward! :) Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
Boo! How is that different than copying licensed software?
"I don't want more choice. I just want better things!" - Edina Monsoon
I am not going to go too far out of my way here to defend myself - as I said, someone will find a way... It is different because (illegally) copying licensed software generally means an entire product, not a few pages of documentation. Copyright violation, yes; unless I could do so under the guise of Fair Use: Purpose and character - it will advance knowledge Effect upon work's value - would not damage current demand for the material Amount and substantiality - ~20 of ~650 pages Nature of the copied work - does not apply(?) Besides, if I could guarantee that the two sets pages are not in use at the same time... (Which would definitely be the case, because management types would not read them anyway! :)) Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
...while waiting to meet with another developer and happened to open right to section 11, which is the section on motivation. And I will be dammed if it was not the best thing I have read in years! Now I want to read the rest of the book! :) I think that section 11 is something that everyone involved with software developers should read, regardless of their level of management. The parts regarding unrealistic deadlines and lack of developer involvement require particular attention. Hell, even developers themselves should read it, because it may help you understand yourself better, and perhaps one day you may be a leader and/or manager (:~ ), and need to respect and understand this stuff! Very interesting stuff, if you have never read it before, and maybe even if you have. Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
Duncan Edwards Jones wrote:
Appropriate lighting
*flicker**twitch**flicker**twitch**flicker**twitch**flicker**twitch*
Duncan Edwards Jones wrote:
Desk and shelf space
classics too Eisenhower special!
Duncan Edwards Jones wrote:
Quiet environment
what did you say? what?
Duncan Edwards Jones wrote:
Privacy and freedom from interuptions
excuse me, can you hold on for a moment... I was expecting this and it needs to be handled now.
Duncan Edwards Jones wrote:
Access to office equipment
I think this WAS Eisenhower's! :cool:
Duncan Edwards Jones wrote:
Immediate repair of faulty equipment
:laugh::laugh: only 104 yesterday, air conditioner has been dead for 3 days, 4 today. The mice left my office to cool off outside!
Duncan Edwards Jones wrote:
Buffering and filtering of end users
:laugh::laugh:
Duncan Edwards Jones wrote:
Minimal beurocracy
:laugh::laugh::laugh::doh::doh::doh:
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)