|
long term? Everything is so Agile and short sighted these days. Quick and dirty
dev
|
|
|
|
|
So many of us tend to come off like we know more than we actually do. Most of us Google topics daily because we don't know or forgot how to do something (which means we don't know it). We always need to be excited about learning and always willing to learn something new.
|
|
|
|
|
My manager has kept on assigning me to work with a specific co-worker (name withheld to protect the innocent)... He does almost nothing to do anything with the software development projects... Just slackening (surfing) and using his "boss mode" (data storage server - web-based version) whenever he hears anyone walking toward his office. He tends to wait for me to complete my tasks then hand over his tasks to me. All he does was to "give command", nod his head, and looking "busy" at his office. ARGH!
I rather to work with someone who has good knowledge (like other co-worker who has been seriously working on the project with me - but now is in other group  )
|
|
|
|
|
The option should really say "Neither. I'll do his/her part of the project myself.", or the indeterminate "their" rather than assuming the male pronoun.
|
|
|
|
|
No; "his" is correct. "Their" is incorrect for an individual.
Even better would be for it to say, "I work alone".
|
|
|
|
|
|
Can't tell if serious or trolling.
Just in case: "Lighten up, Francis"
|
|
|
|
|
1) Someone who doesn't want to learn is trouble in this business. Change is the one constant.
2) An outsider, technology-wise, can bring a fresh perspective and perhaps new techniques for accomplishing the task at hand, as well as bringing fresh, naïve eyes to the code review.
3) It's lonely working alone, truly.
Therefore, I choose the learner.
|
|
|
|
|
You might reconsider if you have 2 weeks, or any other limited amount of time compared to the work to be done, to finish the project.
Then you should pick the guy that already know all about the job and start writing code without any further delays.
|
|
|
|
|
That's a good point, Alex.
|
|
|
|
|
Considering that rapid rate of change that our industry moves at I don't personally believe in experts of technology. I do however believe in experts in learning or at the very least people who embrace change and the challenge of always learning new things.
you want something inspirational??
|
|
|
|
|
I guess that makes you an expert in expertise ? ? ?
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Fortunately, it wasn't on a project. I taught myself VAX Macro Assembler.
He saw it was interesting and had me teach him: he picked it up quickly and we used to code competitively for the fun of it. Also used to hack the VAX cluster (buggy booger). Good memories.
It was with him that we took on Swords of Glass. Later, the first five or six Might and Magic.
"Time it was, and what a time it was, it was
A time of innocence, a time of confidences
Long ago, it must be, I have a photograph
Preserve your memories, they're all that's left you" - Paul Simon
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Are you saying you helped write the early M&M games?
If so, well done - they were good for their time (and still on my current PC thanks to GOG.com  )
|
|
|
|
|
OriginalGriff wrote: Are you saying you helped write the early M&M games?
Oh No! I wish!
We played as a team - just somehow the topic led me off-topic.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I've been there. I spent all my time transferring the content of my brain and the other three spent most of their time absorbing what I told them. Upshot was that this four-man team managed to perform the equivalent of one man-day per day.
|
|
|
|
|
But for a long run project, the productivity will eventually start to ramp up. Just need to spent more time to do code review with them at the beginning.
|
|
|
|
|
I should have added that this was specifically a short-duration team added to my one-man project to try to reduce the development overrun. A classic case of adding manpower to a failing project (cf. The Mythical Man Month, which I had read by then).
|
|
|
|
|
I'd add condition: There is enough time to include the new partner.
Or: The project is at the very beginning.
I've read "The mythical man month" when it was primary issued, so the graph of connecting the new member to the burning project is printed in the memory.
My English is permanently under construction. Be patient !!
|
|
|
|
|
If it's a short thing I would stick with the dinosaur.
Even if the other guy is super smart what I really need is to move things out of my way.
In short missions coaching is not an option.
If it's a long mission then the geek guy would be definitely be the choice.
Probably not because we could change technology but it's always good to have agile people in the team.
|
|
|
|
|
Posted my message "Condition to add" before seeing yours. Actually mine should be here as a reply.
My English is permanently under construction. Be patient !!
|
|
|
|
|
Interesting reply, which one do you consider the dinosaur, and which one is the geek?
It was broke, so I fixed it.
|
|
|
|
|
Dino is a gentile (or maybe not) way to refer to one that is super guru but on ancient tech.
It's not a bad thing if you like it and usually pays off a lot, like COBOL gurus in ancient systems!
|
|
|
|
|
Since every project spreads like chewing gum the dino is out, I'm afraid 
|
|
|
|
|
Could be, but still I could use the dino in the pressing stretch and get the agile guy for the long run if needed.
An approach like "Lets get this done quickly and if there's something else I'll rearrange the team"
It really depends on the scenario and project managements along with a good team leader plays an important part in this.
Of course the most logic answer is to get the savvy guy, but a team of savvy people tend not to be good.
In a team we need to have the stable guys that just do what they're told and they do it well.
It really doesn't matter if they know how to fly a plane it all that is required is to ride a bicycle.
If everybody in the team wants to make park the bike and build a rocket we're screwed 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
