

Why are AI agents on the org chart? That’s odd and sketchy. Seems like it could be some sort of fraud to pad numbers.


Why are AI agents on the org chart? That’s odd and sketchy. Seems like it could be some sort of fraud to pad numbers.


You’re going to a lot of effort to not actually mention what this thing is, which makes me wonder what it is and I suspect knowing that would provide additional and useful context.
I work at an Infrastructure Cloud company. I design and implement API and Database schemas, I plan out backend workflows and then implement the code to perform the incremental steps of each workflow. That’s lots of code, and a little openapi and other documentation. I dig into bugs or other incidents. That’s spent deep in Linux and Kubernetes environments. I hopefully build monitors or dashboards for better visibility into issues. That’s spent clicking around observability tooling, and then exporting things I want to keep into our gitops repo. Occasionally, I’ll update our internal WebUI for a new feature that needs to be exposed to internal users. That’s react and CSS coding. Our external facing UI and API is handled by a dedicated team.
When it comes to learning, Id say find a problem you have and try to build something to improve that problem. Building a home lab is a great way to give yourself lots of problems. Ultimately, it’s about being goal oriented in a way where your goal isn’t just “finish this class”.


This is because there isn’t a job shortage. It’s offshoring. The company I (thankfully willingly) left 2 years ago has shifted all of their software hiring to Europe. And since I left has had multiple US focused layoffs. All while the Euro listings keep popping up. And I get it, the cost of living is much lower and the skill set is equivalent. So yea, get your bank. But, this is companies exploiting Europe/Asia, rather than it being something Europe/Asia is immune to.


Yea, it’s the combo of the chiller and cooling tower is analogous to a swamp cooler. The cooling tower provides the evaporative cooling. The difference is that rather than directly cooling the environment around the cooling tower, the chiller allows indirect cooling of the DC via heat exchange. And isolated chiller providing heat exchange is why humidity inside the DC isn’t impacted by the evaporative cooling. And sure, humidity is different between hot and cold isles. That is just a function of temperature and relative humidity. But, no moisture is exchanged into the DC to cool the DC.
Edit: Turns out I’m a bit misinformed. Apparently in dry environments that can deal with the added moisture, DCs are built that indeed use simple direct evaporative cooling.


Practically all even semi-modern DCs are built for servers themselves to be air cooled. The air itself is cooled via a heat exchanger with a separate and isolated chiller and cooling tower. The isolated chiller is essentially the swamp cooler, but it’s isolated from the servers.
There are cases where servers are directly liquid cooled, but it’s mostly just the recent Nvidia GPUs and niche things like high-frequency-trading and crypto ASICs.
All this said… For the longest time I water cooled my home lab’s compute server because I thought it was necessary to reduce noise. But, with proper airflow and a good tower cooler, you can get basically just as quiet. All without the maintenance and risk of water, pumps, tubing, etc.
A coworker of mine built an LLM powered FUSE filesystem as a very tongue-in-check response to the concept of letting AI do everything. It let the LLM generate responses to listing files in directories and reading contents of the files.
Honestly, I don’t mind them adding ads. They’ve got a business to support. But, calling them “quests” and treating them as “rewards” for their users is just so tone-deaf and disingenuous. Likewise, if I’ve boosted even a single server, I shouldn’t see this crap anywhere, let alone on the server I’ve boosted.


After repeated failures to pass a test, I do not think it is unreasonable for the business to stop paying for your attempts at a certification. Either directly via training sessions and testing fees, or indirectly via your working hours.


In the US, salaried engineers are exempt from overtime pay regulations. He is telling them to work 20 extra hours, with no extra pay.


In a centralized management scenario, the central controlling service needs the ability to control everything registered with it. So, if the central controlling service is compromised, it is very likely that everything it controlled is also compromised. There are ways to mitigate this at the application level, like role-based and group-based access controls. But, if the service itself is compromised rather than an individual’s credentials, then the application protections can likely all be bypassed. You can mitigate this a bit by giving each tenant their own deployment of the controlling service, with network isolation between tenants. But, even that is still not fool-proof.
Fundamentally, security is not solved by one golden thing. You need layers of protection. If one layer is compromised, others are hopefully still safe.


If we boil this article down to it’s most basic point, it actually has nothing to do with virtualization. The true issue here is actually centralized infra/application management. The article references two ESXi CVE’s that deal with compromised management interfaces. Imagine a scenario where we avoid virtualization by running Kubernetes on bare metal nodes, and each Pod gets exclusive assignment to a Node. If a threat actor has access to the Kubernetes management interface, and can exploit a vulnerability to access that management interface, it can immediately compromise everything within that Kubernetes cluster. We don’t even need to have a container management platform. Imagine a collection of bare-metal nodes managed by Ansible via Ansible Automation Platform (AAP). If a threat actor has access to AAP and exploit it, it then can compromise everything managed by that AAP instance. This author fundamentally misattributes the issue to virtualization. The issue is centralized management and there are significant benefits to using higher-order centralized management solutions.


I’m not saying they were purposefully cheating in this or any tournament, and I agree cheating under that context would be totally obvious. But, it is feasible that a pro worried about their stats might be willing to cheat in situations where the stakes are lower outside of tournaments.
What I also don’t understand is, if this hacker has lobby wide access, why was it only these two people who got compromised? Why wouldn’t the hacker just do the entire lobby? Clearly this hacker loves the clout. Forcing cheats on the entire lobby would certainly be more impressive.
PS. This is all blatant speculation. From all sides. No one, other than the hacker and hopefully Apex really knows what happened. I am mostly frustrated by ACPD’s immediate fear mongering of a RCE in EAC or Apex based on no concrete evidence.


This isn’t a statement from Apex or EAC. The original source for the RCE claim is the “Anti-Cheat Police Department” which appears to just be a twitter community. There is absolutely no way Apex would turn over network traffic logs to a twitter community, who knows what kind of sensitive information could be in that. At best, ACPD is taking the players at their word that the cheats magically showed up on their computers.
PS. Apparently there have been multiple RCE vulnerabilities in the Source Engine over the years. So, I’m keeping my mind open.


I do not buy this RCE in Apex/EAC rumor. This wouldn’t be the first time “pro” gamers got caught with cheats. And, I wouldn’t put it past the cheat developers to not only include trojan-like remote-control into their cheats, but use it to advertise their product during a streamed tournament. All press is good press. And honestly, they’d probably want people thinking it was a vulnerability in Apex/EAC rather than a trojan included with their cheat.
I’m sure that’s totally going to help OCI’s reliability. And Ashburn won’t die for 3 straight days again, like it did this week.