justaderp

Janeway’s chaotic evil. Sisko’s chaotic good. Picard’s lawful good. Kirk’s John Wayne with roofies and a starship.

No.

Learned a lot looking up products and understanding what you’ve done. I also realized I’ve not made myself easy to assist. I’ll try again.

When under duress Archer and Janeway are the shallow, emotional humans we often reveal ourselves to be. We throw away our principles as soon as the adrenaline hits, often before. It’s relatable.

Picard’s how we think ourselves. He’s privileged in mature procedure & technology, and has strong external support. He respects justice, law, and principle, then reasons a way to honor all of them in the specific situation. It’s thematically Jesus, OT judge meets NT wisdom, and unsustainably inhuman.

It’s not fair to compare Sisko. He’s lesser Starfleet authority than Archer and Janeway, reasons as well as Picard, he suffered little hope of a life worth living before the series even begins, and Jake’s youth prevents too much initial risk. Sisko by far has the best initial situation to be the best of the lot.

The MB is weak for gen3 PCIe. That’s likely not even 5% loss of GPU performance. It’s a mistake. But, it doesn’t seem worth the money to fix unless there’s also other reasons.

If you’ve trimmed the fat and still are running low on RAM then it’s the priority. Page file usage always kills performance. If you’re not running low then an upgrade does nothing.

I’ve a low risk tolerance with my desktop rig. My next upgrades would be a Gold PSU and line interrupt UPS.

Assuming you’re coming from a linear programming and OOP background, then data (incl. SQL) kinda sucks because it’s not always clear how to apply existing concepts. But, doing so is absolutely critical to success, perhaps more so than in most OOP environments. Your post isn’t funny to me because I’d be laughing at you, not with you.

If a variable is fucked, the first questions you should answer are, “Where’d it come from?” and “What’s its value along the way?”. That looks a lot different in Python than SQL. But, the troubleshooting concept is the same.

If object definitions were replaced by table/query definitions in planning then you’d probably not have made the initial error. Again, it looks different. But, the concept is the same.

Angle iron seems like a very poor choice. I’m assuming it’s been chosen because it’s “free”.

How’d it work out? How’d the welding go?