If it works but the design is terrible - is that still success?

In the short term yes. Long term, no. But I guess you can say the same thing about a team of engineers taking shortcuts

Horses work, Telegraph works, Gas lamps work, etc.

this is a good question. what would make you reject an otherwise working PR on design grounds?

But I assume students already aren't allowed to just submit genAI output and afaik most classes don't involve computer use, so what's really the change?

Which is why they are rushing to an IPO.

Did iran win? Their economy is on the brink of collapse with no relief in sight, and countries are investing in infrastructure to bypass the strait.

And sure oil prices have gone up, but not doomsday scenario prices.

A bit of a pyrrhic victory if you insist on defining that as a victory.

Sometimes everyone's a loser.

Doesn't Europe already have a digital service tax?

Bitmap brothers are also responsible for one of the most underrated RTS games imo: "Z"

I don't understand how come monorepos never just got "solved", and why git didn't expand in that direction.

I switched from a company with a monorepo to one without, and it just feels like going back to the stone age.

I work at a monorepo company and any time someone gets to work on a project that necessitates working outside of the monorepo, it's a night-and-day improvement.

Tools, especially open source ones (linters, static analysis, scanning, LSPs, IDEs, etc) are not built for monorepos, and with AI Agents working in the monorepo results in an enormous increase in input tokens as the agents are constantly trying to grep this giant source tree.

I'm sure it's possible that we're doing the monorepo thing wrong, but I'm genuinely curious what the upside is that you're experiencing? Or are these drawbacks unique to our implementation?

> Tools, especially open source ones (linters, static analysis, scanning, LSPs, IDEs, etc) are not built for monorepos, and with AI Agents working in the monorepo results in an enormous increase in input tokens as the agents are constantly trying to grep this giant source tree.

I've been thinking that one could dynamically patch .claude/settings.json (or its equivalent for other agents) to allow reads/writes only to the active app/package being edited and its dependencies (other packages/apps).

You can, if you have a trusted build graph. I know that “cone-shaped” checkout tools like this are common in monorepo environments, but unfortunately there aren’t any maintained open source implementations that I’m aware of.

This is a great idea.

I feel like almost every standout product in the world was a result of someone with good instincts and not the results of XFN communication.

Unfortunately it is still the job...

Why would they do this extra step if that were the case?

> A fourth person familiar with the matter said that while Central Command — which oversees U.S. forces in the Middle East — has nearly used up the land-based missiles it had before the war began, it has been able to reload from U.S. military supplies elsewhere in the world.

The title seems fairy inaccurate

It also says they declined to say how many the US has left. And saying “person familiar with the matter” is doing a lot of work. It could be anyone with no direct information. This is what laundering a bogus story looks like.

Exactly how many people do you think are allowed to communicate the status of weapon stockpiles? You are only ever going to get off-the-record comments or a top official letting details slip that should have remained secret.

I don’t think the title is inaccurate and robbing Peter to pay Paul isn’t the military flex Pete Hesgeth may think it is. Anyone who has ever slept under a too-small comforter knows how this will go.