Conversation

Notices

1. Embed this notice
   :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 15-Dec-2024 04:57:20 JST :apa: スプリットショックウイルス †

   • かき@GNUsocialJP

   Like you should keep your nose in your bash handbook and stop influencing what our purchasing decisions are.

   You don't even make changes to the code to better accomidate the hardware. I end up being the one that does that, all you do is see if it theoretically possible to run your code on it.

   Everyone is starting to see that, and everyone is starting to get tired of it.

   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 15-Dec-2024 04:57:14 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • 🍔fat fuck🍔 (road to sick cunt)

     @not_benis

     His argument is that if I have two 45 bay chassis with 8TB drives. If the a chassis were to fail that's less data loss than if they were a single chassis with 16TB drives.

     We'd repair the server in either case but he wants less risk.

     It's solely dependant on how much data is in one location.

     However we are now moving datacenter were space is now a premium and so is energy usage as we are over capacity for heat and power at our current location.

     So price and data density are now more important than a programmer's feelings.

   • Embed this notice
     🍔fat fuck🍔 (road to sick cunt) (not_benis@cawfee.club)'s status on Sunday, 15-Dec-2024 04:57:15 JST 🍔fat fuck🍔 (road to sick cunt)

     in reply to
     @splitshockvirus "why yes, this drive that sits mostly idle is surely going to fail within a month"
   • Embed this notice
     🍔fat fuck🍔 (road to sick cunt) (not_benis@cawfee.club)'s status on Sunday, 15-Dec-2024 04:57:16 JST 🍔fat fuck🍔 (road to sick cunt)

     in reply to
     @splitshockvirus if the company has a proper backup strategy I don't see why you'd even need to trust the hardware
   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 15-Dec-2024 04:57:16 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • 🍔fat fuck🍔 (road to sick cunt)

     @not_benis

     has a proper backup strategy

     This is for the backup strategy.

   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 15-Dec-2024 04:57:17 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • 🍔fat fuck🍔 (road to sick cunt)

     @not_benis No this JUST the developers. CEO doesn't care but our systems director is starting to get annoyed with their bullshit.

     Computers are going to get larger regardless on whether you feel "safe" on how much data you have in one computer/location. And when procurment has to pay more for less data (8TB drives compared to 16TB) the CEO is not going to be happy about that.

     A lot of the inefficiency that has occured has been due to them just putting the responsibilty on my department. Everyone is starting to become aware of it, and they are not having it.

     Again ship is sinking they are starting to see why.

   • Embed this notice
     🍔fat fuck🍔 (road to sick cunt) (not_benis@cawfee.club)'s status on Sunday, 15-Dec-2024 04:57:18 JST 🍔fat fuck🍔 (road to sick cunt)

     in reply to
     @splitshockvirus board of directors full of MBAs I'm guessing
   • Embed this notice
     🍔fat fuck🍔 (road to sick cunt) (not_benis@cawfee.club)'s status on Sunday, 15-Dec-2024 04:57:19 JST 🍔fat fuck🍔 (road to sick cunt)

     in reply to
     @splitshockvirus STOP SUBPOSTING YOUR COLLEAGUES IRL, THEY AREN'T GOING TO SEE THESE
   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 15-Dec-2024 04:57:19 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • 🍔fat fuck🍔 (road to sick cunt)

     @not_benis

     "I don't think we should purchase 1TB hard drive because that's a lot of data we could lose if the drive died. We should instead purchase 20x 50GB as that will reduce our data loss risk"

     It's fucking madness.

   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 15-Dec-2024 04:57:43 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • 🍔fat fuck🍔 (road to sick cunt)

     @not_benis it's a circus here. And I'm the professional clown.

     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 15-Dec-2024 04:57:44 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • 🍔fat fuck🍔 (road to sick cunt)

     @not_benis

     They aren't

     You can pay for replication to another datacenter, and we also have a Veem service that's thankfully not in my control.

   • Embed this notice
     🍔fat fuck🍔 (road to sick cunt) (not_benis@cawfee.club)'s status on Sunday, 15-Dec-2024 04:57:44 JST 🍔fat fuck🍔 (road to sick cunt)

     in reply to
     @splitshockvirus oh my God
   • Embed this notice
     🍔fat fuck🍔 (road to sick cunt) (not_benis@cawfee.club)'s status on Sunday, 15-Dec-2024 04:57:45 JST 🍔fat fuck🍔 (road to sick cunt)

     in reply to
     @splitshockvirus you make it sound like your backups aren't layered