It dawned on me during breakfast. Coaster sets come in various containers and as I stared at this particular empty holder, I realized it could be used to hold my iPhone. It props your phone up a bit, and there's a convenient opening to channel your recharging cable.
And what of the coasters it once held? Without a home, they are coasting around the dining table.
I first shared my enthusiasm for dark mode in the post Automate Dark Mode in Apple OS Mojave . Not everyone likes dark mode though, and Victoria Song of Gizmodo recently wrote a light hearted essay to Stop Using Dark Mode . She made some fair points. Color themes for light mode have been around longer and their designs have had more time to evolve; the result is superior contrast and better readability than their dark mode counterparts. I've also found dark mode limitations in Apple's Mail App. While Mail is dark mode capable, html email is rendered in light mode and the harsh contrast is painful to the eyes. Where dark mode shines is when I'm using one application exclusively such as Xcode or Android Studio. The colors are consistent, and free of competing themes, the experience is immersive and harmonious. Discussions of inefficiency continue to trend. I contributed with the post The Hidden Cost Of Efficiency , where resiliency is inversely proportional to eff
My first job had me programming in Microsoft BASIC for the IBM PC (DOS). BASIC worked well enough, but its limitations were clear. The language was interpreted and therefore slow. More importantly, it wasn't a modern structured language, and instead, relied on line numbers and the GOTO statement. Anyone who has read Dijkstra knew GOTO was a bad thing . Having learned a structured language in college ( PL/I ), using BASIC felt unnatural. When a C compiler became available for the PC, I saw a chance to improve and modernize our software. The problem was selling the idea -- a problem made harder because I wasn't fluent in C. "It would be a staffing problem. Not many people know C, but we can find a lot of programmers who know BASIC," noted one manager. The argument was strong as my knowledge of C was weak. But I knew that C, by design, was a small language and thus easy to learn. "It has about 30 keywords," I proffered to another manager. U
In the book Beautiful Code, Jon Bentley describes beautiful code in a Zen-like way , where the most beautiful programs are sometimes, not there at all . In a YouTube interview with Lex Fridman -- Bjarne Stroustrup: Recognizing Beautiful Code -- Stroustrup is less paradoxical, but equally thoughtful: It's easier to recognize ugly than to recognize beauty in code. . . sometimes beauty comes from something that is innovative and unusual, and you have to sometimes think reasonably hard to appreciate that. On the other hand, the messes have things in common. I've always endeavored to write neatly indented, correct code with intelligent defaults and consistent return values, but in terms of beauty, that is a low bar. Code that runs wickedly fast can be beautiful, but perhaps that is more of a measure of cleverness. A better indicator of beauty, however, might be how well the code stands up to time. Requirements change, database fields are added, code is refactored by multiple author