9
meister
6y

More rants coming up.

1st

Working with a guy who I am not sure has the necessary experience to begin with.

The person who hired him told me to teach the guy for him to catch up to our project and its pace. He has some experience with Java. Which our project is being developed in java in a linux dev environment in a full stack way. So we handle front to infrastructure.

First day working with him and I saw this guy is trouble.

1st - doesn’t know effing git commands. Who doesn’t know git nowadays. Ok i can forgive him for that. But damn this guy’s learning curve is so slow. After s month of joining, he still has to look up the commands in his photo cheatsheet.
2nd - doesn’t know linux basic cli commands like cd, ls, rm. not an ounce of knowledge. He told me he is used to developing in Windows. Now this. I can’t forgive him for not knowing this shit. cd (change dir) even exists in windows command line. He even has guts to say to everyone he wants to try working in our servers. The HORROR!
3rd - not sure if knowing junit and matchers of hamcrest, if you are working with Java is a must. But this guy doesn’t understand Matchers of Junit. How the fuck did he ensure effing quality in his prev work.

All in all, seems like this guy doesn’t understand the basics of current development tools.

Comments
  • 2
    I don’t know much about Java, but I know there are a lot of GUI tools for Windows which take away the need for CLI experience. Especially for git. As was my experience college, most of my fellow students were scared to do anything command line related
  • 2
    You're working and that guy is learning. So simple.
  • 1
    It's 2018, there's a gui for everything so it's absolutely possible to use all tools without knowing commands.
  • 1
    I think you should be more pacient with the guy. When I was a fresh grad, I didn't know shit about git nor testing, all I knew was basic OOP with Java. I felt like a complete and useless idiot during my first job, but the senior devs where pacient and helped me every time I got lost. Now I'm a senior myself and can do anything on my own, also help new junior devs on their way.
  • 0
    So I’m reading through and there’s a few thing ya mention I don’t even know.. haha 😅 try to give him some time and patience? Usually people catch on. I would love my first co-worker to teach me to be a mentor sort of. Help me out ya know?
  • 1
    @FerDensetsu that's the spirit, in my first job our only senior dev wasnt so helpfull at all.
  • 0
    To all,
    I understand all of your concerns.
    We got alot of paid interns joining our team and we were impressed with their knowledge. Maybe our team got spoiled with the people we got.

    He joined our team not as a fresh grad but as an experienced engineer. He has 8 years of enginering experience.

    I know we have to give patience and time for new people regardless of experience to get used to devprocess.

    Either I hate the guy that hired him for not properly filtering skillsets. (We are doing dev on a Linux Environment, why would you get a guy who doesn’t have an ounce of experience in Linux). Or the guy for lying in his experience. (How the heck would you pass the interview then?)
  • 0
    @turturtles we are not using windows for our dev. We are in Linux. I am not familiar with client UI for git in linux, maybe I can provide him some clis.

    @theScientist he is. Quite frustratingly slow for an experienced engineer.

    @Biggy i would totally be chill if it was a junior dev

    @CWins i know. But it is frustrating to know that someone got a job due to fake experience. The team’s productivity has to suffer.

    I don’t really care if you have faked your resume just to get the job, because I know google is going to be your friend.
  • 0
    Anyway, in my opinion. If you are an experienced engineer, you have to have at least 1 knowledge of top tools and top language.

    Joining a company as an experienced engineer, you will probably mentored mainly on the project specs and shit.
Add Comment