Okay, this Austin Graff character really has me going on Washington DC now. I’ve always had the National Building Museum in the back of my mind when visiting DC, but now I have to go see it.
The thing is, I always had a slight cognitive dissonance about this museum. Is it a museum about buildings? Or a museum about building things? Or just a museum in a building? Whatever the case, I’m there!
This looks like a great place to visit for some quiet time and to soak tip some pre-industrial America while in DC. Or maybe enjoy some genealogical and historical manuscripts, if that’s your thang. Or just looked around with mouth wide open. 😲🤩
(DAR = Daughters of the American Revolution)
This place hits two of my personal sweet spots: swimming and amazing architecture. 🤩
👉 Victoria Baths: Manchester’s Water Palace
If I ever get to Manchester, and this place is actually open, I know where I’m going to get my exercise. In fact, I’d love to do a swimming pool / lido / bath / spa tour of the UK. Who’s down?
On my Austin to-do list, this “monumental work, a 2,715-square-foot stone building with luminous colored glass windows, a totemic wood sculpture, and fourteen black and white marble panels” looks amazing!
Related NY Times articles…
This is Lyft’s approach for adding a major new feature to their app. -> eng.lyft.com/from-four-wheels-to-two-403bcf1cbf59
I heard about this on the iOS Dev Discussions podcast.
Feature flags, feature modules, launching early and iterating small, facing questions they didn’t have answers to until they did some real world experimenting and iterating.
Love this…
Every new feature is a chance to start with a clean slate, and it’s often tempting to immediately build for scale. We all want our products to launch to massive fanfare and usage, but more often than not, the path to success for new features is slow and steady. With steady growth in mind, we designed our first architecture to support exactly what’s needed for our first product iteration, and nothing more
Also…
The computer scientist in me was angry, but when the datasets are small enough, reasonable tradeoffs can be made in the short term without sacrificing the user experience. When choosing the “rewrite” approach, it’s important to be confident that the code will stay simple and easily explainable. In this case, the algorithm wasn’t perfect, but it worked reliably and quickly.
patmcg.com 