Fordec

[profile.release] overflow-checks = true

What's easier to use as inspiration for coming up with a list of requirements?:

1. A blank sheet of paper

2. A one-shotted POC in the span of an hour with $4 of tokens that is clearly wrong in 20 different ways?

It's true. It says a bunch about their competitors where Nvidia isn't at their a game and have been offering 8Gb cards for a solid decade and nobody out competed them. But also gamers pride themselves on how cheap they are and how they can get a deal, it's not surprising that companies simply just give Nvidia more cash.

Not reacting is a liability. Blue-Green deployment is a liability. Code is itself a liability. Choosing this career at all is a liability.

Due to the small nature of hot patching (eg. bump this dependency, rotate these keys, turn off that config, follow the runbook) it will unlikely need to be a frontier model and is likely able to be done LocalLLM/Jev style decision making rather than having to hand all the keys to frontier model operators.

I fully believe the only sustainable future is that hot patching will need to itself become fully automated. Hot patch now with a minimal allowed amount of line changes to head off the AIs, review it in office hours for auditing and the team is actually awake.

My second belief is that environment variables as a development concept will need to be retired. If it's something that causes a security breach if it by its mere existence on a public git repo, it is information that by design cannot ever pass to a filesystem out of a chain of trust, not by mere development conventions people choose to adhere to.

You can see the thought at 230 of "Ok, that was dumb, gotta move my fingers on the numpad slightly this time to throw them a curveball"

Not advocating this, just more addressing the mindset on it, but in the game of office politics people don't mention concerns ahead of time because they don't want to give the opposing view point opportunity to research how to defeat their argument in a meeting, not that they "can't" give an intelligent response. They're choosing not to in their own self interest.

"The enemy must not know where I intend to give battle; for if he does not know where I intend to give battle, he must be prepared in a great many places. And when he prepares in a great many places, those I have to fight in any one-given place will be but few."

I mean, doesn't this exact statement also apply to the adoption of AI and all the winters that have come before this wave?

Also as someone doing my own implementation at the moment, I expect that there is a big relational database backing the MELT store, just the graph aspect is functionally a big RAG interface on top of it acting as a search cache, not itself the data store.

My local knowledge graph dropped my token usage spend on reads from being 30% of total spend to 2% and I haven't suffered a regex false positive deleting 300 lines of code randomly since. As of this weekend it also now feeds my QA metrics, replacing what was multiple tool calls taking multiple seconds down to about 25ms because it's a single cached graph traversal now rather than multiple tools traversing the same ground repeatedly.

The AAA industry is broken. But there is nothing to repair. The indie industry will continue telling new stories without it. Every gamer will have no shortage of finding games to play. The only problem is if your goal is to employ hundreds or thousands of people and extract money from your audience. If you're in the business of making games and entertaining people, you're already just fine.

Most people making memes never built multicloud or across geo regions