Ideally, when we say we think something is likely (or unlikely), we should revisit our prediction later once we know the actual outcome… so this year some friends and I will be competing by predicting various 2024 events.
For the last year or so, I’ve been chipping away at a side project: a weightlifting-tracking app. The ostensible purpose is to store the metrics I want and make data entry as convenient as possible, but in practice it’s mainly a way for me to become more familiar with the development of a “large” web application and the challenges that come with it.
Rust reminds me a lot of Go. Both languages eschewed exception-style error handling, a feature present in almost every language that’s popular in industry. However, the idioms they use instead are very different.
Last week, Nvidia’s stock exploded…. The AI arms race has heated up and is even getting the attention of normal people through stock prices (among other news), so I’m sure this won’t be the last time I explain GPUs to someone without a computer science degree. I’m using this post as a chance to organize my Chips 101 talking points.
Let’s cover a few more advanced aspects of the Python exception system. We’ll move a bit faster and talk at a higher level than we did in the last post.
Errors flow differently than regular data; if not “handled”, they rise up through the entire function stack and crash the program…. What exactly needs to be done in that “handling” step typically depends on what went wrong, and so there are many types of errors.
When I first started going to the gym, I was self-conscious every second. Over the years I’d like to think I’ve picked up most of the “rules”. Here’s a list I wish someone had given me when I was starting.