Look at the code for the war games. It is an absolutely trivial and incredibly unrealistic handwritten set of rules that determine power. See the function `calculate_relative_fighting_power` for instance.
This is about as close to a realistic simulation of war as tic tac toe with nukes thrown into it.
Much of such issue tracking systems may be better in the repo in the first place. A Jira issue could just be a markdown file committed in the repo. A code review could just be commits of inline remarks/comments.
Maybe there is some value to slapping on a web interface on top of that data for ease of use, but as to where the data lives I'm leaning towards putting everything in repo.
JS frameworks were invented to deal with clunkiness of Vanilla Javascript and got bloated to include everything and the kitchen sink. All of a sudden they're 'ecosystems'.
Modern JS + Web components with the light layer of Lit on top solve at least 80% of the issues there were and are with just plain JS. Close to actual web standards and thus play nice with almost everything. By design they fit into a far more modular approach than React or Vue or Svelte.
Agreed. The amount of effectively annotated (possibly very sensitive) data that users are voluntarily shoving across the line seems worth losing some money over. I imagine that data is also not exactly safe from the Chinese government.
> Learning from others at a small scale is not only socially acceptable, but is the foundation of how advancement works.
Exactly, if anything, the logic (a bit bad -> really bad) shows that one person learning from one thing is far inferior to one person learning from every thing (a bit good -> really good).
> It's a nightmare full of wrestling with the LLM when you try to tell it the version of the framework and that it changed a lot from the previous version and yadda yadda
Tip: Add a default instruction to look at the actial downloaded source code of the dependencies used (assuming you're not dealing with closed source dependencies). Have the agent treat it as your own (readonly) source code instead of relying on model training data and possibly mismatching documentation on the web. Then it just greps for the exact function signatures and reads the file based documentation.
> The goal was to raise as much money as possible as fast as possible before the curtain is pulled back to reveal the Wizard's empire of lies.
There may be some lies, but a big part of the backlash against AI is that it is too effective. The backlash is growing precisely because people are finally getting out of the "it's just a tool and there will always be a place for humans!"-denial phase and into the "they took our jobs!"-anger phase. They're seeing the writing on the wall many (although surprisingly not all) in the tech sector saw long ago.
Additionally, I'm quite sure it's not backlash against slop, as some might think. People have disliked spam and ads forever, but all in all they'll happily stomach loads of it just to watch some badly written Hollywood or Netflix human slop.
No, it isn't. Look at the absolutely trivial code used to simulate war: https://github.com/kennethpayne01/project_kahn_public/blob/m...
Having LLMs play nonsense toy simulations like this tells us very, very little about whether they would use nukes in real life war.
reply