SleeplessCityLights

I have the perfect module to use this once. Most people will see it and will figure out that it is doing what it should, but no one can change it because the file will be LFS locked like 99% of the time.

And I was a bit pissy when my DM collapsed a cave on me in wolf form because I was using wild shape forms more than I was humanoid.

My friends that play CoD only really play CoD, a few are trying BF6. They never play any games with me because my games are uninteresting. My game selection of infinity minus 1 is considered uninteresting compared to their game selection of 1. You got the age all wrong though, they are 20 to 50.

The ports are not built into the chassis. They are modules for slots that the chassis has. The framework 12 has 4. I am not sure if you can output to 4 displays but you can have 4 DisplayPort modules plugged in. I think the latest batch has better processor options.

I guess Post Media is going to have to do a huge Zionist push to try and keep the Boomers in line.

Pen and paper notebook. One for Home and one for work. I use notes on my phone when I don't have my notebook and copy them later on. Nobody at work knows that I have terrible short term memory because I "remember", checks notes, everything.

You are not wrong.

Someone said that coop is not in the game as advertised on Steam and they were going to add it at a later day. Is that true?

What are the user reviews like? Reviews by the media for games made by these mega studios are paid for, so I disregard those.

I look at it differently, everything used to be hobbled together messes without real consideration for running live. Then when you go to scale, you had to redo the whole thing because it's base architecture was garbage. This is going to sound dumb, but the philosophy behind DevOps creates an environment that encourages building extensible systems that hopefully will not require taking a fucking sledge hammer to the systems to upgrade when you get users. My role in particular would require time from a dev from each team and a SysAdmin that understands software and OS at a low levell. That is really inefficient and has communication gaps.

Most DevOps spend our days designing and coding. We are deeper into architecture than anyone else, the dev team does not even consider deployment and uptime. We have to go to each separate teams meetings because our input is needed for many decisions. I had no idea that it was like this when I got into it.

When I was a Sysadmin at a MSP, we had client with 2 main sites and multiple satellite sites. At one of the satellite locations there were two servers. The first ran a bunch of VMs and the second was the backup. If you disconnected the backup, the AD stopped working everywhere and half of the NAS storage was not reachable. As a far as anyone knew the second server was set to spin up replacement VMs if the first went down and nothing else. We were a pretty shitty MSP and never spent any time doing proactive work. So when that server dies, that company is going to have the most epic outage that will cost them a fortune.