|
Yeah, we have been trying to implement source control. Funny huh ?
Elephant elephant elephant, sunshine sunshine sunshine
|
|
|
|
|
Try to get him a separate project where he could unleash his creativity up to the final product.
Otherwise you are looking at a never ending hairy mess of a disaster, which will be sent back to you for minor "adjustments" 2 weeks before launch.
(my current situation)
modified 20-Oct-19 21:02pm.
|
|
|
|
|
The changes in the source aren't really the problem. The guy usually doesn't do anything anyway.
My problem is the "pay attention to me" attitude for such little things, and the annoying interruptions so that I can see what he manage to do.
I'm pretty sure he's done this so that he can say he was involved in the project (annoying). It's a pretty big deal for our company, and he's the one ultimately responsible for it. It's been getting a lot of attention recently because our demo was such a success. I think he wants to be able to say he contributed.
-- edit-
I'm the only one who's written code in the project,and that's typically the way it goes here. This behaviour just started after our demo.
Elephant elephant elephant, sunshine sunshine sunshine
|
|
|
|
|
loctrice wrote: the "pay attention to me" attitude
Wow, you know my BIL? Some people are just like that and I hate to psychoanalyze but usually they didn't get enough attention as children.
As a side-note, I have successfully avoided questions from a NIL (nephew-in-law) on how to build a cost analysis spreadsheet for his job.  I'll have to deal with it this afternoon or run the risk of upsetting that group. Fun! 
Good luck! I guess you are keeping backups in case he really screws something up!
"Go forth into the source" - Neal Morse
|
|
|
|
|
I make commits whenever I finish a feature.
He doesn't care to learn git so there's not much damage with that. I wasn't making backups other than that because it's been a solo project. I will need to be now. Or move it to vsonline(or github) so I can publish stable versions.
Elephant elephant elephant, sunshine sunshine sunshine
|
|
|
|
|
loctrice wrote: My problem is the "pay attention to me" attitude for such little things, and the annoying interruptions so that I can see what he manage to do.
Give him an 'at-a-boy' at the next staff meeting in front of a large audience. Show his contribution and shower him with mock praise.
Most people will see that you are mocking him and get a laugh out of it. 
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
Simply Elegant Designs Jim<</xml>
|
|
|
|
|
loctrice wrote: without telling me your making the changes, which is dangerous
Is this why he is telling you?
Is this "your" project, or the teams/company's project.
I learned a long time ago, not to get emotionally attached to "my" code, because it wasn't really "my" code. If the company decided to change 2 weeks of my work, a month later, so be it.
Also, you need to move any changes to a branched repository. I think a few people here already mentioned this.
|
|
|
|
|
Slacker007 wrote: without telling me your making the changes, which is dangerous
This was really just a side note because I didn't know there were any changes being made to the code, and he worked directly on my branch.
The actual part I was ranting about was the simple things he was jumping in to do, and then taking everyones time to point out how great of a job he was doing. Him actually doing tasks is not an issue, though we should make sure we use the source control if we're going to have more than just me working on it.
Elephant elephant elephant, sunshine sunshine sunshine
|
|
|
|
|
loctrice wrote: This was really just a side note because I didn't know there were any changes being made to the code, and he worked directly on my branch.
Problem solved. Refresh your branch from the repository before you make any additions to the code. Just say you did it as a precautionary measure because you made a mistake and wanted to be sure you didn't unintentionally introduce problems into the code base.
That is why code repositories are implemented.
If he complains make a branch for him and then it can be decided if his changes are folded in to the final project by whomever is doing release control.
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
Simply Elegant Designs Jim<</xml>
|
|
|
|
|
What's the point of learning to hit people?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I'm cutting weight for the 27th right now. You always got to ask yourself in this situation:
"Is this person really an elephanttard sunshine, or am I just feeling the cut"?
Elephant elephant elephant, sunshine sunshine sunshine
|
|
|
|
|
You try to help out, then some idiot re-posts your answer whilst at the same time claiming that your answer is incorrect..
[Edit] The duplicate answer has been deleted. I love CP but the Q&A section is a bit forked IMHO - just makes it feel like it's not worth the hassle getting involved 
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
You cannot blame CodeProject for the actions of a few idiots. The majority of people posting in Q&A do try to post useful responses, and treat their fellows with due respect.
|
|
|
|
|
The guy had a 65k reputation and "Legend" status - my guess is by doing the same thing across CP Q&A.
It wouldn't have been quite as bad if it hadn't been an easy question - the OP just needed a second set of eyes to spot his simple mistake.
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
Brent Jenkins wrote: The guy had a 65k reputation and "Legend" status - my guess is by doing the same thing across CP Q&A.
Sadly, that is quite possible.
Brent Jenkins wrote: the OP just needed a second set of eyes to spot his simple mistake.
Well I guess most of us have failed at that once or twice in our coding lives.
|
|
|
|
|
Brent Jenkins wrote: The guy had a 65k reputation and "Legend" status
Some people's rep is almost entirely made up of such activities.
|
|
|
|
|
|
I wasn't talking about just you!
|
|
|
|
|
*looks at Keef's 150k, turns and walks away*
veni bibi saltavi
|
|
|
|
|
I'll have you know I'm a legend author
[Edit]
And kinda a big thing on my own site!
[Edit Edit]
And the #186262nd person on Stack Overflow
|
|
|
|
|
Well I've got over 60 followers on Twitter so :bleeerrr:
veni bibi saltavi
|
|
|
|
|
Your mother and her sock puppets don't count! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Brent Jenkins wrote: The guy had a 65k reputation ...
It's not the usual suspect I was thinking of, then.
I recently had a fairly long argument with He Who Shall Not Be Named because I'd answered the question that the OP has asked, rather than the question that HWSNBN thought the OP meant. Apparently, telling the OP that something they didn't actually ask for can't be done is more important than telling them how to do what they actually asked for. 
We're currently waiting for the OP to clarify what they meant, but I'm not holding my breath.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard MacCutchan wrote: You cannot blame CodeProject for the actions of a few idiots.
You're right, it takes a glut of idiots to create what's happening in QA !
«I'm asked why doesn't C# implement feature X all the time. The answer's always the same: because no one ever designed, specified, implemented, tested, documented, shipped that feature. All six of those things are necessary to make a feature happen. They all cost huge amounts of time, effort and money.» Eric Lippert, Microsoft, 2009
|
|
|
|
|
You will always find member doing wrong (I done some myself), but that's not CP or the QA...Do and hassle a bit more...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
