I'm a Senior DevOps Architect and publish most of my projects as open source. I have a wife, a son and a real life in Hamm, Germany. In my part-time I enjoy making games, music and acting. (He/him)
What I found pretty disturbing to see is brand new developers coming directly from the University doesn't know their basic tools. Like how to handle a vcs or an IDE or a build system. Maybe universities don't teach that stuff, but it's more important than all of the complex standard algorithms they do teach.
And I expect developers to keep track with current developments (like i.e. how to work with containers) without the employer specifically asking for it. We're on a job that is never gonna stop evolving, so we need to keep up.
But aside from that I expect that a new developer knows when to close the lid of their laptop and do something completely different as a hobby.
Like I said, this job requires a lot of commitment that can't be handled properly without a good life balance.
So welcome to our world. All the best for you career! 😊
I'm a Senior DevOps Architect and publish most of my projects as open source. I have a wife, a son and a real life in Hamm, Germany. In my part-time I enjoy making games, music and acting. (He/him)
Absolutely true. I'd test new engineers differently. I'd poke around in the tools knowledge and how willing the candidate is to keep on learning. And then only left would be to estimate, if they fit into the team socially. Those are the most important parts imho. (Exactly like you mentioned in your other comment)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What I found pretty disturbing to see is brand new developers coming directly from the University doesn't know their basic tools. Like how to handle a vcs or an IDE or a build system. Maybe universities don't teach that stuff, but it's more important than all of the complex standard algorithms they do teach.
And I expect developers to keep track with current developments (like i.e. how to work with containers) without the employer specifically asking for it. We're on a job that is never gonna stop evolving, so we need to keep up.
But aside from that I expect that a new developer knows when to close the lid of their laptop and do something completely different as a hobby.
Like I said, this job requires a lot of commitment that can't be handled properly without a good life balance.
So welcome to our world. All the best for you career! 😊
Meanwhile hiring managers ask questions like "Can you do bubble sort on the whiteboard?" So, I wouldn't blame only the universities for that.
Absolutely true. I'd test new engineers differently. I'd poke around in the tools knowledge and how willing the candidate is to keep on learning. And then only left would be to estimate, if they fit into the team socially. Those are the most important parts imho. (Exactly like you mentioned in your other comment)