I AM NOT A MANAGER!
-
Management is not hard. Just saying. ;)
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
Management is not hard. Just saying. ;)
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
It's not that it's hard - it's that it's not development.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
John Simmons / outlaw programmer wrote:
They recently added FIVE additional forms
For that, they'd need to present you with form a38 :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
38???!!! Surely you mean form 1911.45
-
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013This is to notify you that someone is sending me stupid forms and signing your name to them.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
-
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Do the new reports have a cover sheet too? [Office Space (1/5) Movie CLIP - Did You Get the Memo? (1999) HD - YouTube](https://www.youtube.com/watch?v=jsLUidiYm0w) :)
-
It's not that it's hard - it's that it's not development.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013John Simmons / outlaw programmer wrote:
it's that it's not development.
I see. Are you one of those that only likes to code and not do anything else?
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Learn to delegate, surely you have an officious little worm in your team, dump it on them and just sign off on the forms.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
38???!!! Surely you mean form 1911.45
Permit a38. If you want to register a galley, you should be at the harbormasters' office down at the port. The 12 Tasks of Asterix: The Place That Sends You Mad (widescreen) - YouTube[^]
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
John Simmons / outlaw programmer wrote:
it's that it's not development.
I see. Are you one of those that only likes to code and not do anything else?
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
I've successfully avoided moving into management since 1979. It's important that you stick with what you're good at, and avoid things you're not good at.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
John Simmons / outlaw programmer wrote:
it's that it's not development.
I see. Are you one of those that only likes to code and not do anything else?
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
Hmmmm. Perhaps you're one of the people that think John should continue to try to climb the ladder until he's an example of the Peter Principle? I'm with John - I do this job for the satisfaction, not the money. Promotion to manager? Blah - give it to someone that deserves to be punished. Money:Stress ratio is always better further away from the top-end.
-
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013John Simmons / outlaw programmer wrote:
<sarcasm>As developers, we're used to
You neglected to close your sarcasm tag. Maybe you should consider a job in management ;P I'll see myself out.
My plan is to live forever ... so far so good
-
John Simmons / outlaw programmer wrote:
<sarcasm>As developers, we're used to
You neglected to close your sarcasm tag. Maybe you should consider a job in management ;P I'll see myself out.
My plan is to live forever ... so far so good
is a tag that never ends
-
I've successfully avoided moving into management since 1979. It's important that you stick with what you're good at, and avoid things you're not good at.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013John Simmons / outlaw programmer wrote:
It's important that you stick with what you're good at, and avoid things you're not good at.
Now there's one way to grow as a person. ;)
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
Hmmmm. Perhaps you're one of the people that think John should continue to try to climb the ladder until he's an example of the Peter Principle? I'm with John - I do this job for the satisfaction, not the money. Promotion to manager? Blah - give it to someone that deserves to be punished. Money:Stress ratio is always better further away from the top-end.
enhzflep wrote:
Perhaps you're one of the people that think John should continue to try to climb the ladder until he's an example of the Peter Principle?
Nope. It was just a simple question.
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
John Simmons / outlaw programmer wrote:
It's important that you stick with what you're good at, and avoid things you're not good at.
Now there's one way to grow as a person. ;)
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
I fully recognize my inability (and lack of desire) to give a sh*t about someone's sensitivities. If they f*cked up, they should know, and if it falls to me to tell them, they'll probably end up hiding in a corner, sucking their thumb, and crying for their mommy. I have no interest in changing my approach. I am the LAST person that should be a manager. I also don't feel like this is a major character flaw.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013The absence of a closing sarcasm tag has been noted in your personnel file. :laugh:
-
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I copied that response for future use. Thanks for that.
-
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Under New Mismanagement!!!!
-
I don't know how these people decided that a team lead should be responsible for submitting weekly and monthy status reports, but here I am. They recently added FIVE additional forms to the powerpoint slide deck, which I have to complete every week. The guidance I was given was to : "...include any significant events and state how they were of benefit to the Government, as well as KUDOS for performance." My response As developers, we're used to - and have come to expect - a complete lack of anything that could be identifiable as recognition or appreciation for the work we do, regardless of how much time/money it saves anybody. I suppose when you consistently deliver excellence, it becomes expected, anticipated, or mundane, and is subsequently subverted into feelings that could best be described as, "That's your job. What did you expect? A rrrrrrrrubber biscuit?". Furthermore, a "significant event" would be my continued ability to resist the urge to choke the living sh*t out of the customer for submitting stupid work items in TFS, or for demanding immediate turnaround of "emergency" work items that aren't included in the current sprint. ---------------- I'm not really sure how management will react...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Number Six: I am not a number! I am a free man! Number Two: [laughs] Number Six: I will not make any deals with you. I've resigned. I will not be pushed, filed, stamped, indexed, briefed, debriefed, or numbered! My life is my own!
Software Zen:
delete this;
