I Think your problem here is that you still subscribe to the fallacy that "Code like Hell" Programming is faster than doing things properly.
It isn't.
Many organisations are starting to find this out and are moving to proper professional engineering practices that improve reliability increase schedule predictability and more importantly reduce costs.
A couple of hundred years ago people built houses & bridges the way we build software - work until it's done. These days we have archaetects and project managers that build houses faster, more reliably and ON BUDGET.
This is the way the wind's blowing. It's a lot less heroic but it's the future.
Although you are right about unreasonable deadlines, we as programmers are also to blame for:- a) Not understanding estimation and scheduling, hence producing woefully optimistic schedules. b) Not communicating to management. I know they're Micro$oft Press but I would suggest reading the work of Steve McConnell who has written 4 brilliant books on the subject of Software Engineering. Not dry academic tomes but practical, readable, useable books. No I'm not related to him or M$ in any way:)
Slashdot Mirror
I Think your problem here is that you still subscribe to the fallacy that "Code like Hell" Programming is faster than doing things properly.
It isn't.
Many organisations are starting to find this out and are moving to proper professional engineering practices that improve reliability increase schedule predictability and more importantly reduce costs.
A couple of hundred years ago people built houses & bridges the way we build software - work until it's done. These days we have archaetects and project managers that build houses faster, more reliably and ON BUDGET.
This is the way the wind's blowing. It's a lot less heroic but it's the future.
Although you are right about unreasonable deadlines, we as programmers are also to blame for :- a) Not understanding estimation and scheduling, hence producing woefully optimistic schedules. b) Not communicating to management. I know they're Micro$oft Press but I would suggest reading the work of Steve McConnell who has written 4 brilliant books on the subject of Software Engineering. Not dry academic tomes but practical, readable, useable books. No I'm not related to him or M$ in any way :)