I often think my way is the best because it is the most obvious (to me). When I review someone else’s code, I forget that the way it is implemented is the most obvious way to the developer. We can talk about why it is different from what is obvious to me, but I should expect to often be wrong because the programmer has put more thought and effort into solving the problems. My feedback should reflect that I may be wrong because my perspective is different. Put this way, it is much easier for me to be less blunt, less definitive in my correctness.Read More
Computer vision and is neat but I like being able to explain what I’m doing. I like knowing something all the way down to first principles. I like how the depth can inform the explanation. I also like getting things done. Sometimes, you can't get everything you want. But if you try sometimes...Read More
So what’s up with my typing robot? Has it fallen by the wayside like too many of my projects?
In a word: no. Ty has led me on a merry chase across different worlds. I’m still trying to catch up.Read More
I don’t do pair programming. Even when I worked for large and small companies, I worked mainly by myself. My notebook is my companion in design and implementation. While it lacks programming skills, it is a remarkably good listener.Read More
In a previous post, Andrei discussed the switch statement. In this post, he gives a more indepth review of switch and then deeply dives into the default case.
Rather than just leaving it out, default can be used to detect the impossible. Read on to handle whoopses, neutrino hits, and beer. And remember, be assertive, but be kind to your future self.Read More