Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Radu Camerzan - Teaching Drupal - the road to mid-level.

43 views

Published on

Teaching Drupal - the road to mid-level.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Radu Camerzan - Teaching Drupal - the road to mid-level.

  1. 1. Teaching Drupal: The road to mid level By Radu Camerzan A Drupal Developer From Adyax On 23 June 2018
  2. 2. Programmers are self-taught, why teach them? • We’re speaking about junior programmers here. Mid ones should already be able to learn/specialize on their own. • It’s faster and you get to pick the direction. This way your team will be able to cover “more Drupal” • Mentoring is a form of teamwork. You will be able to see if the person is a culture fit or where it may be a good one.
  3. 3. Define what we want to achieve Junior • Knows HTML + CSS + PHP (basic) • Knows how internet works • Can create a branch in git • Can install contrib modules • Can use Google to find documentation Middle • Knows the Drupal way • Can identify bottlenecks • Can resolve a merge conflict • Is ok with patching a contrib module • Uses Google to find solutions
  4. 4. If they know PHP, why teach them Drupal? • Drupal is the car you’re driving. PHP is the engine + wheels + other stuff inside it. Good Driver != Good Engineer. • The “Drupal Way” of doing things. The community has grown up with modules, coding standards, APIs that you can leverage. • Learn another way to do stuff. If they have prior experience – they might improve Drupal or find things they like in Drupal.
  5. 5. Mind the path
  6. 6. Prepare for the journey ahead of you (mentor + student) • Make time for support – you still have your main job to do • Establish rules – interruption is bad for the flow, plan for it • Set up the environment – a good editor must auto-enforce formatting • Give feedback – good and bad one, they’re both needed for learning
  7. 7. Things I teach It’s OKto: • Not know how to do something • Not hit your estimates • Seek help • Copy/paste a solution • Write smart solutions • Write custom modules It’s NOT OKto: • Fail to deliver because of it • Refuse to give one • Try to solve it by yourself first • Not read it and understand it • Refuse to adhere to standards • Not do your contrib research
  8. 8. What if they’re actually smarter than you? • Double check this. You can try changing mentors, up the game, give more serious goals. • Congratulations, you hit the jackpot! No really, as a teacher you hit it – you just got your student to surpass you. Time to let go.
  9. 9. What do you get as a teacher from it? • Teaching someone means improving yourself. It’s just another way to do it – and it touches more skills than simple coding: communicating, planning, controlling. You’re gonna need those as a Team Lead ;) • Networking. Yes, you get people that are “below your level” – but only at first. You never know when the wheel turns around. • Growing your personal brand – people usually remember good teachers (or awful ones). Try to hit the first category.
  10. 10. Drupal needs you! …but in case you need me, here I am: • Email: raduttzu@gmail.com / rcamerzan@adyax.com • Facebook: https://www.facebook.com/radu.camerzan • Linkedin: https://www.linkedin.com/in/rcamerzan/ Disclaimer: it may take a while for me to come back. Be patient and I’ll be there for you!

×