I've been working longer hours this past week in an attempt to fix PRIDE-Σ' code. But it's hard to know exactly where all these problems are stemming from in the first place. Nothing jumps out at me. Not to sound narcissistic, but I feel our department has done a great job at maintaining the OS over the years — what's more, the base of the code was written by Cardinal Renus. And he's a technical genius. Been studying this stuff longer than anyone across the Beside, that's for damn sure.
Could PRIDE-Σ' issues lie in faulty wiring? Decaying equipment? I have no clue. The only one allowed near the main computer is Renus himself. But I'm sure he would be quick to fix any external issues, if there really were any.
Honestly, I've been working with computers for as long as they've been a part of the Sons' operations. Which, admittedly, isn't a very long time — but still. The way PRIDE-Σ operates is unlike anything I've seen from any other program or piece of software. It's as if commands written in the code are merely suggestions to it. You could tell a dog to sit or stay or do whatever it is you need it to do — but on its bad days, the thing just might not listen to you. Therein lies its free will.
But it's silly to think of a machine like that. I should know as much...
I'm sure there's something here that we're all missing. A reason PRIDE-Σ continues to misbehave, so to speak. Perhaps I need to look outside the box.
Granted, a dog might not always stop digging up holes in your yard, even if you yell at it real strict. But what if you to throw a kind of treat into the mix? Something to reward its good behavior? Encourage its obedience?
What if we could do the same with PRIDE-Σ?
Instead of endlessly scouring for what's wrong inside its code, maybe it would be better to write in events that reward the machine for performing as commanded?
Is such a thing possible? I'm not quite sure. But then, it's often said: "If you deign it to be impossible, the Beside will work swiftly to prove you wrong."