KDC Menu

Sunday, August 20, 2017

Career Tweaks

From time to time we need to make little tweaks to our career paths. Although learning React Native was next on my path, I've decided that learning another framework, even though it’s close to React, would continue taking me laterally; whereas at this point, I now need a much stronger foundation for my current skill-sets.

My goal for 2017 has been to gain exposure to the various front-end technologies that have become prevalent over the last five years or so: To upgrade my skills with tools I'd need to be a more productive asset in the current job market (read: so I can find a job and be good at what I do).

Having been productive this year with three different present-day frameworks (React, Vue, and Laravel), I believe it's time I now turn my focus to strengthening and expanding my knowledge of core JavaScript fundamentals.

Reasoning: Learning React Native won’t help me in passing advanced JavaScript tests, but doing a `.reduce()` a day might.

Instead, because 'dailies' and coding challenges force you to think more proactively (as opposed to being in constant 'troubleshooting' mode), my new strategy is to stick with React and Vue, and get to know JavaScript better! (...and HTML and CSS.)

Keith D Commiskey

Wednesday, August 16, 2017

My Experience with TypeScript + React

TypeScript: "A strict syntactical superset of JavaScript that adds optional static typing" (paraphrased from: https://en.wikipedia.org/wiki/TypeScript).

I just finished injecting TypeScript into my last React web app (Done (for now)), and can say that I've enjoyed learning how TypeScript works: In particular its insightful nuances with React.

Why TypeScript? ...One might ask... I’ll let their intro video tell the full story (link provided below), but for me, it is for proper code insights (IntelliSense) and `type` support that I feel helps me to become a stronger programmer.

How so? TypeScript will continue to help me focus more on a data-first design approach, as I tend to just start "creating", and find myself designing (UI and data structure) along the way. Although arguably instinctive, this is SO not a good approach!

In addition, when you’ve gone through as much foreign (read, spaghetti) code as I have, being able to see an enforced data structure skeleton would have been welcome many a time.

How does it compare with Flow? There are quite a few articles on the subject, so I'll defer to one of those.


TypeScript Intro Video:

At the time I watched it, the video could be found at the following location:

Tip! The reason I mentioned the video's actual location is, I discovered if you remove "_high" from that URL, you can get a smaller version of the video, which in my case, was ideal for downloading and watching offline (I tend to rewind and pause a LOT).