Missing Days 15–17 of #100DaysOfCode
Well damn it all… I need to talk about relationships for a second. Scroll past the dots if you aren’t feeling it.
I’m really bad at breaking up with people. Somewhere along the road of my life, I picked up this strange need to sacrifice. Excessively.
Sacrifice my happiness. Sacrifice people. Sacrifice resources.
Occasionally, these actions are necessary to put in motion that which pays off. But all too often, my actions are for naught.
Over the past month and a half, I’ve had a significant other that I shouldn’t have. We’ve been bad for each other much longer than that, but there is a love that is resilient and just won’t die.
For too many reasons — logical, emotional, and spiritual — we should not be together. Still, we persist. I’ve long past the point where I’m angry at my giving (and her eager acceptance) of my time; my discontent has been saturated to the point of bursting.
Yes, there are good times. Yes, there are awful times. Yes, I still love her. And because of that, I’m allowing us to separate. A quarter of a year in-and-out of suck, constantly saying “it will get better if we just”. The threshold has been passed and I’m tired.
Thoughts on Progress
Today I read two things that got me insanely excited for everything that is Software Development:
- Google has a free book about how they do site reliability: a form of work they practically invented (along with Facebook) because of their scale
- P1xt’s Computer Science centric Web Development Guide
Members of the SRE team explain how their engagement with the entire software lifecycle has enabled Google to build…landing.google.com
Note: @kevcomedia has ported the entire list into a Trello board you can clone to keep track of your progress you can…forum.freecodecamp.com
Once again, I’m pumped like no one’s business. I guess this goes to show that, right now, I’m one who needs a catalyst. While I “self start in many things”, I can use (and profit from) a push. Let me tell you why.
First, I did a deep reading of P1xt’s guide.
The last time I saw them, I glanced over the three of them I only thought, “wow. Good content. I’ve got through that… Studied this… And that. And that. I’ll check these out later”. Oh man was I mistaken to not think twice about these bad boys.
He encourages everyone to build Facebook. Admittedly, he was inspired by other project lists, but at that point in progressing through the guide you have the skills to make one.
Second, the Site Reliability book is brilliant. It’s something like an amalgam of essays from experts in the field that have done this strange thing: SRE.
They talk about how they built Google, the way they built, and why they did it that way. As someone who would still like to work there someday (sooner rather than later) this is fascinating.
As someone who appreciates quality infrastructure over hack jobs, this excites me. It gives me hope for the next meeting to have other sources than the articles (that I don’t have on hand):
“Why would we do it this way?”
“Because engineers get busy, and we don’t refactor our infrastructure. We don’t make room in this process for better process. We haven’t adjusted for onboarding. Our team isn’t Google-scale yet, but we can be more nimble — more agile — by employing something like this…”
Process approached with computer science principles is something I’ve dreamed about. And that’s what Google’s SRE team does.
I want to do the following:
- Practice algorithms, in Dart, with CodinGame (see P1xt’s guide)
- Read the start of the SRE book
- Read more of Deep Work (you thought I forgot, didn’t you?)
- Have fun doing it all
It’s been one heck of a ride. Let’s see where we get.