I’d be driving HTTPS adoption across the web and working with big sites to unblock their migrations in any way I could. When I first started talking to the Chrome Security team about coming aboard, it was for a role on the Developer Advocacy team.
Chroma slasher code#
If all else failed, I’d just avoid working on any especially gnarly code and spend the day handling support requests, updating graphics, or doing other simple and straightforward grunt work from my backlog. Even if I didn’t get enough sleep, it wouldn’t really matter-I’d been coding in C# on Fiddler for a decade, and deadlines were few and far between. When Noah was a baby, I could simply sleep in after a long night. Learning new things when you don’t remember them the next day is a brutal, frustrating process. And that’s been extremely challenging… because I can’t remember much else either. I can’t remember the last time I had eight hours of sleep in a row. Fortunately, Nate has been a pretty good sleeper, but even now, at just over a year old, he usually still wakes up and requires attention twice a night or so. Big brother Noah is at an age where he usually sleeps through the night, but he’s sure to wake me up every morning at 6:30am sharp. The nights, however, have been unexpectedly difficult. Thanks to my wife’s heroic efforts, we found a workable daytime routine.
Instead, it varies between 80% (when the kids happily play together) to 400% (when they’re colliding like atoms in a runaway nuclear reactor). Mathematically, you might expect two kids to be twice as much work as one, but in our experience, it hasn’t worked out that way. But for the most part, my illnesses were minor-enough to keep me awake at night and coughing all day, but otherwise able to work. As I coughed my brains out on the sofa at home, I derived some consolation in thinking about Google’s generous life insurance package. That ended with a bout of pneumonia that concluded with a doctor-mandated seven days away from the office. (Our theory is that Noah was bringing home germs from pre-school he got sick a bunch too, but recovered quickly each time.) I was sick more days in 2016 than I was in the prior decade, including a month-long illness in the spring. Perhaps sensing that my life had become too easy, fate decided that 2016 was the year I’d get sick. I took a short paternity leave, and my coding hours shifted somewhat (I started writing code late at night between bottle feeds), but otherwise my work wasn’t significantly impacted.Īs I pondered joining Google Chrome’s security team, I expected pretty much the same-a bit less sleep, a bit of scheduling awkwardness, but I figured things would fall into a good routine in a few months. When Noah was born, I’d been at Telerik for almost a year, and I’d been hacking on Fiddler alone for nearly a decade. I mention this because it’s had a huge impact on my work over the last year- much more than I’d naively expected. In a year, we went from having an enormous infant to an enormous toddler who’s taking his first steps and trying to emulate everything his 3 year-old brother (Noah) does.
Chroma slasher full#
I took full advantage of Google’s very generous twelve weeks of paternity leave, taking a few weeks after we brought Nate home, and the balance as spring turned to summer. My second son (Nate) was born a few weeks early, arriving ten workdays after my first day of work. While I started at Google just over a year ago, I haven’t actually worked there for a full year yet.
This rambling post is an attempt to answer that question.
When I mentioned my anniversary, friends and colleagues from other companies asked what I’ve learned while working on Chrome over the last year. Time flies when you’re drinking from a firehose.
Chroma slasher free#
Four weeks ago, emailed notice of a free massage credit revealed that I’ve been at Google for a year.
0 kommentar(er)
