spacemanspiff01
Joined 3 years ago
Joined 3 years ago
For context I have a 13th gen intel with the old battery and only get ~4hrs of battery life, but generally go a week or 2 between full shutdowns, since I hibernate all the time. I can close the lid, throw it in my backpack, not use it for the weekend, and when I open it it is ready to go, not having lost charge.
I generally have a better experience than when I was on windows.
That being said, I think the particular bios-chip is a design flaw that they should communicate about and fix for future boards... Probably a teething issue thing, but they should fix it. Either a usable replaceable chip so they can just send out a fix, or the fallback bios chip....
Then once you have the kinda-sorta prototype, do a full rewrite, try to do component modules with interfaces.
(maybe do multiple rewrites depending on architecture complexity)
Then incrementally improve the software quality of each of the components.
---
My thesis in this is that the cost of a refactor has dropped precipitously, LLMs are really good at doing translations, and are pretty good at finding good abstractions if you work them a bit. It is also much faster, becuase in your refactor you try and focus on the big picture and interfaces, and yolo the components... Make sure that they work, but if there is a particular edge case you can fix it later.
I don't know for sure, but I am testing this out and am halfway through a rewrite of a large project into rust from c++ (second step from above) - I am mostly vibe-ing the components, But am paying a lot of attention to the interfaces and layout.
1. The Factory spawning population - This is self-sustained, and never encounters radiation.
2. A subset of the spawned males from the factory population are irradiated, making them sterile.
3. The wild population, consisting of the sterile males + wild males + wild females.
If for some reason the sterile population is not fully sterile (unlikely), then maybe there is a gene that helps for radiation resistance, but the children of that strain will not encounter radiation, so it fades away.
The factories are not going out to the regions where the flies are deployed to get new fly studs.
North Korea is a dictatorship, which one of its main deterrents is to shell soul to oblivion.
I was thinking that Anthropic would just be providing the models/setup support to run their models in aws gov cloud. They do not have any real insight into what is being asked. Maybe a few engineers have the specific clearances to access and debug the running systems, but that would one or two people who are embedded to debug inference issues - not something that would be analyzed by others in the company.
The whole 'do not use our models for mass surveillance' is at the end of the day an honor system. Companies have no real way of enforcing that clause, or determining that it has been violated. That being said, at least historically, one has been able to trust the government to abide by commercial agreements. The people who work in cleared positions are generally selected for honesty, and ability, willingness to follow rules.
I might have missed it in their writeup.