How often do you take the initiative in your company?
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
All the time. Be it Accounts based, Tech or Administrative it is my job to be on top of it. Proactive (how I hate that word) Management it is called.
--------------------------------- Obscurum per obscurius. Ad astra per alas porci. Quidquid latine dictum sit, altum videtur.
-
All the time. Be it Accounts based, Tech or Administrative it is my job to be on top of it. Proactive (how I hate that word) Management it is called.
--------------------------------- Obscurum per obscurius. Ad astra per alas porci. Quidquid latine dictum sit, altum videtur.
Dalek Dave wrote:
Proactive (how I hate that word) Management
How about "Thinking Ahead"?
speramus in juniperus
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
Everytime. when a new project comes. I take it or forced to take alternatively. :-D
-
Dalek Dave wrote:
Proactive (how I hate that word) Management
How about "Thinking Ahead"?
speramus in juniperus
I always prefered "Drive" or "Driven" though marketing and sales always manage to ruin a word by repeating 50,000 times.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
-
It's my job to take initiative, to find improvements (but not necessarily to implement them). So I do it every day a several time...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
I must say that sounds like a brilliant job, though hard also? Is it mainly for one company or do you do consultant based work?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
-
I must say that sounds like a brilliant job, though hard also? Is it mainly for one company or do you do consultant based work?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
I do it for the same company for over 15 year, and still interesting...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
-
DaveAuld wrote:
there isn't usually a lot the people above can do!
Don't be rude, they'll be more worried than you! What if there was a loss of... ...money?
speramus in juniperus
-
DaveAuld wrote:
there isn't usually a lot the people above can do!
Don't be rude, they'll be more worried than you! What if there was a loss of... ...money?
speramus in juniperus
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
Every minute - I am steering the company towards understanding that we need specifications(all the work is internal work). The advantage is I have a very large creative input - the bad part is the 'can you shift this to the left half a pixel', then the next week 'can you shift this to the right one quarter of a pixel'. I am lucky to have very understanding, patient and intelligent customers which makes my job enjoyable :) I err on the side of preferring having lots of creative input.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
It is a part of my job, as others have already said. I do research and proof of concept prototype design. We also do quite a bit of improvisation when it comes to getting the bits and pieces of software and hardware to work together. Initiative is a requirement to do what we do. I think software in general needs people who take the initiative, many times management has no clue how to implement software and take the "does it work?" and "just make it work" approach.
It was broke, so I fixed it.
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
More often than I'd like, as odd as that sounds. But when you see a carload of drunks heading full tilt boogie towards a brick wall at 120mph, you've got to say SOMEthing, if only so you can work in peace.
-
More often than I'd like, as odd as that sounds. But when you see a carload of drunks heading full tilt boogie towards a brick wall at 120mph, you've got to say SOMEthing, if only so you can work in peace.
mikepwilson wrote:
a carload of drunks heading full tilt boogie towards a brick wall at 120mph,you've got to say SOMEthing
I would say WOW! Did you just see that!? Hopefully they are all lawyers.
It was broke, so I fixed it.
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
I tried twice: 1. To save hundreds of pages of printout each comprising 5 or 6 line URLs sent to every employee of the company. On average 5 pages per mailing every fortnight. When I suggested that putting this information on our intranet website and sending an email with a link, the response was, "we will take it under advisement": AKA you are a foreign no nothing, please don't tell us how to do our job. 2. I tried to explain to our management why the project I was working on was not being managed properly, and how the technical documentation was not clear enough for the developer (me) to produce a working system. Much the same response, i.e shut up and do your job. Lesson learned, keep your mouth shut and your head down.
Veni, vidi, abiit domum
-
I tried twice: 1. To save hundreds of pages of printout each comprising 5 or 6 line URLs sent to every employee of the company. On average 5 pages per mailing every fortnight. When I suggested that putting this information on our intranet website and sending an email with a link, the response was, "we will take it under advisement": AKA you are a foreign no nothing, please don't tell us how to do our job. 2. I tried to explain to our management why the project I was working on was not being managed properly, and how the technical documentation was not clear enough for the developer (me) to produce a working system. Much the same response, i.e shut up and do your job. Lesson learned, keep your mouth shut and your head down.
Veni, vidi, abiit domum
I would of said you were in the right and they at the very least should of listened and considered, developers are thinkers, it's what we're paid to do.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
-
I would of said you were in the right and they at the very least should of listened and considered, developers are thinkers, it's what we're paid to do.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
That assumes they were willing to accept that someone else may have known something that they did not. Our general experience with in-house departments was that they believed they knew everythig, and refused to accept that they could ever be in the wrong.
Veni, vidi, abiit domum
-
So as the subject states, how often do you take the initiative in your company? When you see a problem with a process or a way in which you think you can improve the codebase / system / application do you speak to someone higher up not with just a complaint but a resolve to fix this? I do and quite often if I can think of a suggestion as an improvement, when I was less experienced and more naive this used to be often without enough thought however now I go through my own little process to decide if I should talk to someone about an improvement. Will this help the company? Is it just me who thinks this? Is this proccess costly (performance, exspense etc) etc. So once again the question; How often do you take the initiative in your company?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
Simon Lee Shugar wrote:
do you speak to someone higher up not with just a complaint but a resolve to fix this?
..sometimes it's there for a reason.
Simon Lee Shugar wrote:
How often do you take the initiative in your company?
If it ain't broke, don't touch it.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
