Just had a junior/mid dev who worked in our company for around 3 months quit because in his words "he is unable to win any argument".

I saw his comments in MR's and other seniors were just being meticulous. Had he compromised a little or atleast got to knew the devs in person and took this offline most of his problems would have been resolved. Never scheduled any meetings before implementing stuff, he just followed his gut and then shot himself in the foot plenty of times.

Personally I think it wasnt even a skill issue but a communication issue. We have a relaxed culture where u can work in the office or fully remotely so the guy came in on his first day, picked up his laptop and we never saw him. Tried to invite him for an afterwork beer or some activities, he never accepted.

If he had met the devs in person he would have seen that:

1. One guy has OCD and he never agrees with anyone but if theres a timeline hes able to make compromises and hes actually chill
2. Second guy is also a perfectionist but has mentor capabilities and you can always go to him about anything and he helps to mediate with the first guy. You can run everything through this guy and he will never give you shit
3. Third guy in the team is just a junior hotshot whos a bit insecure and disagrees in comments just because he can. But he can be dealt with very quickly with showing a little backbone.

Like seriously these are just people that you can deal very easily when u know their personalities. Instead he saw everyone in company as these 2D robots that he wasnt able to win his arguments against.

Communication shouldnt happen only in standups and MR comment section. U have to learn to deal with people otherwise u will burn urself out like this guy and quit.

  • 0
  • 0
  • 2
    Guy 1 sounds like a pain to work with.

    Guy 2 sounds like a pain to work with but less so than Guy 1.

    Guy 3 sounds like a pain to work with more so than guy 1 and 2 combined.

    They can be chill, but that doesn't excuse them being a pain in the ass. Sounds like Guy 1 and 3 needs to be more self-aware since this is clearly a *thing* with them. Maybe Guy 2 should try to offset that or be less nitpicky.
  • 6
    @nitnip You completely missed the point. Nobody is ideal. If your level is junior/mid and when you join the company your only interaction is standups and comments in MR's you are destined to run into many problems, not even technical ones but also domain ones.

    Especially if you implement whatever latest standard google results came up just because it's latest, withour even having a meeting with anyone and so on. The app has 700k lines of code and 56 modules.

    I dont even think that he even received a proper onboarding. Could be a great solo dev but but hes not that experienced and wasnt able to be a teamplayer.

    But I guess for you as a senior if such junior hotshot joins your team and makes unnecessary trouble it would be a pleasure to work with him right?
  • 1
    @topsecret230 Sounds like your company is absolutely shit when it comes to onboarding. You didn't make a good case for me in that rant.

    I'm just telling you that I don't know your guys. And from the point of view of someone who doesn't know them, they sound like a pain to work with given what little you've said about them.

    Maybe if I knew them I'd be super friendly with them, and forgive/understand their nitpickiness. I don't, so they seem like a pain.

    If a "hot shot junior" joined my non-existant company. Maybe I wouldn't give them full write access to the repos until after the onboarding, and then give them some actual tasks that need doing instead of letting the new junior roam free and try to make himself useful.
  • 2
    @nitnip from my pov if you are a mid or a senior who is worth your salt you should be able to join a new company, get all access on day1 and on day2 you pull the project, pick a simple bug and start learning from there how everything works and ask your assigned buddy questions (ofc he gives you an overview during your first days)

    Other newcomers tend to bury themselves in documentation for first 1 or 2 months and they dont ask questions which means they will have a very hard time delivering. I mean even seniors ask lots of questions when they join lol.
  • 2
    Totally agree to op. It's a huge dissapointment for those hyper introverts and social anxious ppl but even software development requires human interaction. Those seniors might be idiots or not, but it's the team he applied to. To think you can get part of a team without any efford of actually getting to know them is heartbreaking naive. Rational arguments is an illusion, any discussion has a human factor in it. It's even hard to understand any code base without talking to ppl behind it, because clean code is an utopia way more unrealistic than world peace.
    Thus having said i would also, you guys, as a team, should maybe think of a good onboarding process which maybe requires a couple of week being on-site. It not only a cliche that many devs lack social skills (actually having to interact with a computer rather than with ppl is what makes the job attractive to them), and being the new one is not easy for anyone anyway. It's true that as a new one, you have to ask questions all day, but the team must create a safe atmosphere for it (which is quite difficult, but also possible if they are working remotely).
  • 1
    This (and the fact that I often work with hardware) is still the reason I come into the office every day.
  • 1
    @LotsOfCaffeine how do you get into working with more hardware?
  • 1
    @chonky-quiche I write embedded software which runs on hardware system with custom, in-house made stuff.

    Nowadays we can do 99% remotely, we even got remote controlled power plugs so we can hard reset the systems in the lab. Of course plugging and unplugging is still done by hand.

    I still prefer working in office mostly for social reasons.
  • 1
    @LotsOfCaffeine how do we get into this field as a web dev
  • 1
    @chonky-quiche idk I got here right after finishing my bachelors. The stuff I work on is very high level too, we have an operating system and an Ethernet port.

    I guess you could just see around if you can find job offers in that area. But you must be prepared to work with C, C++ and all of the quirks of those Eco systems.
Add Comment