CTO Think

{{ show.title }}Trailer Bonus Episode {{ selectedEpisode.number }}
{{ selectedEpisode.title }}
{{ displaySpeed }}x
{{ selectedEpisode.title }}
By {{ selectedEpisode.author }}
Broadcast by


We speak with our first guest, Mark Thompson of Trilogy Education, about his approach to creating a productive learning environment both on the job and in a classroom setting. Mark is also working on a side project named Totally Strong, which is pushing his own limits about learning to code while building an MVP (and raising a newborn!).

Show Notes

  • Mark Thompson is both a developer of apps and teacher of coding bootcamps, and now he's working for Trilogy Education as Director of Academic Excellence working on developing new training programs for Trilogy instructors
  • Mark is also working on a side project (with a new baby at home) called Totally Strong, Inc, which allows people to coordinate and plan workouts for free
  • Totally Strong is being built with a new framework called Flutter, which is still in beta
  • Junior developers need a culture where questions and answers are a key part of the workflow
  • Create a culture where senior members of the team are open to being interrupted and asked questions constantly
  • Mark is quick to highlight when someone asks a question that they are probably not the only person with the issue
  • Mark also compliments a person for taking the initiative to ask a question in the first place
  • Have students/juniors explain back what is going on with the code, which will likely force them to ask questions
  • Let people see that the teacher may need to re-explain things because the first delivery is not clear
  • Allow senior team members to also ask questions on behalf of the juniors
  • A great set of resources is also important (asynchronous learning) with documentation
  • Managers need to consider how much time they are allowing juniors to spend with the learning tools
  • Pair programming is a good way to strike a balance between work getting done and teaching at the same time
  • Give assignments in the early days that force juniors to learn (without throwing people into the fire)
  • Go through your issue cue and mark issues as "newcomer friendly" so you have some assignments ready for onboarding
  • Explaining pairing to a non-technical manager can be a challenge; one approach is to explain it more like a guiding process or apprenticeship (how other industries handle it)
  • Pairing does allow for teaching while something is getting done
  • Pushing all learning to the off-hours and weekends is courting burnout, which is dangerous to the most vulnerable people on your team (newcomers)
  • We are in a different workforce, where some ideas tell you that developers shouldn't even have side projects
  • Pairing does help mitigate the "hit by a bus" risk factor that a team has among senior devs
  • How do you keep energy high in an office environment, like a Mark Thompson classroom setting?
  • One of the Mark Thompson hallmarks is the "power clap" and "the dab" for praise, attention, and a little bit of fun.
  • How do you reach and pull energy out of the introverts when they are not engaging with the office or classroom?
  • Make sure your students or junior devs feel safe in the classroom. Have one-on-one conversations to build a rapport and reach out to them in a way that makes them comfortable.
  • Don't treat everyone the same. It's not just extroverts and introverts, but how people with different backgrounds interact with the world at large.
  • How does each individual person handle a learning environment? There's no silver bullet for handling the need for individual focus by managers.
  • Using empathy: how to respond to people in a more thoughtful manner? Put yourself in other people's shoes so that your response to questions and feedback or criticism is kind
  • Kindness invokes a higher level of care for those people around you
  • As a leader, it is on you to have more empathy: seek to understand before being understood
  • If you take over a new office, you need to give yourself time to learn about each person before trying to teach everyone
  • Be patient with yourself because teaching other people will not be easy for you
  • You need to learn more about the person, the student, in order for them to learn best
  • Patience in the workplace is vital if you want to create a learning environment
  • Be direct about deadlines and the needs of a project, but provide folks with the outlet to get help where needed
  • Also let the junior know that there are boundaries about when communication is needed
  • It's up to the learning developer to take the responsibility to ask for help or when they feel overwhelmed
  • Instruct learners to advocate for themselves and to not suffer in silence, take the initiative to reach out for help
  • People will not isolate themselves as much when they have a network to reach out to or vent
  • Being a teacher allows a budding manager to be a bit more fearless, how to communicate the need for a task and allow them to succeed at it
  • Going into a new career, don't compare yourself to everyone that is already experienced in the field. Think about how you learned things before, how high school seemed harder than middle school, and college harder than classes before.

Thanks for listening to the CTO Think Podcast.

Shownotes and previous episodes can be found on our website at www.ctothink.com

Reviews on Apple iTunes are always appreciated and help promote the show.

Patreon contributions help us to produce transcripts, which allow people that are deaf or hard-of-hearing to access the show.

For questions, comments, or things you'd like to hear on future shows, please email us at hello@ctothink.com

Show music is Dumpster Dive by Marc Walloch, licensed by PremiumBeat.com

Voiceover work by MeganVoices.com

You'll hear from us next week!

What is CTO Think?

A pragmatic podcast about leadership, product dev, and tech decisions between two recovering Chief Technology Officers.