The Flipping Table(s)

This is a story about a tiny toy table. Well, a couple of them.

Courtney and I play pub quiz, a lot. We play with a regular group of people at a couple of venues across town. We aim to take a “podium place” home. We come up with a fresh, topical team name every week. We are a bit competitive. It’s a thing.

One of our team rules is: avoid second-guessing ourselves1. The first reasonably confident person to provide the answer to our “quiz scribe” holds sway. Typically, they’re right or confident enough that no further discussion is needed and the answer is scribed to the answer sheet. A terrible way to run a company or government, but an okay way to run a quiz team.

Occasionally, it happens, during a quiz, that two folks will feel that the answer to a question must or must not be something. For instance, there are very frequently questions on the numerically outstanding planets in our solar system. It’s almost always Jupiter or Saturn, but it’s hard to say which. “It’s Jupiter because it has a ton of moons” or “it can’t be Jupiter because Saturn has even more moons”! Well, given the no-second-guessing rule, now we have a pickle. Two conflicting answers, or a non-answer, and what to do about it?

Regardless of how we arrive at it, we can only write one answer. This leaves the door open for us to have the right answer, but write down the wrong answer. Little indignations in jest. We are a bit competitive.

Enter the flipping table

Possibly, you’ve seen the table-flip “emoji”: (┛◉Д◉)┛彡┻━┻. It’s a shorthand for “this makes me have a big, not-good feeling” in online conversation. If not, here’s the late, great Alan Rickman “performing it”:

Alan Rickman turning a table over

That’s how it feels when you suggested the right answer and your quiz team went with the wrong answer anyway. Actually flipping tables would get us kicked out and banned from the venues we frequent, so that’s not an option. However, it happens, tables come in all sizes. Including, very tiny simulacrum of tables.

This is a toy, not an actual dining set

So one night after quiz, I scoured the internet for tiny tables that we could flip. Once I dialed in the search (there are many ways to search for “toy table” on Amazon that will not yield tables that are toys or tables that are flippable amongst polite company), a table was ordered. A few days later, thanks to the magic of just-in-time supply chain logistics2, we had a toy table. So it came that every night, as we were preparing for the quiz, we set out our little (toy) table on top of the (actual) table in case there was a moment of indignation.

Our reputation precedes us

Turns out, flipping a tiny table with your finger is pretty cathartic. The tiny table got a lot of use. We really liked our tiny table.

Even better, a table of adults with a tiny toy table in the center of them is a curious thing. Other teams and quiz hosts inquired about our table. We explained it, let them flip the table. People liked it.

Word of our flipping table spread amongst the Austin pub-quiz community. When new hosts would fill in for our normal quiz host, they would introduce themselves and ask to see our flipping table.

Our reputation for flipping tables preceded us. One could have a worse reputation!

Epilogue for a tiny toy table

As is common of tiny toys delivered by a logistics machine optimized for low cost, the flipping table was not particularly strong. Eventually, we lost or broke it, I don’t remember which.

In any case, a second, slightly larger and fancier flipping table was provisioned. This one even had place settings. Fast-forward a few months, it too broke. One of our quiz teammates took it upon themselves to repair said table. At this point, we had a very robust flipping table, and some of its place settings remaining.

Sadly, our regular quizzing was curtailed by the pandemic, shutting down basically all bars wherein one would play pub quiz. I’m not sure where the flipping table ended up; we haven’t used it in the year since we started quizzing again.

But those months we had a flipping table; glory days!


  1. Other rules:

    • rounds with two options for answers should have some symmetry for the first and second choice

    • if the answer is numerical, there’s a good chance it’s the same as the number of the question, e.g. the answer for round 2 question 3 is probably 3

     ↩︎
  2. Back when supply chains worked ↩︎


Onboarding when you don't have access to the team

Mitchell Hashimoto, Contributing to Complex Projects:

The first step to understanding the internals of any project is to become a user of the project. You do not have to become an expert user, but my personal graduation criteria for this step is to try to build something real using the project, even if it is small or simple.

Analog: here's a functional area. Set it up for yourself or on your localhost. Now, make a small, well-contained change.

Learn how to build the project and get a working binary (or equivalent). Don’t bother with understanding the build system, the dependencies, etc. Just cargo cult guides, websites, whatever you need to reliably and repeatedly go from source code to runnable binary on your system.

Analog: get to the point you can run the app, run (focused) tests, and see changes in the app. Then start trying to make functional changes.

To learn the internals, I like to use an approach I call “trace down, learn up.”

Analog: for your first several changes, read from the top of the call stack down as far as you can. Don't try to make changes, but do try to note all the landmarks (files) you visit and how they relate to each other. Note “side quests” to investigate later as you go.

Don’t be afraid of complexity. I think too many engineers look at stereotypically complex projects such as programming languages, browsers, databases, etc. as magic or as destined for higher-beings. I like to remember that all projects were started by other humans. If they could do it, I can do it too. And so can you.

You, too, can gain enough understanding of an eight-year-old system to work on it as though you were around when some of it was written. In fact, your effort will compound: the longer you're around, the more you will find curious code that, it turns out, you added in the first place. 😆


Great Albums: Little Rock

Album cover for \_Little Rock\_

Or: Texas, the Good Parts. (Despite the title!)

Or: it sounds like Texas, to me. (Again, despite the title.)

Hayes Carll is my favorite under-the-radar, “this is what country music should sound like” musician. Wit, remorse, nostalgia. Storytelling, quirky characters, relatable characters. Little bit of rock, little bit of western. An ideal Americana mix. It’s all there.

Plus, at 40 minutes, it’s a perfect road trip selection. Always moving forward, but never long-winded.


An un-conference appears

I jumped into a short un-conference organized/hosted by Andy Matuschak last weekend. Within this humble Gather, I came across lots of intriguing people and energizing ideas. Some notes and a few follow-up ideas:

My notes from the event

Napkin is space for ideas and not, it seems, about note capture as an end. Rather, it’s about throwing ideas or quotes at the (metaphorical) wall and letting the system organize them into clusters or connections. If you like some of those idea, you organize the ideas into a linear outline and export that to whatever you like to write with.

Nutshell is about adding an extra dimension to documents on the web. The creator, Nicky Case, described it as a “tool for expandable explanation”. Those explanations take the form of popovers that may contain a bit of text (like a footnote/annotation), a scraped reference to another page (transclusion), or a fully interactive gizmo to explore an idea in a more tactile manner.

Excitement about applying language models (e.g. GPT-3 or DALL-E) to generative creativity came up a few times. Some of the applications demoed were already using language models to augment insight or obviate manual human organization. Using models to ‘read between the lines’ of captured notes/human input and generate new ideas came up as well.

Dissatisfaction with some current PKM tools came up a couple times. In particular, seeking note capture or memory recall as a (customer) engagement end rather than as a means to thinking more/better thoughts. I think I heard a couple criticisms that some tool was “too IT”, but I’m not sure I even heard it correctly or what that would even mean! 😆

Overall: highly recommend seeking folks using computers to augment their ability to create and remember instead of stopping at “finally got my notes app just the way I like it”!


Very handsome task tracking, offline and online

About a year ago, I added a curiously pretentious object to my repertoire of productivity hacks. Analog is a) a paper productivity notation not unlike Bullet Journaling b) printed on pleasantly thick index cards and c) a bit of desk furniture to prop up the cards and store the last couple dozen of them.

The idea is you write your tasks down for today/later/someday. Those tasks sit right in front of you, taunting you. You cross them off as you get stuff done. Now you’ve done a productivity!

Reductionist jokes aside, it’s a fine system. The cards are printed with “Today”, “Next”, or “Someday” at the top and lines to encourage writing down several, but not too many, tasks. It’s a good way to think about organizing what you need/want to get done. As productivity systems go, it’s clear and non-invasive1.

Dave Rupert uses/tried Analog too and has a good take on it.

Tactility is Analog’s leg up. It’s nice to start the day writing out some tasks, looking over the previous day’s cards, shuffling the cards from previous days. Even Things, the best task software, can’t provide the tactile “ahhhh”-moment of crossing an item off your list. Tasteful animation, design, and haptics get close, but touching glass isn’t as good as pen and paper.

That said, I’m not tempted to discard Things. It’s literally one of the best applications I’ve used, ever. That said, it’s charming to have a redundant, back-up scheme for reminding myself of the most important things to accomplish today. Analog is like having a (very handsome) back-up alarm clock to the alarm clock one intends to wake up to. It’s always pleasant to look at, and every so often it is the difference between an energetic day and a day played catching up.


  1. Many productivity schemes feel like they want to take over your life to realize their benefits. IOW, they fantastically fail the “is this sufficiently distinguishable from a cult?” test. ↩︎


Dad rock is a beautiful tapestry

Spooky dad rock - Trent Reznor

Sad dad rock - the National, LCD Soundsystem

Quirky dad rock - Cake

Over-enthusiastic dad rock - Foo Fighters


Perspective, you want it

Perspective is the lens we view our world, work, relationships, etc. All the luck, resources, or knowledge in the world are wasted without good perspective. If we’re talking about life like it’s a role playing game character sheet, you want to have a good perspective stat/multiplier.

Some clever tricks:

  • keep the mind open and flexible to other perspectives; seek them out
  • practice at holding many perspectives simultaneously
  • know the limitations and strengths of a perspective as you navigate the world
  • know when your default perspective makes a scenario more difficult and how to fall back to a perspective you still believe in
  • get out of routines periodically and see if it changes how you see things
  • more so, get out of your bubble; see people of a different background live their lives, reflect on what factors brought them there and how factors are different/similar for your life
  • even more so, travel outside your city/state/country; axiomatically the people most different from you live in a place far away

It’s often tough to gain perspective. Most of the defaults in life steer us away from insight. School, cliques, work, even typical travel nudge us toward seeing familiar things with similar people who live similar lives. I’m by no means an expert at breaking out of these ruts. I’m pretty enamored with my routines. Unfortunately, I don’t have a clever trick to offer here.


Julian Shapiro, What you should be working on:

What is admirable is periodically killing your momentum to ask, Should I still be doing this?

Michael Lopp, The Art of Leadership: Small Things, Done Well:

Let others change your mind. There are more of them than you. The size of your team’s network is collectively larger than yours, so it stands to reason they have more information. Listen to that information and let others change your perspective and your decisions. Augment your obvious and non-obvious weaknesses by building a diverse team. It’s choosing the path of least resistance to build a team full of humans who agree with you. Ideas don’t get better with agreement. Ideas gather their strength with healthy discord, and that means finding and hiring humans who represent the widest possible spread of perspective and experience. Delegate more than is comfortable. The complete delegation of work to someone else on the team is a vote of confidence in their ability, which is one essential way that trust forms within a team. Letting go of doing the work is tricky, but the manager’s job isn’t doing quality work, it’s building a healthy team that does quality work at scale.

Be like Bill Gates and Warren Buffett: If you’re not spending 5 hours per week learning, you’re being irresponsible

Former president Obama perfectly explains why he was so committed to reading during his presidency in a recent New York Times interview (paywall): “At a time when events move so quickly and so much information is transmitted,” he said, reading gave him the ability to occasionally “slow down and get perspective” and “the ability to get in somebody else’s shoes.” These two things, he added, “have been invaluable to me. Whether they’ve made me a better president I can’t say. But what I can say is that they have allowed me to sort of maintain my balance during the course of eight years, because this is a place that comes at you hard and fast and doesn’t let up.”


Notes from the Miles-verse Part 3 and final thoughts

This ended up covering late Davis stuff. He’s basically inventing a new genre of jazz every album or two now.

  • On the Corner: Davis invents funk/soul jazz.
  • A Tribute to Jack Johnson: Davis invents rock/jazz fusion.
  • Tutu: Davis invents synth-jazz/the thing that would get distilled and warped down to New Age/Kenny G jazz in the 90s.

There are numerous live albums! I didn’t go down the rabbit hole on this part. Miles and Quincy Live at Montreux features Quincy Jones and is a pretty great end-of-career retrospective.

“Willie Nelson” on Directions is surprisingly funky.


Overall, I could have gone for less Birth of the Cool-esque and more Bitches Brew. 🤷I like bop, but funk and fusion are more legible to my modest jazz-harmony ear.

Highlights: On the Corner, Jack Johnson, Tutu. The last was originally planned as a Miles Davis/Prince collaboration (❗ ❗ ❗) which fell through. Still pretty good.

What I’d hoped to get out of this, and indeed did, was hearing the invention of large swaths of the jazz landscape over time, album by album. In this way, Miles Davis was a singular influence on the course of music, a lot like Beethoven was.

Hopefully, in my lifetime, we’ll realize another musician has come around and broadly invented entire genres of music every few albums. (I’m assuming we’ll still have albums!)

Previously: Notes from the Miles-verse Parts 1 and 2, Into the Miles-verse.


Leadership keywords

My current theory of leading software teams and projects has four keywords:

  • Trust: I assume everyone is working to get the job done. They assume I will help them get the job done. This starts off more like faith and grows into trust as teams coalesce.
  • Autonomy: each person on the team is independently productive for a significant chunk of their day. When they make assumptions to stay unblocked, they are adept at collaborating asynchronously to verify them or correct course.
  • Agency: each person solves the task they’re working on in a way they see fit, within the conventions shared by the team. If an interesting idea comes up outside of the those norms, anyone can pursue it such that they maintain the trust/faith of their colleagues.
  • Support: each person knows that the team, particularly yours truly, is there to help each other. This most often manifests as pairing on troubleshooting, designing, coding, etc. Most importantly, sometimes it is sharing the load when one person is feeling overwhelmed.

Support is a recent addition. I had previously thought that autonomy and agency were the things enabled by trust. But I’m starting to think1 support is a crucial part of the equation too.

Without support, you’re just throwing people into the pool and telling them they can stay a-float however they like. It omits the “get good enough to swim” part, which is pretty crucial!

This kind of support is most obvious when you’re bringing someone new onto a team. But you need it throughout an individual’s tenure on your team. The people with years of deep experience and history in their head need support of a different variety.


Teaser: I’m on the fence about adding 2-3 more words to my repertoire. There’s a lot of moving parts to leadership!

  1. Largely due to onboarding people to a team/system/organization with a long history. This doesn’t happen without a larger-than-normal support effort. Perhaps that effort is amortizable over time (i.e. writing docs), but it’s still a big lift.

Managers can code on whatever keeps them off the critical path

Should engineering managers write code?:

Spending time in meetings and working through complex team relationship issues leaves you feeling more drained than energized most days. You look longingly at your team and feel a slight tinge of envy. You want to code again.

The good news is that you can! The bad news is that you shouldn’t. At least not directly on your team’s codebase and not on any critical path work.

Good ideas therein! Let me emphasize one I’m particularly fond of.

In my first engineering management role, I had the opportunity to go completely hands off. For a while, I found it a little off-putting. I really like solving problems with code! (I later realized leadership and management are solving problems with people, but that’s for another time.)

I felt a lot better about engineering management once I figured out it gave me license to code on impractical things. When you’re an EM (the hands-off variety, not the sitting-on-the-fence variety), you have the opportunity to code on whatever draws your interest, knowing it won’t block your team.

That’s a pretty rad opportunity for someone like me who’s a bit of an esoteric tinkerer.

If you’re less of a tinkerer and more of a shipper or solver, even the highest functioning teams have some pile of ambitions and ideas they aren’t actively pursuing. An engineering manager can explore the frontiers on these ideas. Maybe a plan is made, research is noted, or its found the idea isn’t all that great after all. Still a win!

As long as your code doesn’t create challenges or blockers for your organization: dive into it, have fun, explore the space!


The paradox of producing process

The agency to create the system or process you want to work in (axiomatically?) implies you’ll rarely get to work in the system because you’re spending a lot of time working on the system by communicating/iterating/supporting it. 🤷🏻‍♂️


Notes from the Miles-verse Parts 1 and 2

Wherein I’m listening to Miles Davis’ studio albums in chronological order. Priors: I have listened to Kind of Blue and Bitches Brew a lot. I’m mostly familiar with “earl years” sort of stuff.

Basically bop

  • Collector’s Item: this album starts to sound “Idiomatically Miles Davis”. Which I guess means “rather abstract bop-vibe”.
  • Bag’s Groove: this is very hip.
  • Cookin’ with the Miles Davis Quintet: I’ll take basically any version of “My Funny Valentine”, same as I will listen to any version of “Caravan”.

The albums Davis made with Gil Evans are my early new-favorites. Miles Ahead, Porgy and Bess, and Sketches of Spain all sound more lofty, less improvised than the earlier stuff. Almost composed, classical music, not unlike some of Mingus’ work.

Very much not bop

Getting into Davis’ fusion era (1968–1991) is my big discovery. I know Bitches Brew is a thing, but where it fits chronologically is the missing piece. Davis entirely switching gears from bop to an entirely different vibe must have been as jarring as Rite of Spring was to Parisans. Favorites so far: Filles De Kilimanjaro, A Tribute to Jack Johnson, On the Corner. In a Silent Way is entirely different from the albums around it in this era, but I like how it’s basically a long song.

Currently listening: Circle in the Round.

Previously: Into the Miles-verse.


Get lost in an idea

Rabbit-hole-athon - it doesn’t look like an event is scheduled, but I dig the idea:

Tl;dr, we are organizing a weekend long IRL rabbit-hole-athon for technologists: an intimate retreat/hackathon dedicated to reading, thinking deeply about a topic, and sharing your learnings with others.

Like a hackathon or BarCamp, but with the intent to focus an individual’s attention on a topic of their choosing instead of diffusing it. (Which is fine, on balance!)

We believe that being a good builder and problem solver is rooted in being a clear thinker. Intentionally dedicating time to exploring, pursuing your curiosity, and understanding things deeply is an important part of exercising this muscle. We believe this is essential in shaping the next generation of technologists, builders, founders, and researchers.

That’s a snappy manifesto! The notion of taking an afternoon/day/weekend to throw tactics to the wind and go deep on a topic is exciting. I’m already thinking about topics I could go down the rabbit hole on. 🧠


Two snappy covers

I saw this local band Adam’s Farm (no relation, promise) a few times when I was 15 or so. In the era of mixing bass guitar out of rock music (no thanks, Metallica), these fellows stood out by being having an EP where I could clearly hear all the instruments. It was almost 25 years later that I’d learn that “Girlfriend” in particular is a Modern Lovers cover.

Sidenote: it seemed like this local band was lost to the internet until recently as well. I figured I’d ripped one of the only copies of this CD, but Adam’s Farm music appeared on YouTube recently. Fancy that!

William Shatner’s cover of “Common People” is less difficult to find, but possibly equally obscure. Back in the late ’90s, Shatner did some voice overs on a Ben Folds pre-solo album Fear of Pop. In the mid ‘00s, Folds produced William Shatner’s album of songs with tons of guests doing the singing and Shatner mostly talking about mortality and aging. Again, it was several years before I heard the original of “Common People”.

I rather like these two covers better than the originals. So it goes with a notable cover!


Like caveats? Try writing about leading teams!

It's tricky to write about leading software teams. Herein, reflections, not complaints, on pursuing higher software leadership truths. Many of which are riffs on 4 Reasons Writing About Software is Hard:

Writing is actually an incredibly relevant skill for engineering leadership (and engineering in general), but it’s still hard. You can have all the insights in the world, and still struggle to convey your message or find the right audience.

First off, writing is hard so writing about software is hard too. Developing our thoughts beyond “that sounded nice in the shower” is hard but rewarding work.

It's difficult to translate "this worked" out of the system of people, circumstances, and goals. As noted above, at one scale everything works, at another basically nothing works.

No advice on software development is universal. From the smallest coding details to how we structure our multi-person/week projects, there are no best practices. There’s only “this worked/failed for us when building this particular project”.

Writing about software leadership ends up being a lot of describing the people and scenarios that led to a successful approach. The trick is that getting down to particulars about people and scenarios is either too personal to share on the internet or too specific/proprietary to make sense outside a specific organization. It’s hard to write high-quality leadership ideas without drowning in setup, hedging, or over-generic characters.

It’s tempting but insufficient to suggest “act as a good person would and most things will work out”. Merely acting as a good person does will not get me out of situations where individual best intentions created bad outcomes. Perhaps specifying what a good person does with enough clarity that another person can apply and/or emulate it is a laudable step.

In practice, it seems better to say “act as a good person 95% of the time but do the minimally jerk-y thing 5% of the time to cut Gordian knots created by good intention”. I’m not happy with that trade-off, but it does seem like a necessary part of leading people. I build context so I can trade accumulated trust for impact when the situation requires it. (Hopefully! I often don’t know if I was spending from a surplus or deficit of trust until much later.)


Benchmarking Rails apps in 5 bullets

  1. When in doubt, measure. Twice!
  2. For ad-hoc/napkin estimates, I use Benchmark.ms { …the code… } to size up the performance of Ruby code.
  3. When I want to do The Science to compare approaches, I use benchmark-ips. It works a lot like Benchmark, but does all the cold start, iteration, and math for you. It’s great, thanks Evan!
  4. When it comes to code that interacts with databases (Postgres, ElasticSearch, HTTP APIs, Redis, etc.) it is almost always the case that one big query is far faster than queries inside a loop (e.g., N+1 queries)
  5. Ruby performance is often limited by creating many objects and the time it takes for the garbage collector to find/free them up afterwards. This is sometimes not the case in recent Ruby versions (see #1).

Bonus useful tools:

  • bumbler - profile loading gems from your Gemfile at application boot. In most Rails apps, there are several seconds of savings to find in lazy loading rarely loaded libraries.
  • active-record-query-trace: shows the call-site and last few stack frames for every query in your development log. Super handy for “where is this blasted query coming from?”

Logistics is endless intrigue

The modern marvel that moves commodities, sub-assemblies, finished product, and people across the planet is largely invisible. Except when I’m bumped from an overbooked flight. Or when I can’t buy your favorite kind of candy because the trucks to move the containers from the ships to the stores are in the wrong place. Or when one can’t build a car in Germany because semiconductor fabrication plants aren’t as elastic as some executive thought they were. Then it becomes all too apparent that the default state of transportation is, absent considerable effort and coordination, for the wheels to fly off constantly.

Hence, A Brief Introduction to Container Logistics is a great primer for understanding the weird state of our world:

The whole shipping process involves dozens of actors, from the exporter, through a long chain of companies who handle the container (incurring costs on behalf of the shipment), all the way to the importer. This creates a trust problem: who is responsible for the problems that arise when one part of this chain goes wrong? Some of these companies are hired by the shipping company, others by the exporter or importer, or even by a logistics company acting as a middle man. This is usually solved by some kind of chain of custody, where any problem with the container must be immediately noted and complained about by the relevant party.

Adjacent: Venkatesh Rao, Remystifying Supply Chains:

Supply chains are a new class of engineered-emergent artifact, one that includes a few other globe-spanning things like the internet, the air travel system, and low earth orbit, that exist at a level of Gaian phenomenology, terraforming, and planet-scale husbandry. We only ever catch local glimpses of these things. The wholes are too big to fit in a single human mind, and the physical embodiments are too vast to capture even on a single map, let alone in a single photograph.

We have to understand these beasts, in all their evolving, learning glory, while living within their bellies. Abstract slicing and dicing of the phenomenology, via aspects like computation, circularity, and situatedness, can only get us so far. To finish the picture, we have to develop a sensitivity to how we inhabit these beasts at a human scale.


Beethoven’s symphonies, visualized and interpreted

Abstract art poster of Beethoven Symphony No. 7

This is extremely my jam. Beethoven Symphonies Abstracted:

To accompany the National Symphony Orchestra’s Beethoven & American Masters concert series, author and illustrator Mo Willems presents Beethoven Symphonies Abstracted, an exhibition of nine large-scale, painted abstractions inspired by the music and genius of Beethoven. Each large-scale work is a response to one of Beethoven’s nine symphonies, divided into panels that visually interpret each symphonic movement.

(Via Austin Kleon)

Previously: my affection for symphonies seven and eight, John Coltrane’s “Giant Steps” animated.


Cool things to do with your spaceship besides launching billionaires

Fancy some near-term imagination on the opportunities the re-commercialization of space presents us? Yes, have some! Science upside for Starship:

It is, however, a fun exercise to enumerate all the ways in which Starship and related technologies can help execute bold, ambitious missions of scientific discovery.

Giant, poly-lithic space telescopes? Sure.

Probably the coolest telescope concept enabled by Starship, though, is the giant segmented telescope to end all giant segmented telescopes. An unmodified Starship can deliver perhaps a dozen 8 m monolithic hexagonal free-flying segments per launch to a target location such as L2, where they self assemble, calibrate, and then focus incoming light. Over a few dozen Starship flights, a truly enormous spherical mirror section perhaps 1000 m in diameter and with a focal length of 1000 km or so can be assembled behind a free-flying sun shade, pointed in a direction of general interest.

Heating (low-key terraforming) Mars with constellations of mirrors? Okay.

The second is mass producing light sails on Earth, launching them into LEO, then flying them to Mars where they can lurk near Mars-Sun L2 and reflect light back at the planet, reducing heat loss during the Martian night.

“Flood the zone” of our planetary neighbors with exploratory robots? As you wish.

Why shouldn’t we have a dedicated orbiter, lander, rover, helicopter, and submarine on every discrete body in the solar system over, say, 100 km in diameter? Let’s build a fleet of clockwork automatons for Venus and an armada of submarines for Europa, Enceladus, and Titan. Let’s darken the Martian skies with helicopters. Let’s drive rovers across the frozen nitrogen plains of Pluto.

I’m sure it’s a lot more complicated than it sounds from these pull-quotes. I’ll bet that SpaceX’s starship won’t meet some of these expectations. We will have to hold our nose or plug our ears as Musk bloviates. Despite all that, it’s exciting that folks are thinking, writing, and blogging about this and some of it could come to fruition in my lifetime!


Great albums: Blood Sugar Sex Magick

Cover art for Blood Sugar Sex Magick

Favorite tracks: “Suck My Kiss”, “Sir Psychosexy”, “Power of Equality”, “The Righteous & the Wicked”.

The essential (in my opinion) Red Hot Chili Peppers album is, for me, a few things:

  • One of the first albums I heard with good bass playing (I ‘grew up’ in the age after Metallica had mixed bass guitar entirely out of their albums and many others followed suit)
  • One of the first albums I heard that was great from end to end and where many of the songs flowed into each other as if played live, meant to fit together, or like they weren’t even separate songs
  • Extremely teenage and horny, of which I was both when I first heard it

It’s an album that has aged well for me. It was an excellent album when I first heard it, and is still an excellent album when I listen to it today.

There are other nice qualities too: Rick Rubin’s production work. When it’s not extremely horny, it has some good lyrics. It’s rooted in the RHCP musical predecessors with intelligent awareness, not than blind copying. They are seeing further by standing on the shoulders of George Clinton, not just sitting on his shoulders for a free ride. It’s just good funk.

And yes, the RHCP joke in The Good Place is superb.