(no subject)

[randomdreams]

This whole week has been a process of me spending the whole day trying to fix broken things on my test system, staying late until I get everything running, doing one quick test run to make sure everything is working 100% correctly, going home, coming in the next morning, rerunning the same test, and having multiple subsystems of the test system fail, glow, catch fire, or just smoke a lot, and I then spend the whole day trying to get back to where I was the night before.
Three days in a row of that gets really, really old.
I could say "hey there's nothing left to fail" but I've already had things fail, that I replaced with brand new ones, that have themselves failed, under conditions where they should not fail.

Comments

[darkoshi]

That sounds similar to a lot of my work, just in a different way. Spending a lot of effort just to keep what was working, still working, even without having made any progress on what I was working on. Due to having to pull other people's code updates, and software upgrades, and changes to jar versions, etc. Or some config value that I changed and forgot about, and didn't realize would cause a problem.

[amaebi]

The new version of Sisyphus. But you don't deserve the punishment. :(

I'm so sorry.

[basefinder]

You reminded me of something I forgot to post several weeks ago.

By replacing the weak, bent hook connector in my seat (lumbar adjustment) with a several-hundred pound rated quicklink, I replaced the weakest link in the system with something much, much stronger. So next time that system reaches stress point and fails, my new link will survive and something more difficult to replace will break instead.

[randomdreams]

The electrical engineering equivalent is "everything on the board is a fuse, eventually."

[malterre]

Sounds maddening!

[ivy]

Arrrrrrrrrrgh pirate sympathy.

[myka]

oh no! :-o