How do you feel about different versions of frameworks/libraries? E.g. Drupal 8 is a completely different beast than all previous versions. If I want a Drupal 8 developer, somebody who knows Drupal from the start is not necessarily the right fit, if he/she didn't do anything in Drupal 8 yet.
Tell me about it. I've been a contract Drupal developer for 11 years (started on the tail end of Drupal 5).
Drupal 8 is awesome. I love it (thank you, Symfony!).
My first D8 job was taking over a project that was the most appalling hack. Clearly written by someone who was clueless about how D8 does things. The guy was using D6 techniques.
So I did my best, tried to move the site to proper D8 while doing all the fixes and new implementation work. Then I had to brief one of the permie Drupal staff on the site - this person was also completely clueless about D8.
"You know how the config works, right?" "Features?" "NO!"
"How about services? Controllers? Events and subscribers?" [Blank look]
(I did not lose my cool at the time, of course, but really?)
I take my job seriously but I was lucky to get the job at all, because "no Drupal 8 experience".
Yeah, we mostly look for D8 experience, but we'd also look at Symfony or other OO framework experience. I'm not the best interviewer, but I can usually spot when somebody's bullshitting his way through an interview. So if somebody knows the concepts that are important in D8 (Dependency injection anyone), they should be fine.
I hate when people don't know something and just start hacking instead of educating themselves. I work in an architect function now, so my development skills are waning, and I'm so happy I have a team of devs who have my back and are patient with my questions :)
It's a good thing you kept your cool and I'm glad you got that job. Keep on being patient and educating people, the programming world needs it :)
I think in the example you've given, it's worth listing them separately.
To be honest, I would never expect a recruiter to take this page at all seriously, but if you were using it to find Drupal 8 developers, and experience with Drupal 8 is key, then it makes sense for them to be split out.
Thanks for the quick reply!
I think this tool is gonna start living a life of it's own, so I'd anticipate on that by defining some guidelines, if you have the time to do that.
It is mostly cool because now I can just reference a site when recruiters call me with impossible demands :D
Yes and no. If you'd had to choose between somebody that knew a framework inside/out or somebody with no experience, you'd choose the first person anytime like most recruiters/interviewers probably would. Unless you have similar and relevant experience, like e.g. for Drupal 8, it would be Symfony mostly.
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.
How do you feel about different versions of frameworks/libraries? E.g. Drupal 8 is a completely different beast than all previous versions. If I want a Drupal 8 developer, somebody who knows Drupal from the start is not necessarily the right fit, if he/she didn't do anything in Drupal 8 yet.
Tell me about it. I've been a contract Drupal developer for 11 years (started on the tail end of Drupal 5).
Drupal 8 is awesome. I love it (thank you, Symfony!).
My first D8 job was taking over a project that was the most appalling hack. Clearly written by someone who was clueless about how D8 does things. The guy was using D6 techniques.
So I did my best, tried to move the site to proper D8 while doing all the fixes and new implementation work. Then I had to brief one of the permie Drupal staff on the site - this person was also completely clueless about D8.
"You know how the config works, right?" "Features?" "NO!"
"How about services? Controllers? Events and subscribers?" [Blank look]
(I did not lose my cool at the time, of course, but really?)
I take my job seriously but I was lucky to get the job at all, because "no Drupal 8 experience".
Yeah, we mostly look for D8 experience, but we'd also look at Symfony or other OO framework experience. I'm not the best interviewer, but I can usually spot when somebody's bullshitting his way through an interview. So if somebody knows the concepts that are important in D8 (Dependency injection anyone), they should be fine.
I hate when people don't know something and just start hacking instead of educating themselves. I work in an architect function now, so my development skills are waning, and I'm so happy I have a team of devs who have my back and are patient with my questions :)
It's a good thing you kept your cool and I'm glad you got that job. Keep on being patient and educating people, the programming world needs it :)
Good question!
I think in the example you've given, it's worth listing them separately.
To be honest, I would never expect a recruiter to take this page at all seriously, but if you were using it to find Drupal 8 developers, and experience with Drupal 8 is key, then it makes sense for them to be split out.
Thanks for the quick reply!
I think this tool is gonna start living a life of it's own, so I'd anticipate on that by defining some guidelines, if you have the time to do that.
It is mostly cool because now I can just reference a site when recruiters call me with impossible demands :D
What have I done?
That's a really good idea, though, I'll try to carve out some time for it.
Thanks, Dieter!
Except for the job I mentioned there: I had no Drupal 8 experience on my resume.
But I was better at it than anyone they had employed before. Years of experience doesn't necessarily mean anything.
Yes and no. If you'd had to choose between somebody that knew a framework inside/out or somebody with no experience, you'd choose the first person anytime like most recruiters/interviewers probably would. Unless you have similar and relevant experience, like e.g. for Drupal 8, it would be Symfony mostly.