+1 in general. It's been pretty obvious to me, in the past, what the sorts of problems must have been on inherited code. Mostly because I have had to deal with the same clients and pressures that the previous guy had to. i.e. This situation is more than just an engineering one.
I agree with Michael Pearson re. finding explanations for bad code. I find that most of the really bad code is related to decent technicians in tough situations with inadequate management, communication skills or managerial support, resulting in poisoned attitudes, resulting in a feeling of not caring anymore, directly resulting in inadequate tests or poor quality. Whether or not you believe that the previous guy could have been more professional about the tough situation is probably not helpful. I think more discussion and training within our professional community about project management (even from the POV of having technical people manage themselves and their own teams such that there is no dedicated manager) would be very valuable. -Greg -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
