What you said. Extrapolated to months. Hope you're right.....else
it may be more than just things that will "die down" :-(
A bit of wisdom in most workplaces seems to be this:
You will become far less stressed when you come to the realization that you will NEVER catch up, no matter how many extra hours you work. So work hard, work smart, but don't kill yourself trying to "catch up."
yea, I've also been pulling the sled hunting Sausage fishing rod a while back.It doesn't work out. The only way out was to switch the job. But took a while to figure that out.
Get everything done that I can and a bit more.. But then stop the insanity.
Hm, I guess iggy promptly knows whose desk he would lift?
http://www.the9gag.com/recent/if-a-programmer-have-personal-office-4522
I've a coworker who is in a bit of a pickle. He's been assigned to something for which he has almost no hope of accomplishing the goals without seriously screwing it up due to lack of manpower and aggressive scheduling set up by someone other than himself. Someone who obviously doesn't know beans about software development.
He's a good guy, but I fear we'll lose him if he doesn't get some relief.
After about 30 seconds of hysterical laughter from me I would respond "that's why God invented tomorrow" and proceed to walk out toward the main office sign-out desk.
And when "tomorrow" arrived, I'd hand it off to my intended successor (as department chair) and tell him "review, initial, hand back"... I'd never see it again... <evil grin>
Hm, I guess iggy promptly knows whose desk he would lift?
Yes but not like that. I prefer to lift desks using explosives underneath.
Preferably while occupied.
Mon Mar 02 2015 05:57:15 PM EST from IGnatius T Foobar @ UncensoredWhat you said. Extrapolated to months. Hope you're right.....else
it may be more than just things that will "die down" :-(
A bit of wisdom in most workplaces seems to be this:
You will become far less stressed when you come to the realization that you will NEVER catch up, no matter how many extra hours you work. So work hard, work smart, but don't kill yourself trying to "catch up."
Ha...yeah, no question of that!
In this case, it's more a matter of the fact that the group I manage grew from 5 to 35 in less than 2 years - and we STILL can't keep up with all the business. It's a great problem to have, but operational management of 35 people, plus 2 actual projects, plus escalation management for a portfolio of 50-60 active projects at one time is a big apple to bite. No hope of catching up...it's more a matter of not drowning.
2015-03-17 12:53 from IGnatius T Foobar @uncnsrd
35 is way too many for one person to manage.
Heh.
I guess you'd be disqualified from being a Nun in the parochial school I attended for eight (long) years.
The first 6 years, class size was *never* less than 60 kids.
One Nun.
Two 3-hour sessions per day.
You could hear a pin drop - literally.
Make the Nun mad? Pain followed.
Don't pay attention? Pain followed.
Pass a note or whisper to the kid next to you? Pain followed.
So... it looks like you need corporal punishment in the workplace!
<evil grin>
Never, ever, try to do a full day of interviews for candidates for a software engineering position.
It's soul-crushing.
Even the intern. I didn't expect much from the intern, honestly, but when she said she had taken a C/C++ course, I thought she would at least know what a pointer is.
She didn't. Her instructor primarily teaches Java, and skipped past the detail of pointers by passing everything by value.
I want to break his kneecaps on her behalf. Or whatever else is nearby.
Right, but the point is that she paid for a C/C++ course, and her asshole of an instructor didn't tell her anything about pointers. So she is under the delusion that she has had a proper education about C/C++ when, really, she hasn't.
It galls me. I get that instructors can be somewhat out of the loop about what really goes on in software development once you get out of their ivory tower, but this is inexcusable.
There might be an excuse for that, if the course was intended to be an intro as part of a longer CS curriculum. Which, obviously, was not her major...
The word 'parrallelizing' is paralyzing to pronounce.
That's why you need several people to pronounce it at the same time.
Mar 25 2015 4:26pm from IGnatius T Foobar @uncnsrdThe word 'parrallelizing' is paralyzing to pronounce.
That's why you need several people to pronounce it at the same time.
Oh, I like that idea! We need to record that, and send it to all of our federal politicians with a request for immediate response.