antrix

The companies building giant AI compute for themselves have started renting it out: SpaceX leased all of Colossus to Anthropic, and Meta says a cloud business is on the table. Apple is about to have the most efficient, most private inference fleet on earth. Can it keep that to itself?

From the article, it seems the information was flowing _from_ the reporter:

> The feds allege that Peltz used disposable “burner” phones and encrypted apps to communicate with a journalist, and that the reporter provided “material nonpublic information about forthcoming articles” which Peltz used to trade in the market “just prior to publication of an article about each company written by the reporter.”

They have a point though, testing patterns are absolutely a real world concern.

I've worked in finance technology for eight years now, in various domains.

As a broad generalization, if you are latency bound (milliseconds or less) then everything is done in code and the DB is never in the main loop.

At the other end, if you are throughput bound - think end of day/month activities - then stored procedures all the way.

For everything in between, prefer to have the logic in code due to the maintenance benefits that come with it.

> Do you have an API on top of DB that enforces the rules?

In general, a database is owned by the app it is associated with and the app mediates all access to that data. The usual enterprise integration patterns (esb, messaging, web services, file dumps) are used to share data with other systems.

> Is the security/data validation also done in the API/app layer?

Largely yes. There's some level of security (like app access control and encryption at rest) that's handled in the DB tier but authorization is largely an app level concern.

Similarly, some constraints are imposed in the DB schema but those are quite basic. Most validation is done in the app tier.

> And those guys hardly ever ship any code due to how encumbered developers typically are in those places and release maybe once every 6 months to a year perhaps.

I've worked in places where some teams ship with this three or six month frequency. They consider it completely normal and find ideas like continuously delivery or even weekly deployments as not just abnormal but risky and irresponsible! This is the very point OP is trying to make, the _normalization of deviance_.

"Compulsory time off" is actually required by law in some regulated industries such as finance.

If I understand correctly, the gitbook toolchain isn't freely available. Nor does gitbook address any of the limitations of Markdown that prompted me to switch to Asciidoc.