Goals for 2019

By  on  

Every turn of the year is a new opportunity to start over, set goals, and renew optimism that time can heal wounds and drive us to change and achieve. I did really well with my 2018 goals:

  • I started a fun podcast with TrackJS' Todd Gardener
  • I found my passion again by joining Mozilla's DevTools team and improving the Debugger, as well as pitching in on other DevTools projects. I also removed the old debugger, which was a testament to how amazing the new debugger is
  • Not the mark I thought I would make but I realized the huge value of the work I did to customize the Phabricator instance which will soon be used by all Firefox developers and contributors. It didn't feel like much at the time but the impact I had was massive and I'm quite proud of that. I'm also proud of the work I did on the Debugger to improve its design, features, and stability.
  • I didn't redesign but I do have a new logo coming soon so I'm happy about that.

All in all it was a really awesome year for DWB and my career at Mozilla. With 2018 behind me it's time to try to duplicate an amazing year in 2019. The following are my goals for this coming year!

Become a Better DevTooler

While I'm on the DevTools team at Mozilla, I've been mostly isolated to the DevTools Debugger; not that that's a bad thing. In 2019 I'm hoping to become a more well-rounded DevTooler, having the ability to jump from panel to panel with more fluidity and more knowledge. In doing so, I think I'll also learn more about Firefox, the C++ engineers, and browser architecture.

Achieve "Staff Developer" Status

This new year will be my seventh year at Mozilla and I'm almost humiliated to admit I'm still "Senior" Engineer/Web Developer. In fairness to myself it's not for lack of trying; the truth is that due to Mozilla's shifting priorities I got moved around a lot, and when that happens, you get new managers who can't necessarily judge whether you're up to that level; it's almost like I started over a half dozen times. I think it says something that I succeeded on every time I was on, but that's neither here nor there. In 2019 I want to cement myself as a Staff Developer at Mozilla; someone who can think big and execute bigger.

Improve the Script & Style Show

I'm proud to have gotten over my insecurities to co-host the Script & Style show -- it took quite a it of fortitude and encouragement to do it, but it's paid back big time. We've had amazing guests, fun conversations, and loads of laugh along the way. In 2019 I'd like to get us up on iTunes, do a proper show intro/outro, and mix up formats.

Redesign and Rebrand

My current blog theme has served me very well over the past five years but I'd really like to spruce things up. As you an imagine, maintenance after five years has become difficult and I'd like create a framework-less site, now that ES6 and the JavaScript language have everything I've been shimming with MooTools. I also have a top secret new logo I hope to debut soon.

All The Small Things

A few bits and bobs to attack on the side this year:

  • I want to get a better understanding of Webpack and Babel this year. I've skated under the radar on these because they're usually already setup in projects I work on.
  • I'd like to become better organized in what my daily tasks will be, especially transitioning from the end of one day to the beginning of another. Too often I can get sidetracked by a brand new task while neglecting an old one.
  • I need to become a performance expert: identifying performance problems using profiling, pinpointing the exact code causing the problem, and then fixing or making recommendations. Coding something just to work isn't good enough anymore.
  • I want to continue to improve my work-life balance. I'm doing well these days but I can always do better!

Whew, it's looking to be another ambitious year for me. What are your goals for 2019?

Recent Features

  • By
    5 Awesome New Mozilla Technologies You’ve Never Heard Of

    My trip to Mozilla Summit 2013 was incredible.  I've spent so much time focusing on my project that I had lost sight of all of the great work Mozillians were putting out.  MozSummit provided the perfect reminder of how brilliant my colleagues are and how much...

  • By
    Regular Expressions for the Rest of Us

    Sooner or later you'll run across a regular expression. With their cryptic syntax, confusing documentation and massive learning curve, most developers settle for copying and pasting them from StackOverflow and hoping they work. But what if you could decode regular expressions and harness their power? In...

Incredible Demos

  • By
    Implement jQuery’s hover() Method in MooTools

    jQuery offers a quick event shortcut method called hover that accepts two functions that represent mouseover and mouseout actions. Here's how to implement that for MooTools Elements. The MooTools JavaScript We implement hover() which accepts to functions; one will be called on mouseenter and the other...

  • By
    Select Dropdowns, MooTools, and CSS Print

    I know I've harped on this over and over again but it's important to enhance pages for print. You can do some things using simple CSS but today's post features MooTools and jQuery. We'll be taking the options of a SELECT element and generating...


  1. Awesome read! I feel like this is a lot of achievement.
    Personally in 2019 I’ll love to contribute more to open source projects I’m passionate about.
    – Improve my blogging skills
    – Become a better version of myself

  2. Looks like a lot of your 2018 spend behind the scenes but you have much planned for 2019.

    I am looking forward how you improve the work needed to be carried on the next rather that sidetracking.

    Secondly I really want you to be Devtoller and improve Firefox. Recently I switched to Firefox from chrome and one thing you would miss is chrome’s devtools. It was really hard to find feature that were hidden in Firefox inspector settings. Something like command palette would have helped me. It really mises things like resource blocking, code usage and more.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!