How many hours do you put into your work Lulu ?
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
"Disappointing" and "Utterly Horrible" are not equal.
I'm quitting and going to work at Radio Shack
all projects all crunch all the time
Originally posted by Tim LeMaster:
Don't blame your clients, blame your management for accepting unreasonable deadlines.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
"Disappointing" and "Utterly Horrible" are not equal.
You laugh when I say I'll go to work at Radio Shack
delivered product should be higher calibre than the grossly sloppy stuff I see everyday at major corporate websites.
Enough IT projects fail as it is.
Don't simply blame your management, blame yourself, too.
Another thing that promotes long work timings is when people stare at you for leaving early, even though your work is complete. Some people can take it while others cant, which forces them to stay late just so it looks like they are working.
R.N
OCUP UML fundamental and ITIL foundation
"...it takes all the running you can do to keep in the same place. <br />If you want to get somewhere else, you must run at least twice as fast as that!" <br />~ Through the Looking-Glass
Originally posted by John Meyers:
Another thing that promotes long work timings is when people stare at you for leaving early, even though your work is complete. Some people can take it while others cant, which forces them to stay late just so it looks like they are working.
R.N
"...it takes all the running you can do to keep in the same place. <br />If you want to get somewhere else, you must run at least twice as fast as that!" <br />~ Through the Looking-Glass
Try leaving quietly
Originally posted by tambi durai:
Try leaving quietly, without saying goodbye to anyone; just leave as if you are going for a coffee. ;) Don't carry any bag, coat; leave that in your car. Most people won't notice that you have left early...at least not immediately...
Originally posted by Rohit Nath:
8 hours per day, 5 days a week should be more than enough for an IT job.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Since we are talking about work, then I mean 'career path'.
Originally posted by Mark Herschberg:
In the US, the 40 hour week, outside of government work and government related industries is pretty much a thing of the past for salaries employees.
Originally posted by Lulu Carr:
How many of us believes that willingness to work late & hard is based on if we consider what we do "just a job" vs. "a career"?
Originally posted by Lulu Carr:
What I've noticed in my company is that people don't get noticed for just working 40 hrs a week, because that means that they are only doing what is requested, or not getting what is requested completely done.
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
What I've noticed in my company is that people don't get noticed for just working 40 hrs a week,
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
There is nothing inherently wrong iwth a 60 hour work week.
I've yet to find an employer who wasn't honest with me about the hours. (Or maybe I simply only took jobs from employers who were honest about it.)
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
"Disappointing" and "Utterly Horrible" are not equal.
Originally posted by Tim Holloway:
The problem is, it's been pretty well established that in the IT world, hours worked have virtually no relationship to productivity whatsoever.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
The problem is, it's been pretty well established that in the IT world, hours worked have virtually no relationship to productivity whatsoever.
R.N
I tweaked around with my work style:-
1. Spend time on clear understanding of task.
2. Cut down on "time wasters" like email/phone/surfing/friends during work hours!
3. Plan the day for the task. Set my own deadlines.
4. Try to complete task before each deadline.
5. In the saved time do extra things that help me provide that "extra".
6. Make the *Task my first priority* and everything else after work time.
All this added up to efficient usage of my time.
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
"Disappointing" and "Utterly Horrible" are not equal.
Originally posted by Tim Holloway:
I'm not just spouting anecdotes. There are people who get paid to analyze productivity and to distinguish real productivity from apparent productivity. One of them is Ed Yourdon. Without digging back through my library, I believe it was Yourdon who made the observation that "when programmers are productive, they are very very productive, but when they are bad, they are horrible." I'm sure I've mangled the quote, but you get the idea.
...
If I was absolutely forced to, I suppose I could go back and rummage through a lot of that material and present it formally with hard numbers (where available).
Before I do, however, who among us is willing to state that their functional code output is truly a linear function of time?
Originally posted by Tim Holloway:
Before I do, however, who among us is willing to state that their functional code output is truly a linear function of time? That's the whole basis of the more hours = more productivity assertion, isn't it?
Originally posted by Tim Holloway:
1. My own personal experiences and observations over the last several decades as a professional.
2. The collaborating reports of peers - some of whom have made similar observations in various forums here on the JavaRanch.
3. Published case studies and similar documentation by respected figures in the industry.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Originally posted by Jeanne Boyarsky:
I still think the 40 number is arbitrary. Each person has a limit though. It's important to know where it is as an individual!
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Originally posted by Mark Herschberg:
While I agree that everyone is different, the 40 hour work week is not arbitrary.
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Originally posted by Jeanne Boyarsky:
Oops. Let me further qualify my sentence:
I still think the 40 number is arbitrary as the peak amount of time for employee productivity. There's going to be some point at which working more hours makes people less productive. I think this point varies by individual, so it's not some fixed number anyway. This number is not likely to be exactly 40.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
I suggest huckleberry pie. But the only thing on the gluten free menu is this tiny ad:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
|