ONI: So I showed off my base reference, and I've just about got it up and running.
Classic off-by-one, of course: I built one more layer in the base than I actually need. I'll chop that off here in a bit.
It's only c40, I feel like I'm having a good run here. I have 9 dups, the shrooms are starting to build. The next thing in the base is to get the kitchen area closer to how I want it when the shrooms are in. I have one hatch ranch to the east, just getting started.
Next up, the drecko ranch, which i'll put just west of the base. I think I've found the place for my rodriguez, further east. It's got a lot ph2o getting dumped to a pool, and a cool steam vent, and there's an ice biome with an AETN right below it.
Actually, ya know what? Maybe the drecko ranch will go *above* the base, over the west half? That might be just the thing.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
"It puts the database on its browser skin, or else it gets the hose again." This task occupies the daily life of a great many programmers. Today, I want to throw out some random sparks of advice for people working in that setting.
Folks, my ideas about changing code are deeply intertwined with my ideas about changing the world, which is a far more important activity than any kind of geekery. Let's geek out, for sure.
But please keep working for change, and supporting those who do.
Black Lives Matter.
In enterprise IT, it is commonplace for backend folks to work on problems shaped like this: there's a web endpoint controller on the top, a database on the bottom, and some simple or complicated business logic in the middle.
ONI: c51, and a couple of building tips. That space next to the musher is going to be infinite food storage. I need it vacuumed out and filled with chlorine.
The stairs down & up on the west are actually a working liquid lock. We usually make permanent ones, but I won't need access to this room, so I really only need the lock for a short time. Two dribbles of water is all it takes. It won't last long, but I don't need it to.
The fastest & easiest way to a vacuum is to fill all the gas tiles with a solid, then use diagonal deconstruct. Whatever was in them is gone when the tile is built, and you get vacuum when it's destroyed. Wouldn't work in this case, but it's the best way.
When we talk about transitioning to microtest TDD, we have to figure out how to provide the right experiences in the right order. That's why I propose we start by getting the experience of changing a well-microtested graceful class.
Folks, my ideas about changing code are thoroughly entangled with my ideas about changing the world, a topic of far greater importance. Let's geek out, by all means, but let's also act outside the monitor.
Black Lives Matter.
"Create Experiences, Not Arguments" is one of the core habits of change-harvesters. We want to take that slogan very seriously when we approach any significant change to our practice. And microtest TDD, believe me, is a significant change.
One of her takes that just features her voice more than her sense of style.
Wright has a lovely not-quite-contralto, but what I really like in general is the richness of her voice connecting, both with the tradition she pulls from and the combo she plays with.