I have foudn that the standard 8-8-8 schedule doesnt suit me as well as other schedules I have worked under. In particular, when I was workign privatetly (i.e. unemployed), I found that a 4-2-6-4-2-6 schedule worked much better. Not only was I workign more horus per day, btu i was getting a lot more accomplished because I was always working in the most efficient first 6 hours.
Has anyone else foudn patterns that better suited them?
What does 8-8-8 mean anyways? I mean, I've worked 5 8's, 5-4 9's, 4 10's etc, but only three 8's????? Is this one of those European things again?
8 hours work 8 hours personal time, 8 hours sleep
4 hour sleep 2 hours personal time 6 hours work
I don't think I'm so comfortable with sleeping in two intervals of 4... however, I must ask where you're getting "8" from when it comes to work time... Try, at least 8, not to mention two hours or so of commute. If I got 8 hours personal time everyday, I'd be in dream land... hell, I'd be in dream land if I got 8 hours of sleep.
From a business perspective, this new schedule would require buildings to be fully operational (and maintained) 24 hours a day. This can prove to be costly. So much so that I don't believe the extra efficiency of a few would make it worth it.
Last edited by SlyMaelstrom; 03-11-2008 at 09:07 AM.
Sent from my iPadŽ
Well, as a Software Engineer, there is no real reason I can't telecommute. My commute time is only 10-15 minutes each way, but thats an extra hour on the road each day (I go home for lunch). As for the 2 4 hours sleep cessions, I sort of fell into that pattern naturally, i.e. I didnt plan it that way, it just happened one day and I stuck with it.
Many people do not realise how many hours proffessional programmers work. It can vary, but the hours of work can be quite a strain on a social life. Then again it largly depends on the employer
Double Helix STL
And you don't do overtime, or work at home, or spend entire weekends, holidays and even vacations finishing projects because the deadlines are always impossible to fulfill?
Heck, I don't remember working 8 hours a day, but I can't say what my schedule was. When I didn't have to work overnight, I had to work overtime. When I didn't have to work overtime, I had to work from home. And when I didn't have to work from home, overtime or overnight, it was probably because I was unemployed.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
It is absolutely amazing that management cannot seem to understand that developing ANYTHING takes longer than a couple of weeks. Right now I am 3 weeks overdue for a "simple" X-Windows install for a touchscreen display that we are working with. I told them it would take about 3 months, they said that was way too long. I'm about 1.5 months into it and I figure I've got at least 3 more weeks.
This is a fairly typical "project management solution" - you estimate how long something will take, PM's say "Not good enough" and reduce the time allowed, but doesn't reduce the ACTUAL work needed, and what results is either that the product is not completed in time.Originally Posted by Kennedy
Now, it's OK to "take things off" to reduce the project time, but just saying "that takes too long" without either adding more people to work on it, or reduce the amount of work is just like saying "I make $3000 a month" then take out a mortgage for $2000 a month, when you actually only make $2000 a month in the first place [and no other income]. It's never going to hold in the long term.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Thats why you learn the lessons of Scotty and tell them it'll take 4 times longer then you actually think it will.
Or do as my teacher suggests "Okay boss, I just got this color dialog box in order, took a while to program the color spectrum chart. Now off to the open file dialog, see you in a few days.
My original estimate was 6months with NO INTERRUPTIONS. 10 Months with interruptions.
But we see how quickly that went the way of all flesh.
Yeah I've been down that road recently. Arogance coupled with ignorance is a bad combination for a manager, but all too frequent. The military used to follow a principle that any commander had to be able to do not just his own job, but his bosses job, everyone below hims job, and that of everyone below them. This didn't guarantee that unreasonable schedules werent made, but it drasticalyl reduced them.
Sometimes you get the trifecta, Arrogance, ignorance, and obstinance.
