Skip to content
⚠️ This article was written in 2018. Some content may be outdated.

2018 Year-End Summary: Growth and Reflection of a Frontend Engineer

2018 is coming to an end. When I started writing this, I scrolled back through the blog posts from this year and was surprised to find nearly 50 of them. From the Vue features notes in January to the in-depth articles in December, I can genuinely feel myself growing.

Technical Gains This Year

Frameworks:

  • Gained a deep understanding of Vue 2 reactivity internals, VDOM, and SSR
  • Explored the React ecosystem: Fiber architecture, Hooks (still unstable), Suspense
  • Started taking TypeScript seriously — went from "why bother?" to "this is great"

Engineering:

  • Migrated Webpack from 3 to 4; build speed improved noticeably
  • Babel 7 upgrade was messier than expected, but on-demand polyfills are genuinely good
  • Learned to analyze bundles, tree-shake, and split code
  • Encountered micro-frontend concepts and shipped the first production implementation

Fundamentals:

  • JavaScript prototype chain, closures, and event loop — finally got them straight
  • Browser rendering internals: critical rendering path, caching strategies
  • HTTP/2, CORS, and other networking fundamentals

Tools and Process:

  • Git workflow, code review standards
  • Jest unit testing from zero to practice
  • ESLint + Prettier code standard configuration

Growth Beyond Technology

This year I started genuinely caring about software design, not just "knowing how to use frameworks."

Read Clean Code and reflected on a lot of the "make it work" code I'd written before. Started caring about naming, function size, and single responsibility. My code is still far from elegant, but at least I have the awareness now.

Participated in several tech talks — took content from the blog, organized it into slides, and presented to the team. My communication skills have improved noticeably since the start of the year.

2018 Technical Highlights

  • February: Webpack 4 released; build speed improved dramatically
  • August: Babel 7 officially released
  • August: React 16.6 brings lazy/Suspense
  • October: React Conf 2018; Hooks officially unveiled
  • November: Vue 2.6 released; v-slot unifies slot syntax
  • Throughout the year: TypeScript's momentum keeps growing, more projects adopting it

React Hooks was the most exciting thing for me this year. It's not stable yet, but the direction is right — extracting logic from UI, composing with custom Hooks, much more elegant than HOCs and render props.

Plans for 2019

Technical:

  • Wait for stable React Hooks, then fully migrate a company React project
  • Track Vue 3.0 progress seriously; learn Composition API
  • Get the TypeScript advanced types and type gymnastics down
  • Do a systematic Node.js study — not just for writing scripts

Skill Development:

  • Finish reading Refactoring
  • Try contributing to an open-source project
  • Keep writing blog posts; target 30+ posts

Directions to Explore:

  • WebAssembly basics
  • GraphQL — a new approach to API design
  • CSS Houdini — more powerful CSS extension capabilities

A Few Reflections

The deepest insight I took from this year: technology evolves fast, but underlying principles change slowly.

Frameworks change, tools iterate, but JavaScript's runtime mechanics, browser rendering internals, network protocol fundamentals — these things barely change over years. Investing time in solid fundamentals beats chasing every new framework.

That said, you can't completely ignore new technology either. An innovation of Hooks' magnitude — if you wait for it to be fully mainstream before learning it, you'll fall behind significantly. The key is distinguishing the big changes you must track from the details that merely deserve awareness.

2018, that's a wrap. 2019, let's keep going.


Thanks to everyone who read this blog over the past year. Writing is really a process of organizing my own thinking. Feel free to point out anything I got wrong.

Happy New Year!

MIT Licensed