Engineering

Two failures. One evening. Both lied. First, a validation error with values that were clearly fine. Then, a send-to-printer command that disappeared into silence. No confirmation. No error. Nothing. The mission: determine what actually broke. Not what the dialog box claimed broke. Not what the forum said probably broke. What actually broke, isolated layer by layer, with evidence. I print miniatures. I run a Bambu A1 with a 0.2mm nozzle and community profiles for tabletop minis. Orca Slicer is my tool of choice because it gives me more control than Bambu Studio. That control comes with a cost: when things fail, you’re on your own. ...

The electrician was standing in front of my panel. Rows of switches. None labeled. He had a marker. He put it back in his pocket. I asked why. “Because I’m not sure which does what. And a wrong label is more dangerous than no label.” The next electrician would trust it blindly. He walked away. The switches stayed blank. I thought about that for a long time. Then I recognized the pattern everywhere in software. ...

You’re staring at the terminal. You know what to build. But your hands don’t move. The workflow you’ve used for years, the one wired into your hands, feels off. Not broken exactly. Just… wrong-shaped for the work in front of you. I’ve been sitting with this feeling for months. AI agents writing code faster than I can review it. The gap between “I know what to build” and “it’s built” shrinking to minutes. And the growing realization that the process I’d refined over a decade was designed for a world that’s already moved on. ...