This week was pretty uneventful, and yet I didn’t manage to do much work.
The idea with spreading stuff across the week was a good one: I feel it lets me work better at my main job and on these things too. In a way, it allows me to ensure that more “versions” of myself tackle a given problem. To be more specific, if I work on something for 2 days, 4 hours at a time, I am more likely to have two different perspectives on some problem, which is certainly better than just the perspective I can get on one 8 hour day.
Still reading a couple of pages just once a week. Just reading is simple enough, I’m trying to “parse” the sentences, i.e. perform some semantic analysis to make sure I understand what’s going on from the language’s perspective.
Took a bit of an L with guilt this week. I had implemented patch tagging some time ago, but this week I found out guilt already has this feature, it just calls it “guards”. Its approach certainly can still be improved, but I like how it deals with storing the patches’ tags. I’ve removed my patch from the repository for now, I might add it as a separate tag or branch later.
So yeah, if there’s anything to learn from this situation, it’s this: always read the documentation. I had actually read it, but didn’t read about “guards” and just assumed it was something about locking. I guess in my case, the lesson is: stop making assumptions. It’s weird, but whenever I assume something, I turn out to be wrong pretty often. But when I assume something and try to ignore that, I end up asking dumb questions and learn that my original assumption was correct after all. No idea why this is the case, but it feels like most of the time this is due to my general lack of attention to detail. Perhaps I should do something about that, but what?
Dismal
I didn’t make much progress, but it feels like I still advanced somewhat.