In June from last year, I sent an email to Cory House, a pretty famous and in-demand developer, so I didn’t really expect a response. I’ve tried in the past to do the same with other notorious developers, who never came back to me (and that’s fine, they must receive hundreds of emails per week from strangers with all kinds of requests).
I’ve had a thought on my mind the previous days that I couldn’t shake off. So I knew I had to write an article about it.
The idea is simple: For most of the external constraints on my studies and career, I chose to see the bright side and make the most of them, to turn them into opportunities. It’s easy to feel stuck and spend our days complaining about our unlucky state. But it’s almost always possible to turn our seemingly sour lemons into tasty lemon cakes.
The best way for me to show you what I mean is to share 4 examples from my life, in chronological order.
Two months ago, I shared some updates on my coding journey. The main news was that I was going to start working remotely and as a freelance for my previous employer. Here are some new updates on how things have been working for me since then.
The quick summary is that I’m very satisfied by my new working conditions. Actually, it’s almost a dream come true. So much so that I’ve decided to put on hold my application for the London-based distributed startup I mentioned in my previous post who wanted me as a long-term employee and not as a freelance.
When I started this blog in December 2016 (almost a year ago), I pledged to write a post weekly. Some followers on Twitter told me that this was bold and that it was hard to be consistent. They were right. I kept my weekly pledge for 6 months, and then baby #3 was born. Life has been a storm since. 6 months later, baby boy’s still not sleeping through the night. And since my wife has finished her maternity leave and has resumed her medical residency, I’m the sole night watch. Do you imagine blogging while not having a single straight night for 6 months?
But I’m not seeking any excuses. Blogging is hard because it never seems a priority when life gets in the way. At the end of the day, regardless of how little I slept or how little margin I had left in my days, I could have found 1h per week had I really tried. So here it is: since my pledge was public, I publicly acknowledge my failure. And I won’t renew it. But I’ll still try to dust off my blog a little and bring it back to life a bit.
The first step will be to bring you up to speed to where I’m at in my software journey. A crazy lot has happened the last few months.
Last week, I continued my Clean Code series by having Emilien Pecoul answer the question: “What is Clean Code for you?”
Today, I have the priviledge of introducing Bill Sourour and his answer to you. I’ve been reading his Dev Mastery newsletter since July 2016, and I’m a better developer for it. If you don’t know about it or haven’t subscribed to it, you can check all his previous posts on his Medium profile. And if you like what you read, you can subscribe here.
The breadth of topics he can address in depth thanks to his more than 20 years experience is impressive to me. Whether you agree with his conclusions or not, you can always find nourishing food for thought.
A few months ago, I started a series on Clean Code. After introducing the series by sharing quotes from leaders in the tech industry, I had the privilege of having two friends of mine working at Mozilla share their answers to the question: “What is Clean Code for you?” Jan‘s and Ben‘s).
One thing I appreciate in this series is how each answer is at the same time unique, yet shares the same fundamental values. Each developer has their own perspective on what makes clean code, yet all essentially agree. It’s like watching the same diamond from various angles.
Today, I have the joy of sharing the answer of someone who has had a great influence on my young software development career: Emilien Pecoul.
In my initial post on December 27th 2016, I pledged to write one post a week. Which is what I did without a single miss until April the 3rd, keeping my promise 15 weeks in a row. But those of you who follow carefully realized that I didn’t post anything since. By the way, I want to thank those of you who called me on this for caring enough to do this.
The reason behind these misses is that my (growing) family is in the process of buying our own home for the first time. And next to a full time job and a busy family life, this project has been taking all my free time since we made an offer that was accepted. We’ll be signing the deal at the end of this week, and now need to find the best deal for our mortgage. Each little win can mean thousands of euros in gain, so I’m working hard on it.
However, my wife rightfully pointed that life will always throw new urgent and important tasks at me. If I start making excuses, it will be much harder for me to keep blogging. So here I am, back to the task.
Now let’s talk about MiXiT
Today, I want to share with you some thoughts on the tech conference MiXiT 2017, which took place in Lyon Thurday and Friday of last week, and was the first tech conference I ever attended.
Last week, I explained what Free Code Camp is in my own words. Today, I’m going to detail my experience going through the very beginning of their front-end course, where the goal is to build some simple static web pages.
Last week, I intended to write the post you’re currently reading. But I realized that I couldn’t explain my experience with Free Code Camp without writing about the remarkable man behind it, Quincy Larson.
So here we go today. No digression allowed. What is Free Code Camp?