Should I tomorrow correct that senior guy about the term ray casting that I was true in-front of everyone and clear up my image :/ ?

Should I tomorrow correct that senior guy about the term ray casting that I was true in-front of everyone and clear up my image :/ ?

No, why in the world would you do something like that?

That actually might get you fired, or at the very least make people think badly of you, and would probably even make some idiot cause more problems just to see what you will do.

I mean think about how that will sound: "Last week you were an idiot to me for making me look bad, look here I was right!!! Everyone look I was right!!". What would you think if someone else did that?

Being wrong isn't even that bad... if you can choose between people thinking you were wrong even though you were right, and people knowing you are right but thinking you care that much about it... just let them think you were wrong, it's better for you.

Smile and never say a thing and keep doing good work, and find your next job ASAP and try your luck elsewhere. And when you quit, still smile and thank everyone for a good time.

Also, you don't really seem to like it where you are... maybe try to go where you're happy and like people.

Also, you don't really seem to like it where you are... maybe try to go where you're happy and like people.

You're so clever, you felt what are behind the words. Yes I'm not happy where I'm, Austria.

They're not going to fire you for a couple of small mistakes if you've only got 7 months experience. That's what's expected from a junior dev. Hell, two mistakes is doing pretty well.

If they are inclined to fire you, they're assholes and you don't want to work there anyway -- the only thing worse than feeling a bit insecure is when the whole of the rest of the company is jumpy as well because no-one works well when they're on edge and everyone's tempers get frayed.

The guy who's shouting in public about your mistakes is already demonstrating assholeness. Just accept that he's an over-reactor. Learn some strategies for coping with the over-reactions[1]. That's not how you train people and bluntly he needs moving somewhere where his personal issues won't damage the company's investment in taking on and training new people. Chances are you'll just have him explode at you every couple of weeks. Sorry about that, that's people. There is a chance it's not actually permanent; he may be under other stresses you can't see which may go away.

And yeah, like Erik says, just let it lie. Honestly, if he goes off the wall every other week the rest of the team are probably used to just ignoring the content of the noise anyway; their reaction's not going to be judging you, more gratitude that it's not THEM being yelled at.

[1] Alcohol works, but I'm not sure I'd recommend it. Meditation helps. Lunch-time shoe shopping used to get me through bad times but that's a girl thing. Put up with it for a few years, get some credit on your CV from having been involved in stuff and then leave. If you're feeling brave, you could mention the mutual support within the team not being all you'd hoped for in your exit interview and let HR fill in the blanks.

I'm not sure what exactly is the performance expected from me.

Talk to your boss.

This applies to the OP as well.

Most places (inside and outside the industry) have regular one-on-one meetings between you and your manager. That is the place to discuss what is expected, if you are meeting expectations, what you can do better at.

It is also the place to discuss feeling like someone is intimidating you or calling you out in public. They can watch for it as well, and if they see a pattern of some senior person knocking down junior people then they as the managers should get back to both people; the abuser to tell them to stop, and the abused to agree that it is happening and to tell them how they are going to correct it.

Test, test, test your code. Everyone makes mistakes, even professionals, even those with 1000 years of experience (exaggerated). Your brain is so fragile that your thinking can be affected by the time you wake up/sleep, what you ate, what you drank, what your friend just told you, or a bug buzzing around your monitor. Pretty much everything. Any developer who refuses to write tests is only fooling himself.

Your coworker is immature. Any senior engineer would've understood that everyone makes mistakes, and not make a big deal out of it. He's not a team player, and plays the blame game. If your manager is anywhere smart, he'd boot him instead of you. Act professional, admit your mistakes, correct your mistakes, and don't play the blame game. What you did was right. If the company decided to boot you, it's their loss. Really. Keeping that coworker would damage the company more.