Code Story episode
S6 E11: Why Tech Training Fails Engineers: Building Live Micro-Coaching Engines with Hywel Carver of SkillerWhale
Mar 29, 2022 · Season 6 · Episode 11 · 33 min
Personalized, Developer training - in bite sized chunks
Hywel Carver has been writing code since he was 9 years old. His first language was C, which quite a language to start out in, and his first program was a "Guess the Number" program, using binary search - and of course, with an embedded Easter egg. He is married, with 2 children. Parenting has really pushed him to learn how to focus, and he regularly has to put things down to take care of other responsibilities. One of his biggest hobbies is pub quizzes, which in Britain is a big deal. In fact, he has been on a few quiz shows on TV, including Who Wants to be a Millionaire.
Hywel and his co-founders dreamed about a way to distill down the distinct learning moments for you, leading you to the point of inception for skills and wisdom. Their passion for this topic led them to build a way to develop developers, in an incremental, personalized way.
This is the creation story of Skiller Whale.
Sponsors
ImmediateOrbitPostmarkStytchVerb DataWebapp.ioLinks
Website: https://skillerwhale.com/LinkedIn: https://www.linkedin.com/in/hywelc/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Technical due diligence checklist for startups
A technical due diligence checklist for founders and investors: what reviewers examine across architecture, security, team and process, and how to prepare before a raise.
Fractional CTO vs full-time CTO: which does your startup need?
A practical comparison of a fractional CTO and a full-time CTO: cost, scope, when each makes sense, and the questions to ask before you hire either one.
CTO vs VP of Engineering: how the two roles actually differ
CTO vs VP of Engineering explained: who owns architecture, who owns delivery, when to split the roles, and how to avoid the overlap that breaks engineering teams.