Looking back at 2017

I’m late, I know.

Let’s take a look at what I accomplished this past year:

Now let’s talk about the other side of things:

Looking further back

Since this is my first time writing a “year in review”, let’s look further back a bit:

I submitted my first pull request to open source a year and a half ago. If it wasn’t for the amazing welcoming attitude of those reviewers (thanks Kent :)), I probably wouldn’t be nearly as excited to contribute to open source as much as I am now.

Goals for 2018

2017 to 2018

New Years resolutions never made sense to me. Why not just begin something in December if it’s weighing on your mind? Why wait for the new year?

With that being said, I think we all have things we want to improve on. If somebody likes to plan goals on a yearly basis, who am I to say that’s not the right of way of doing things. There really isn’t a “correct” way to have goals.

So what about myself? Sure, I can say I want to work on more open source projects, give more talks, write more technical content and so on. Will I get disappointed if I don’t do anymore of these in 2018? Maybe. But there’s more important things to think about.

One thing I regret about spending quite a bit of time on stuff like this outside of my full-time job is that I’ve not nearly helped as many people get into web development that I would have liked to. Every week, I meet individuals who were pretty much in the exact same shoes I was two years ago - unsure about what web/mobile development really is but curious enough to start trying to get involved. And I’m not talking about JavaScript enthusiasts in particular, this includes folks interested in design, DevOps, user experience, marketing and so on.

So for 2018, if I focus too much on myself and not help as many newcomers that I can get into the intimidating world of web development — hold me accountable.

If you have any questions or suggestions, feel free to open an issue!

Houssein Djirdeh