I give up... more source control...
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
El Corazon wrote:
prefers all tools to be command line
And apparently doesn't know how to use the 'Net, since SVN has plenty of good command line tools. :rolleyes:
El Corazon wrote:
Another submits all the time and breaks the build at least once a week
Have you considered setting up build scripts that roll back the last revision whenever the build breaks? :~
El Corazon wrote:
Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more.
Tell him he can go back to using VSS when he trades in his PC for this computer[^]. I'm sure VSS works just fine with it. :-\
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
El Corazon wrote:
Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more.
You should tell him that SVN works the way it does by design. You see, unlike VSS, SVN was actually designed. VSS was just something that accidentally came to existence when a Microsoft employee happened to spill coffee in the keyboard. Seriously.. with a team like that, you guys need to dish out warnings of the sterner kind.
-- Kein Mitleid Für Die Mehrheit
-
El Corazon wrote:
Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more.
You should tell him that SVN works the way it does by design. You see, unlike VSS, SVN was actually designed. VSS was just something that accidentally came to existence when a Microsoft employee happened to spill coffee in the keyboard. Seriously.. with a team like that, you guys need to dish out warnings of the sterner kind.
-- Kein Mitleid Für Die Mehrheit
Jörgen Sigvardsson wrote:
VSS was just something that accidentally came to existence when a Microsoft employee happened to spill coffee in the keyboard.
I thought VSS was what happened when Microsoft bought it off a company that spilled coffee on the keyboard.
Deja View - the feeling that you've seen this post before.
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
He who breaks the evening build buys donuts for the team the next day.
MrPlankton
-
Jörgen Sigvardsson wrote:
VSS was just something that accidentally came to existence when a Microsoft employee happened to spill coffee in the keyboard.
I thought VSS was what happened when Microsoft bought it off a company that spilled coffee on the keyboard.
Deja View - the feeling that you've seen this post before.
I just looked at your profile, you are a CEO , What the hell are you doing here? This is CEO free zone.Anyways I need to get these things out of my chess, I still have them from my x-job: 1- Stop hiring id**ts ! 2- Being a CEO does not mean you are Project manager, development manager, programmer and DataBase Adminstrator ! Have a good day !
-
I just looked at your profile, you are a CEO , What the hell are you doing here? This is CEO free zone.Anyways I need to get these things out of my chess, I still have them from my x-job: 1- Stop hiring id**ts ! 2- Being a CEO does not mean you are Project manager, development manager, programmer and DataBase Adminstrator ! Have a good day !
Bassam Saoud wrote:
I just looked at your profile, you are a CEO , What the hell are you doing here?
I'm actually an MD (Managing Director - not Doctor), but they don't have MD in the drop down.
Bassam Saoud wrote:
Being a CEO does not mean you are Project manager, development manager, programmer and DataBase Adminstrator !
No - but it does mean that you're isolated from the people who'll tell you this by a huge layer of suckups.
Deja View - the feeling that you've seen this post before.
-
Bassam Saoud wrote:
I just looked at your profile, you are a CEO , What the hell are you doing here?
I'm actually an MD (Managing Director - not Doctor), but they don't have MD in the drop down.
Bassam Saoud wrote:
Being a CEO does not mean you are Project manager, development manager, programmer and DataBase Adminstrator !
No - but it does mean that you're isolated from the people who'll tell you this by a huge layer of suckups.
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
No - but it does mean that you're isolated from the people who'll tell you this by a huge layer of suckups
you call them suckups, I call them idiots.I heard last month that the company I was refering to closed. 50 people i.e. 50 families lost an income and that is in freakin lebanon man, they will not find a substitue anytime soon. Reasons, bad Management: - Suckups - Nothing get done - No problem get reported.
-
Pete O'Hanlon wrote:
No - but it does mean that you're isolated from the people who'll tell you this by a huge layer of suckups
you call them suckups, I call them idiots.I heard last month that the company I was refering to closed. 50 people i.e. 50 families lost an income and that is in freakin lebanon man, they will not find a substitue anytime soon. Reasons, bad Management: - Suckups - Nothing get done - No problem get reported.
When you think about it, nobody likes to tell the person above them about problems. So, the CEO is being "protected" from bad news by everybody below him. He couldn't tell you if it was raining if he looked out the window.
Deja View - the feeling that you've seen this post before.
-
When you think about it, nobody likes to tell the person above them about problems. So, the CEO is being "protected" from bad news by everybody below him. He couldn't tell you if it was raining if he looked out the window.
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
When you think about it, nobody likes to tell the person above them about problems.
I always tell my suprivisor in a very clear and professional way any problem I have. Between, in that job, I was the only person who brought up the problem, but nothing change so I left. I brought it up with my immediate manager nothing changed. Then we had this "looking to the future" meeting with CEO and president present, I brought the problem up again. Nothing happened. I knew then that my career is not with that company. Imagine ten of your core team developers leaving the company with no questions asked.
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
OK OK, it's easy. You look at him with those helpless kitten eyes, lean forwards so he isn't looking at your face, say in a soft husky voice "There is something I'd like you to do for me.", lean back and smile slightly then... Go into full PMT ninja mode and scream "Check in the code when you're told and after you've checked the build works or you'll get the same as the last guy! :mad: :laugh: Just don't ask me what happened to the last guy :-O
Visit http://www.notreadytogiveup.com/[^] and do something special today.
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
Do you have a QA department or release manager? Someone needs to be in control of releases and hopefully releases are pushed to a testing environment. Are you using a build server with something like CruiseControl.NET?
Todd Smith
-
Marc Clifton wrote:
I hope I don't go schizo.
Was that you or your evil twin that said that?
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
Was that you or your evil twin that said that?
My evil twin. No it wasn't! It was you! Hah, always blaming the good guy, aren't you? Well, you're the one that's always optimistic and telling the client "no problem!" :rolleyes: ;P Marc & Marc
-
Pete O'Hanlon wrote:
It's MTL - Marc's Trashing Language.
Hehe. I've been reworking some C++ code for client (I'm a rocket scientist again, sort of :jig: ) that resurrected a project 8 years old. OMG. It's so wierd going back to C++. I hope I don't go schizo. Marc
Heh - I've got a proof of concept project on the go at the moment using Haskell[^] on the client side (using libcurl to provide very, very easy to program HTTP access), Python for the web service layer and C# for Windows services providing server-side functionality behind the web layer. Admittedly the Haskell is as much for a learning exercise as anything (and a very pleasant experience it's been), as is part of the C# (a monitoring app on the server is my first taste of WPF :-)), but it's still gratifying that it's all worked together very easily.
-
Do you have a QA department or release manager? Someone needs to be in control of releases and hopefully releases are pushed to a testing environment. Are you using a build server with something like CruiseControl.NET?
Todd Smith
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
"I'm givin' ya all she's got Captain!"
WE ARE DYSLEXIC OF BORG. Refutance is systile. Your a$$ will be laminated.
-
Do you have a QA department or release manager? Someone needs to be in control of releases and hopefully releases are pushed to a testing environment. Are you using a build server with something like CruiseControl.NET?
Todd Smith
Todd Smith wrote:
Do you have a QA department or release manager?
Not for 10 years! he was laid off at the last lay off. I am the QA, mostly because this is my "baby" I started it all on my own in 1994 when no one thought it could be done, and especially not by some no-body kid without any edjumakation! I was just a hick kid from a hick town in NM, with a tech certificumacation from a hick school in hick-town oklahoma (Tulsa). :) I have pride in this work, so I am Scotty, and QA.
-
And if so do they get support from the management?
Visit http://www.notreadytogiveup.com/[^] and do something special today.
Trollslayer wrote:
And if so do they get support from the management?
lots of support, as long as it is only verbal, doesn't require punative action, $$, or new hardware (or chairs -- chairs were a 12 year battle, our last set were govt. rejects tossed at the dumpster our building raided the dumpster till it was empty). As long as management doesn't have to do anything, sign anything, or buy anything, I have their 100% support!
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
[helpful_info] I've used SVN to test out what it has. It is pretty cool, bringing back the good old days of using the command line for fetching and committing files. As others have mentioned, you could create a short little script that checks in stuff into the SVN repository or get a helper utility such as Ankh (adds tools inside Visual Studio for working with SVN repositories) or even Tortoise SVN which adds Windows Explorer commands for working with files outside of Visual Studio. If you can go all-out, I recommend Source Gear's Fortress or Vault solutions for version control. [/helpful_info] [fun_project] There are always options out there for aiding in even the most mundane tasks. Furthermore, we're developers. If we see something missing that seems like it would help in developing or managing something, roll your own and distribute it onto the masses. [/fun_project]
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
Your team needs therapy. Kjetil
-
We have one programmer who wants it kept a file system with directory structure that is nested almost as deep as his code, doesn't like branch/merge and prefers all tools to be command line. Another submits all the time and breaks the build at least once a week (and is on vacation after making one such fatal commit before leaving). Another who submits rarely complaining that svn doesn't act enough like VSS and when it does he will do it more. A few others do what ever they want because they don't share and don't team, and will not either. yet when there is a problem, I am supposed to be "Scotty" and get everything fixed. I don't want this trouble. If my company was only doing good enough to pay health insurance... gonna hide in my office for fifteen minutes before I shift to Scotty mode. I need a (tm)Trollslayer method for dealing with teams... I wonder if she'll contract out to teach the (tm)Trollslayer method.... *sigh*
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
Dont know if I understand correctly, but already had a look on Visual Studio Team System (Server)? ... there are some good webcasts out there.