... Where Credit Is Due
Posted July 11, 2018
"And I never could have come this far without you
For everything you've done, you know I'm bound
I'm bound to thank you for it." — Natalie Merchant
Starting a journey without a map
When I signed up for KU's full-stack program last fall, I really didn't know what to expect. I completed my second degree several years a go, and although I've consistently earned certificates, attended workshops and taken non-degree seeking classes, I'd never done anything this intense. I was sure I wanted to become a developer, but I prepaid as added incentive to stick with it just in case.
Meet your lifesavers, a.k.a. TAs
Along with our great instructors, Ryan and Ryan, our cohort had two amazing TAs: Byron and Cameron. Whether they were alleviating homework angst, saving us from installation pitfalls, tirelessly debugging bad code or imparting general wisdom (keep it DRY!), these guys were always there for us. I know they sometimes doubted whether we were listening, but I for one will always remember their guidance and patience.
Discovering mentors along the way
KU also provides full-stack students with access to career services and weekly tutoring sessions. On the career side, burgeoning developers can't find a better cheerleader than Amber. She mixes positivity with great tips on networking and job hunting, and even if your code is broken you can't help perking up after an Amber chat. My tutor, Maxwell, provided structured guidance geared toward ensuring I adopted good coding habits from the get-go. I started more than one session with him at Defcon 1, only to be calm, cool and capable of progressing further by the end of the hour. If future employers notice my clean, indented, well-commented code, I'll be sure to give Maxwell credit.
A good portion of learning to code is tracking down your own solutions. I'd be remiss if I didn't thank my mentor Rowan Hamilton for teaching me to Google smarter. I know it sounds odd, but you have to search differently when you seek answers to why two NPM packages have conflicts or hunt for a React-based workaround for your sticky footer issue.
I'm still no pro. But watching Rowan break a bug down to its separate parts then solve them one by one 'til the code worked was like a real-world re-enactment of the mantra Ryan, Byron, Cameron, and Maxwell kept repeating: Tackle one issue at a time. Console log is your friend. Use your DevTools wisely. And one day a true developer you may be.
Exploring the knowledge that lies ahead
I've reached the stage of my coding journey where the rest is up to me. But my mentor is still around (I know where you live, Rowan. And I know what kind of cake you like!), and I've already kicked off a new mentorship through (KCWiT) that I'm excited to undertake. Keeping in touch with fellow students ... attending new workshops and Meetups ... there are plenty of ways to find help navigating the development universe. Maybe someday I'll even be competent enough to return the favor to another new developer starting down this amazing road.