I was "on site" this morning for the installation of the helical piers for my laneway suite (that will be the topic of a separate post). More often than not, I'm in the office. But I like going on site because, well, building things is fun. One of the things that I find interesting about being on site, though, is that my preferred method of communication always seems to change. When I'm in the office, I have a bias toward emails. That is the case for two reasons: 1) I'm usually focusing on something and I find that calls can be disruptive, and 2) emails can be a highly efficient way to communicate. Tell me what you need (in the shortest email possible) and I'll try and respond as succinctly as I can. However, when I'm on site, all of a sudden I don't want to do emails. I would rather talk on the phone. That becomes the most direct way to deal with things. I am mentioning this because communication is paramount. And many of us have different preferences for how we like to do it. Knowing those preferences can be helpful when you're trying to get things done.
What it shows you is the principal routes of the Roman World: the road network, the main navigable rivers, and the hundreds of sea routes that crossed the Mediterranean, the Black Sea, and the coastal Atlantic.
The tool then attaches both time and expense to these routes (which would have been used for the transportation of goods and people, but also for general communication across the Roman Empire).
So if, for example, you are curious about how many days and how many denarii it would have cost you to deliver an important dinner invitation from Roma to Alexandria during the summer months of antiquity, you now have an online tool. It's about 14 days.
"Everything should be made as simple as possible, but not simpler." I'm not exactly sure who this quote is attributed to -- maybe Einstein -- but regardless, I love it. I'm a big fan of simplicity.
I have a cookbook in my kitchen by Jamie Oliver where each recipe contains no more than 5 main ingredients. There's a picture of the 5 ingredients, a picture of the final product, and a short explanation about how to make it. It's my favorite cookbook (and also my only cookbook).
When I go to a restaurant I prefer to see a short menu rather than a long menu. Not only because it's easier to make decisions that way, but because I have little confidence that a restaurant with an interminable menu can make that many terrific dishes all at once.
And in architecture school, I remember being taught that every design project should really only have one principal idea. If you have two ideas, that's probably one too many. Distill it down. Clarify the idea that you're trying to communicate.
Because here's the thing about simplicity: it's usually more work to make things as simple as possible, but not simpler. It takes effort. It takes iterations. Whether that be in cooking, design, or in writing.
But once you've got it, simplicity is a beautiful thing. And it also greatly increases the chance that somebody will actually remember the message that you're trying to get across. Five ingredients. A short menu. And one architectural idea. That's all it might take.
