I'd like to share a story of a dev (details I will hide cause he may be reading this).
Once upon a time, there was a dev who had 10 years of experience working in 7 to 8 big companies. He had the most impeccable resume. Worked with a stream of technologies. iOS Native, Angular, CI/CD, Flutter, ASP, AWS, Azure, Java... you name it, he had everything. He was not lying either. HR rang up most of his previous companies and they all spoke well of him.
We hired him and assigned him to a spanking new project. It's any developer's dream. We wanted to make sure the project will be done by the best. We tasked him to set up the initial commits, CICD pipelines, etc.
But surprise!
This guy can't build Sh$T!
He doesn't know how to start at all! 2 weeks pass and he wrote the amount of code of what a college grad would write in 3 days.
Management was furious and he was getting anxious. In his vulnerable moments, he opened up to a coworker. All this while he had only worked in big companies. Every year he would change jobs. His task was updating existing projects, never building anything new. The teams were big and his lack of coding skills was shielded by the scrum i.e. his experience was only in executing tasks and building upon other people's code. Eventually, he left.
Lesson's learned: "A guy can play to most awesome guitar riffs, but never compose a song of his own"
They are 2 different skills
Have you had any experience with someone like this?
Dość ciekawy przypadek i w sumie nie uważam że gość jest z definicji zły, bo nie ma się czasem wpływu do jakich projektów się wpadnie oraz "modern" development - narzędzia, best practices itd. bardzo szybko się zmieniają oraz generalnie maintenance to jest trochę inny skillset
chociaż z drugiej strony 2 tygodnie i nic sensownego?
co somdzicie kamraci
czy aż tak dziwne jest że doświadczeni devowie mają problem ze stworzeniem sensownych fundamentów projektu, czy może jednak jak ktoś trafi na utrzymanie, to może tak się stać?