Lots of insights here I agree with The gaps in our understanding of how the system works contributes to incidents. Because we don’t have a full understanding of how the system works, we can’t ever fully reason about the impact of every single change that we make. I’d go so far as to say that, [ ]
If I had to pick one trait, it would be the ability to be comfortable with “the struggle”. That part of the day/hour/minute where the code isn’t doing what you expected, things aren’t looking like they should, or where things are going wrong and you don’t know why. If you can be comfortable with the [ ]
I wanted to make some changes to the excellent Autonomie theme, but because I'm yet a Wordpress development tyro I wanted an environment that I could break. At the same time I didn't want to manually copy changes from local to the real remote env if those changes did turn out to work. There's probably a better way of doing all this, but here's what worked for me.
Moving back to Toronto in September. Barrie is just too weird with its clear IPAs and front lawn inspectors (yes, that's you, Kevin). Also, figuring out how to run in the summer without dying.
The weather is unpredictable this time of year. Last Saturday, however, it was quite certain: rain all day. So, naturally, I went for a long gravel bike ride. I ve never been this soaked and dirty for this long. Here s what my (black) shoes looked like: I thought I learned my lesson, but then on Monday [ ]
at the end of your working day, shut down every app on your machine.[ ]Then, spend ten or perhaps fifteen minutes reflecting on your day.[ ]Then, in the morning, when you open up your machine, there should be nothing yelling at you—no unread badges, no cluster of notifications calling for your attention. At that point, you can [ ]