Press "Enter" to skip to content

Posts tagged as “We Call It Living”

[twenty twenty-four day forty-two]: a new life on the off-world colonies

centaur 0

This is your periodic reminder that we may not be on the moon, but we live in a pretty awesome world, where almost every movie, book or comic book you ever wanted is either available to stream over the air or can be readily shipped to your home, genre toys that once were inaccessible are now readily available, and we can shrink a playable Galaga machine down to the size you can put it on your coffee table.

We've got it good. Don't screw it up.

-the Centaur

[twenty twenty-four day twenty-six]: make up your mind

centaur 0

Cat, when it's raining: "Let me out! Let me out! But not this door, it's wet. Let's try another door. And another! Or another! I gotta get out! Just hold the door open until the rain stops!"

Also cat, when it is nice and sunny: "Who cares about going outside? Ima gonna havva nap."

-the Centaur

Pictured: the cat-shaped void, Loki, actually using his void-colored cat tree for once. Image taken in infrared bands and color enhanced by NASA to show surface detail.

[twenty twenty-four day twenty-four]: in foggiest depths

centaur 0

One of the problems with computing is when it just gets ... foggy. Not when you're trying to do something hard, or when two pieces of software are incompatible, no. When things just sort of kind of don't work, and there are no known reasons that it's happening, and no reliable actions you can take to fix it.

Once this happened to me when I was working on a robotics device driver, and I realized the lidar itself was unreliable, so the only way to fix problems was to run each configuration ten times and keep average stats. Broken "worked" around ten percent of the time, whereas "fixed" worked around seventy percent of the time (approaching the rate at which the manufacturer's own software could connect to its own hardware).

Today, I ran into a seemingly simple problem with Anaconda, a Python package / environment management system. Conda lets you corral Python and other software into "environments" with different configurations so that potentially incompatible versions can be used on the same computer (albeit, not at the same time). It even gives you a handy indication about which environment is in use in your command prompt, like so:

There's a seemingly innocent blank line between (ThatEnvironment) and the previous line, yes? Not part of the standard Conda setup, but you can easily add it with a single line of configuration, changing the "env_prompt" to include an extra newline "\n" before printing the environment, like so:

Yeah, that line at the end. "env_prompt: \n({default_env})". In a conda configuration - a .condarc, or "dot condarc" file - which is almost as simple as possible. I don't even think the "channels" bit is needed - I didn't recall writing it, I think it just got added automatically by Conda. So this is almost the simplest possible change that you could make to your Conda configuration, done in almost the simplest possible way.

Except. It. Didn't. Take.

No matter what changes I made to the .condarc file, they didn't affect my Conda configuration. Why? I don't know. No matter what I did, nothing happened. I changed the prompt to all sorts of weird things to try to see if maybe my syntax was wrong, no dice. No amount of searching through manuals or documentation or Stack Overflow helped. I re-ran conda config, re-loaded my shell, rebooted my Ubuntu instance - nothing.

Finally, almost in desperation, I went back to my original version, and tried creating system-wide, then environment-specific configurations - and then the changes to the prompt started working. Thank goodness, I thought, and rebooted one more time, convinced I had solved the problem.

Except. It. Took. The. Wrong. Config.

Remember how I said I created a weird version just to see that it was working? Conda started reverting to that file and using it, even though it was several versions ago. It actively started overwriting my changes - and ignoring the changes in the environment-specific configurations.

So, I blew away all the versions of the file - local, system and environment-specific - and re-created it, in its original location, and then it started to work right. In the end, what was the final solution?

I have no idea.

When I started working on the problem, I wanted Conda to do a thing - print an extra blank line so I could more easily see a command and its result, separate from the next command and result. And so I created a file in the recommended place with a line containing the recommended magic words ... and it didn't work. Then I hacked on it for a while, it sort of started working, and I backed out my changes, creating a file in the same recommended place with a line containing the same recommended magic words ... and it did work.

Why? Who knows! Will it keep working? Who knows! If it breaks again, how do I fix it? Who knows!

This is what I call "the fog". And it's the worst place to be when working on computers.

-the Centaur

Pictured: Sure was foggy today.

[twenty twenty-four day twenty-three]: and for the record …

centaur 0

... it's still one of the worst feelings in the world to turn back the sheets at the end of a long day, only to realize you hadn't blogged or posted your drawing. I had a good excuse yesterday - my wife and I were actually out at a coffeehouse, working on our art, when we had a sudden emergency and had to go home.

I had just finished my drawing and was about to snapshot it so I could post it, but instead threw the notebook into my bookbag, packed it up, and drove us home. Disaster was averted, fortunately, but the rest of the day was go-go-go, until finally, exhausted, I went to turn in and then went ... oh, shit. I didn't blog.

Fortunately, I didn't have to go back to the drawing board. But it did flip over to tomorrow while I was posting ... so, next day's post, here we come.

-the Centaur

Pictured: A jerky shot of me trying to document my wife's computer setup for reference.

Studio Sandi Sells Custom Sustainable Furniture!

centaur 0

So, my wife's furniture business is finally kicking off! Here's the first ad for Studio Sandi's custom sustainable furniture, made from (almost) all eco-friendly, recycled and recovered materials:

Check them out at studiosandi.com , where more information will be added soon!

-the Centaur

Pictured: An ad for Silicon Valley Open Studios, showing four pieces of art and two pieces of custom furniture, almost entirely made from recycled / sustainable materials except for the resin tops.

[twenty twenty-four day twenty]: cat-shaped void

centaur 0

We have a black cat, so we got a black cat condo (just barely visible to the left). But of course, our cat-shaped void is a cat, and so prefers the blue couch, where its voluminous shedded fur is easily visible. My wife caught him in the act, so, enjoy this picture of our cat-shaped void, doing cat-styled things.

-the Centaur

Pictured: Loki on our couch. Interestingly, this picture was taken at an angle, so I rotated it, then used Adobe Photoshop's generative fill to recover the outer edge of the picture. The very outer edge is ... mostly right. Some weirdness is visible in the carpet patterns on the lower left, the brick pattern on the upper left, and whatever it is on the table on the right isn't there in reality. Otherwise, not a terrible job.

[twenty-twenty four day sixteen]: blog early, blog often

centaur 0

I'm a night owl - I'd say "extreme night owl", but my wife used to go to bed shortly before I woke up - and get some of my best work done late at night. So it constantly surprises me - though it shouldn't - that some things are easier to do earlier in the day.

Take blogging - or drawing every day, two challenges I've taken on for twenty-twenty four. Sometimes I say that "writer's block is the worst feeling in the world" - Hemingway apparently killed himself over it - but right up there with writer's block is deciding to call it a night after a long, productive evening of work - and remembering that you didn't draw or blog at all that day.

Sure, you can whip up a quick sketch, or bang out a few words. But doing so actively discourages you from longer-form thought or more complicated sketches. Drawing breathes more earlier in the day, especially in the midafternoon when your major initial tasks are done and the rest of the day seems wide open. And blogging is writing too, and can benefit as much from concentrated focus as any other writing.

SO! Let's at least get one of those two things done right now.

Type Enter, hit Publish.

-the Centaur

Pictured: Downtown Greenville as seen from the Camperdown complex.

[twenty twenty-four day fifteen]: photographic archaeology

centaur 0

I take a heck of a lot of pictures, seemingly way more than most of the people I know other than the ones in the movie industry; in fact, one of my friends once said "your phone eats first". But there's a secret to why I take pictures: it's for something, for the creation of an external memory - and memory is my brand, after all. With those photographs, I can figure out what happened in the past, even sometimes obscure things - like the attachment point of this lightsaber, which isn't just the diamond-shaped piece of wood, but also includes two hooks that seem to have disappeared in the move.

We may not find them, but at least now we know what to look for.

How can you turn the things in your life into an unexpected resource?

-the Centaur

Pictured: the old library, which was very nice, but not as nice as this one: