My Never-Ending (Coding) Story

Posted August 13, 2018

Completing my coding program was the preface to my developer journey. Now the real story begins.

I’d barely scanned my KU full-stack program completion certificate and linked to it online before the questions started flooding my brain:

Lying here at 4 am thinking about my current React project, replaying my latest interview in my head, and anticipating my next KCWiT meeting, I can happily answer my introspective questions with a “yes.”

Finding your way without a roadmap

Now that I have a solid development foundation and fundamental understanding of how a full stack functions, I can wander about the cabin freely to pick up new skills or dust off old ones. Instead of one all-encompassing guide to what I should master next, I’m letting demand and interest guide me. For example, since React keeps popping up in job descriptions, I’m working my way through a great tutorial to expand my knowledge.

When I’ve absorbed enough React concepts for the day, I switch gears to expand my UX knowledge. With microcopy growing in importance, I’m convinced my hybrid content writing and development experience could open new development doors in the future.

Preparing for the next — not rehashing the last — interview

My first few developer interviews were more notable for what I didn’t say than what I did. I froze when asked to explain simple functions. I couldn’t remember basic concepts I’d used for months — if not years. In short, interviews induced panicky episodes of imposter syndrome in me.

But now a few months have passed, and it’s easier to keep a cool head and a clearer memory when asked about the technologies I’ve used and strategies for learning new ones. Instead of forgetting JavaScript requires script tags, I wax eloquently about ECMAScript and its value in relation to React. I can even toss in knowledge of Babel’s role in compiling later versions back to vanilla JavaScript for older browsers and explain why developers have to adapt to new technologies without losing sight of older ones.

Embracing the spirit of community quid pro quo

As students we heard a lot about how much easier it is to code these days thanks to open source. Our instructor and TAs encouraged us to connect with the development community; now I see why.

For one thing, it’s affirming to help others just as you’ve been helped because it’s proof you know something. And while I haven’t yet written an NPM package or established a Github Repo for the sole purpose of sharing code, those possibilities don’t seem impossible, either.

Ultimately, being passionate about coding means you’re eager to learn and willing to share knowledge, which helps other developers grow stronger and smarter. After all, you never know when you’ll have to reach out for help. But when you do, it’s comforting to imagine a robust squadron — rather than a Lone Ranger — standing by to lend a hand.

My development story is still in its early chapters. But given the plot line so far, it’s shaping up to be a pretty exciting read.