While I’m riffing off of Dan Luu’s post about not being afraid to look stupid, I want to think about asking Stupid Questions. In this post I want to explore: What is a stupid question? What are some examples? Why would I want to ask them? Why don’t I ask them? What is a stupid question? I’m thinking of a specific type of Stupid Question.
The last time I wrote a regular blog post was about one year ago. Now, as we all know, a few things have happened in the world since then. So, it could be understandable if I didn’t post anything. But, if I’m honest, the reasons I stopped posting related more to my feelings and less to the state of the world around me. I’m thinking about this because I just finished reading this excellent post by Dan Luu about his willingness to look stupid.
Nothing wasn't quite what I expected it to be. I think I expected emptiness; nothing is a little different that empty. In order for there to be nothing there can't even be me. When I thought about emptiness I was really thinking of emptiness except for me. All that nothing — or is it, none of that nothing? — I expected a vast darkness, like I was floating around in space. Instead, I was alive one moment, then nothing.
One of my favorite reads is Joel Spolsky's Things You Should Never Do. He wrote this post almost twenty years ago, outlining the downfall of Netscape and others because they spent years rewriting working code. His solution is, unsurprisingly, to refactor. About a year before Joel wrote Things You Should Never Do, Martin Fowler published his popular book, Refactoring: Improving the Design of Existing Code. So, my question is, if we as a community figured out — twenty years ago — that we should stop rewriting programs, why is it still commonly done today?
This series, Go Things I Love, is my attempt to show the parts of Go that I like the best, as well as why I love working with it at The New York Times. In my last post Go Things I Love: Methods On Any Type, I demonstrated a feature of Go that makes it easy to build Object-Oriented software. This post, Channels and Goroutines, will demonstrate a few neat concurrency patterns in Go.
Water is still pouring out. Maybe not quite as much as before, I can't remember. Even so, it doesn't look like it's going to be a problem. The river is hundreds of feet below. Still, I remember this whole region is a flood zone if the dam breaks. People used to talk about how everything would break down once people were gone. There was a book about it. The subways of New York would flood, homes would be overtaken by nature, bridges would fall, and dams would collapse.