Ttdfjt

And he is a greater asset than me to the company

No. An abusive co-worker is never a greater asset to the company.

Everyone in your company, regardless of their level, has the right to be treated with respect - from the cleaner to the CEO. Your manager should know this, and simply moving people around this guy isn't dealing with the situation.

It looks as though this guy is known for this behaviour and people have either avoided or worked around him. Ask your peers how they've handled this, how did they report this behaviour, and how they dealt with it.

If possible, record this behaviour happening (whether toward you or someone else) and take this to HR. Remind your manager that allowing this situation to carry on isn't an acceptable way of dealing with it.

It's possible that this guy's defense is an autism-related condition and that "that's the way he is". That, however, is his problem. Abusive behaviour should not be tolerated - from anyone.

It's fairly obvious that this guy is both obfuscating and protecting his code base in order to protect his job. Again, this situation cannot be allowed to happen (for obvious reasons).

You should have clear examples showing:

• that you could not finish your work without touching "his" code;


• "his" code actually is broken.

I used "his" because the code belongs to the company.

Additionally, keep reporting (to the boss and HR) his behavior as often as needed. Show how his work is sloppy. Complain that you are forced to work in an unprofessional environment because of this colleague, and that this affects both you professional performance AND your private life - since a difficult day at work cannot be "magically" forgotten at the end of the "shift".

Learn as fast as possible, you might have the (nice) surprise to be promoted to do his work.

You might want to discuss with HR too, yelling is not welcome in any company.

While looking for another job is definitely one alternative, I would not say that this workplace is toxic, but only one colleague. Yes, it is difficult. And it is likely that he will go away as soon as somebody can take over his tasks. Since you are a beginner, you might want to consider having a little more patience (if you can do it, and if you want). Also, think about this: do you have any guarantee that the next job will be perfect? I changed jobs several times, and I am yet to find one which comes close to "perfect".

What matters most here is not the senior jerk, but how your manager reacts. It sounds like the manager is entirely aware of the jerk's failings, and that he's tired of the jerk pushing new people out. They may well be seeing whether you're able to replace him if they get rid of him (either by firing him or by transferring him out somewhere). So in your place I'd do the following:

• Work hard, keeping to your own area as much as possible, to demonstrate you can indeed do the job at the same level. If you find an error in jerk's code, show it to the manager but not the jerk, it's manager's job to deal with that.


• Don't talk to jerk at all if at all possible, and in fact make sure all your interactions at least start in email.


• Keep a log of incidents like this one, including date, time, witnesses, and quotes as exact as possible. This may be useful for you in negotiating your exit, it may be equally useful to your manager in firing him. Keep all emails.


• Mark 3 months from now in your calendar. Start polishing your resume now. At 2 months at the latest, make sure you have a full-blown job search going, so that there is some resolution by the 3 months promised. There must be light at the end of your tunnel if you want to survive this as a sane person.


• Make sure you tell your manager that you will hold him to his promise timewise, because enduring this situation is not viable. Be sure to remind him of it every month at least.

I am sorry he is like this. However, he may seem to be a bigger asset, what he really is to that company is a huge danger. As a coding team, you should be trained to have your code on a company GIT server and no code should live on any one computer. Daily pushes of that code should be done. The fact that all code exists on his computer alone is a huge problem if he decides not to come to work anymore or gets his by a bus. The company is too in experienced to know he has set them up for doom. You would require a staging server and a production server to push code. You would have access to produce code based upon your assignment, pass it to him for testing and he would make the decision to push to production.

Code should be written in such a standard that anyone can edit it as it should be easy to understand. Even if you did edit it, and it was incorrect, so what. It would still need to pass testing, make it to the staging server for testing and then to production. What he is, is an idiot wannabe devops guy pretending to be important like a mutt on the street with a bone.

You are supposed to be a team. He is supposed to be training you to fit into his code, habits and the company so that you too are an asset in the event of his absence. It would seem that company and manager have not thought of that and thus are doomed to fail.

I would recommend that if they are not team oriented and since management is so poor, you would be better off, moving on. Let them find another programmer. Proper management is providing direction and guidance to coworkers and subordinates. They are all failing at it. The end result will be the deterioration of your own personality and it is not worth it.

So let me start with your yelling friend. He's highly protective of his code. Why would that be ? Are you just as protective and not letting anyone see a single line, or is your code in the repository free for anyone in the company to see ?

That 'dev' over here is perfectly aware how bad his code is, and how low his coding skills are. He understands that if you see his code in its entirety it won't take you long to rewrite his bullshit. It won't take much longer after that for you to explain to management that this "irreplaceable developer" is actually quite bad and should be going. I'm guessing that's the core to the reaction and the behavior. They are afraid you'll introduce the correct methodologies and he'll be SOL trying to change industries as no one would hire him.

I wasn't going to suggest job hunting but given your manager's reaction and the hint I'm getting that developing isn't highly regarded in this company (No reppos ?) it might be time to go.

I just thought I'd chuck a little advice in as I went through the exact (and I mean EXACT) same experience during my apprenticeship.

The senior developer made terrible code, wouldn't allow me to fix any problems he clearly made, and blamed me for every mistake even if it was his fault. He would yell, throw tantrums, call me an idiot, and even ask if I were stoned.

This guy was allegedly ex-military, and not a very nice person.

I ended up standing up to him (as an apprentice), scared that I would lose my job as I had a newborn baby to support. But still I did it, and got separated from him at work, expanded my skills, got a pay rise and am now getting tons of other job offers.

I waited through 2 years of torment from that guy before standing up; there were countless conversations with my manager and director (who never got rid of him and still hasn't). I'd say: stand up, man. Tell him he's ridiculous, demand to be moved/separated from him and search for a new job whilst you're at it!
That company clearly doesn't appreciate or respect you and will probably be taking advantage of you more the longer you stay.

Most of all: stay strong, I cried twice after some yelling and threats from the guy I worked with. It's fine to do that, because things get to us. You just have to realize when enough is enough and take the plunge.

Keep your chin up, man.

He is absolutely right, you shouldn’t touch his code. However, the code that the company uses that he wrote is not his code. It is owned by the company, not by him. He has no rights to it.

As far as that code is concerned, agree with your manager whether (a) you have the company’s permission to modify code he wrote, obviously doing code reviews etc., or (b) whether you should send the developer requests to make necessary changes to his code, Cc’d to your manager, and escalated if the changes don’t happen in a timely manner.

BTW. In most companies, the worst you can do is retribution. Doing something that gets complaints is often harmless, but retribution against the complainant gets you fired. Tell him that.

Yup... you'll encounter developers like that as you walk the path. They never document anything, won't help you... and their code is usually trash.

Personally I like to challenge people like this. Get on his turf, step on his toes, and mess with him a bit. Start doing his job. Build a prototype for a parallel system, but do it right, and make improvements. You're better than him anyway.

If he starts yelling, just sit and smile at him. Really, what can he do? He's just blowing smoke. The whole office will love you for it.

I love to hear 'em scream >.<

You may be over your head at this company, and it may not be worth staying or trying to resolve things. Other answers have made many good points about resolving this while remaining at the company, but I would like to suggest leaving as the best option.

This senior developer needs to be replaced, not just because of his abusive behavior, but because of the way he has designed your company's systems. He has set himself up as a single point of failure by hoarding and obscuring code, and it is likely that no one else in the company knows enough about IT to recognize this as a problem. Are there things that no one else has credentials to? If he got hit by a bus, would you even be able to access the machine he keeps your company's code on?

You have made it clear that this is your first job as a developer. While you may be capable of replacing him, you are still a junior developer. Even if he were completely willing to train you as his replacement, it would probably still not be a good idea for you or the company. You would benefit much more from being able to work in a team and learn from others. Consider your hostile senior dev: there is no one around (besides you) to point out his harmful practices. Working alone at this early stage of your career could set you up to have bad habits of your own.
(Granted, if he were willing to train you as a replacement, then he would be a very different person and not need to be replaced.)

The best route for this company would be to hire a senior developer with the goal of replacing the hostile developer - someone with not just the knowledge, but years of experience. The best route for you would be to find another job, one where you have GOOD examples to learn from, instead of just examples of what NOT to do.