 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 13/11/2013 11:52 PM, Jim Henderson wrote:
> On Wed, 13 Nov 2013 22:14:00 +0000, Orchid Win7 v1 wrote:
>
>> If it were noticed that I was only pretending to work, I'd probably be
>> fired on the spot. That doesn't mean that my work is critical to meeting
>> deadlines - it's just that, why would you pay somebody to do nothing?
>
> They actually hired you to do a job, and you're doing it - so as a self-
> assessment, you need to talk about how you're doing the job they're
> paying you to do.
>
> You're still relatively new to the organization, so it's entirely
> possible that your tasks to date haven't been mission-critical deadline
> items, but you need to talk about them in the assessment, certainly.
> Getting things done earns you more responsibility, more visibility, and
> ultimately (it's generally hoped) more pay.
>
> So look at this another way - they interviewed you, hired you, and seem
> to be happy with the job you're doing, right? So don't tell them they're
> stupid by saying that what you do doesn't matter.
>
Jim is perfectly right. He comes from a culture that, we in Britain are
drifting to, like a boat in a whirlpool.
Think about it like a justification for your job. You either play the
game or opt out and be expendable. I opted out. For my last assessment I
went into the maintenance supervisor’s office with my trousers over my
arm and said that it was his job not mine to give me an assessment. It
did not go down well. Now I am a contractor and I will never have one
again. I don’t think that you would like the lifestyle, of either.
Blow your own horn because the days that someone else would do it for
you are long gone. :-(
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 13/11/2013 10:49 PM, Orchid Win7 v1 wrote:
> Put simply, we make stuff used by several foreign governments, and if
> you want to know exactly what it does, you're going to need security
> clearance.
>
So! I have that. (When you work in the nuclear industry it is
mandatory.) So has doctor, you know who.
> Not joking.
Not joking.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 2013-11-13 17:49, Orchid Win7 v1 a écrit :
>>> *mumble something about the company not actually having any defined
>>> direction*
>>
>> Certainly someone must have an idea what the company does.
>
> Remember that "the company" consists of less than 10 humans [decimal].
> When a company is that tiny, they don't necessarily have a grand
> "corporate vision" laid out in meticulous detail.
>
> From what I can gather, the business owner's plan is to make a product
> that does everything for everybody. Every time a customer mentions
> something the product doesn't do, we must immediately implement that
> feature.
>
> I presume I don't need to explain why this is a flawed approach?
>
>> You're very
>> secretive about even where you work, so it's kinda difficult to provide
>> specific information.
>>
>> What market does the company serve? Who are its competitors?
>
> Put simply, we make stuff used by several foreign governments, and if
> you want to know exactly what it does, you're going to need security
> clearance.
>
> Not joking.
>
Them?
http://en.wikipedia.org/wiki/FinFisher
> That probably makes it sound *far* more exciting than it actually is.
> But obviously I'm not going to sit here and talk about it on some random
> Internet forum that anybody can read.
>
> What I can tell you is this: There are only so many governments in the
> world. So our market is small, and competing products number dozens
> rather than thousands or something.
>
>>> Thing is, if I say "I wrote some code", that's too short. And if I
>>> describe everything I implemented - even just the noteworthy stuff -
>>> that's *way* too long.
>>
>> There's a middle ground. "I wrote code that does 'x'" - as a summary,
>> not a detailed description.
>
> Well, this year I wrote code for about 25 different small tasks. A list
> of 25 items seems a little excessive though...
No. Not at all.
You may want to group them in categories if some of those tasks are
similar. Or only give 2 or 3 main ones as an example.
Ex:
- Created installation scripts for X, Y, and Z.
- Created, implemented testing plan for 23 modules (main ones being Foo,
Bar and Baz).
- Etc...
--
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/* flabreque */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/* @ */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/* gmail.com */}camera{orthographic location<6,1.25,-6>look_at a }
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 2013-11-13 19:57, Stephen a écrit :
> On 13/11/2013 10:49 PM, Orchid Win7 v1 wrote:
>> Put simply, we make stuff used by several foreign governments, and if
>> you want to know exactly what it does, you're going to need security
>> clearance.
>>
>
> So! I have that. (When you work in the nuclear industry it is
> mandatory.) So has doctor, you know who.
>
So do I, but I work in one of the colonies. It may not be recognized.
>> Not joking.
>
> Not joking.
>
Not joking.
--
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/* flabreque */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/* @ */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/* gmail.com */}camera{orthographic location<6,1.25,-6>look_at a }
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>>> There's a middle ground. "I wrote code that does 'x'" - as a summary,
>>> not a detailed description.
>>
>> Well, this year I wrote code for about 25 different small tasks. A list
>> of 25 items seems a little excessive though...
>
> No. Not at all.
>
> You may want to group them in categories if some of those tasks are
> similar. Or only give 2 or 3 main ones as an example.
>
> Ex:
> - Created installation scripts for X, Y, and Z.
> - Created, implemented testing plan for 23 modules (main ones being Foo,
> Bar and Baz).
> - Etc...
Now that seems reasonable...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 13/11/2013 11:52 PM, Jim Henderson wrote:
> You're still relatively new to the organization, so it's entirely
> possible that your tasks to date haven't been mission-critical deadline
> items, but you need to talk about them in the assessment, certainly.
> Getting things done earns you more responsibility, more visibility, and
> ultimately (it's generally hoped) more pay.
In such a tiny company, *everybody* is already very near the top of the
tree - because it's only a tiny tree. (More of a shrub really...) ;-)
> So look at this another way - they interviewed you, hired you, and seem
> to be happy with the job you're doing, right? So don't tell them they're
> stupid by saying that what you do doesn't matter.
Fair enough.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 14/11/13 00:57, Stephen wrote:
>
> So! I have that. (When you work in the nuclear industry it is
> mandatory.) So has doctor, you know who.
>
So now I'm going to have to kill you; but not before you've bought me a
beer (and possibly some uisge beatha)
>> Not joking.
>
> Not joking.
>
What do you think ;-)
John
--
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 14/11/13 00:38, Stephen wrote:
>
<snip>
> For my last assessment I
> went into the maintenance supervisor’s office with my trousers over my
> arm
Now I've lost my appetite :-)
John
--
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 14 Nov 2013 08:39:02 +0000, Orchid Win7 v1 wrote:
> On 13/11/2013 11:52 PM, Jim Henderson wrote:
>
>> You're still relatively new to the organization, so it's entirely
>> possible that your tasks to date haven't been mission-critical deadline
>> items, but you need to talk about them in the assessment, certainly.
>> Getting things done earns you more responsibility, more visibility, and
>> ultimately (it's generally hoped) more pay.
>
> In such a tiny company, *everybody* is already very near the top of the
> tree - because it's only a tiny tree. (More of a shrub really...) ;-)
Yep, I've worked with companies that size as well. The COO of one client
is the CEO's "minder" - because the CEO is sorta "Jobsian" in his
approach (ie, very little focus, big thinker, not too concerned about the
details, changes his mind daily about where he wants to go).
But the developers at that company have specific areas of expertise. One
works on network systems, one works on CPU utilization, etc.
>> So look at this another way - they interviewed you, hired you, and seem
>> to be happy with the job you're doing, right? So don't tell them
>> they're stupid by saying that what you do doesn't matter.
>
> Fair enough.
So just summarise what you've done over the past year. That's a starting
point.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> (ie, very little focus, big thinker, not too concerned about the
> details, changes his mind daily about where he wants to go).
That sounds disturbingly familiar.
Ooo, a shiny thing...
>>> So look at this another way - they interviewed you, hired you, and seem
>>> to be happy with the job you're doing, right? So don't tell them
>>> they're stupid by saying that what you do doesn't matter.
>>
>> Fair enough.
>
> So just summarise what you've done over the past year. That's a starting
> point.
OK.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
