* Robin Szemeti ([EMAIL PROTECTED]) wrote:
> On Thu, 18 Jan 2001, you wrote:
>
> > Having something to crash on when pulling an all-nighter is, IMO, a bad
> > idea as it encourages pulling all-nighters. You just don't write good
> > code at 2 in the morning, and end up spending just as much time untangling
> > it as you did writing it in the first place.
>
> yes and no. If you need to do an allnighter and its unavoidable (due to a
> client suddenly changing ther mind) then theres no problem doing it ..
> just charge em bigtime!
>
nope this is where your pimp/MD should of tied up the contract watertight,
so if they change their mind the deadline changes
> and 2 because I was just so tied up in it and it was going so well that I
> didn;t want to stop .. so I didn't ... the code from the latter is
> untouched to date and some of the better code I've written.
thats fine, but if you have such commitment to work surely you could grab a hotel
that the business is friendly with and put it on expenses
> play. One of the reason I hated a 9 to 5 job was people asking me to do
> hard things before lunchtime and having to quit doing hard things because
> it was 5:00.
this is fine for internal work, but wrong for our earlier discussion
about consultancy
> > And in any case, if you
> > *need* to work all night, there's something wrong with the project
> > management.
agreed
> no matter how well planned the project I have yet to find a client who
> hasn;t kept some small but deadly surprise as a secret to throw in just
> when they know its getting close. Some of these bombshells are smaller
> than others .. but they always seem to be there, waiting ... no problem
> .. just expect em an be prepared .. and charge em BigTime :)
how do you think IBM deal with this? if the client adds some crap, they
change the deadlines/cost
greg
--
Greg McCarroll http://www.mccarroll.uklinux.net
