Who says putting time pressure on programmers is more effective? What I have seen is that it leads to delivering low quality work, followed by a lot of "putting

Who says putting time pressure on programmers is more effective? What I have seen is that it leads to delivering low quality work, followed by a lot of "putting out fires" work. When you work with motivated engineers (most programmers are in my experience), they set their own pressure and deliver quality work. If you have a project supervisor that doesn't understand how quality software is made, leave. Putting in 80-100 hours? Nuts! Your estimates will slip even further when you do that.