Tell that to Microsoft!
bool?
Tell that to Microsoft!
bool?
In my experience, token limits mean nothing on larger context windows. 1 million tokens can easily be taken up by a very small amount of complex files. It also doesn’t do great traversing a tree to selectively find context which seems to be the most limiting factor I’ve run against trying to incorporate LLMs into complex and unknown (to me) projects. By the time I’ve sufficiently hunted down and provided the context, I’ve read enough of the codebase to answer most questions I was going to ask.
I have the same model, powering 3 machines with an average load of ~125w when it switches to battery power. I have a NUT host on one of the servers which will broadcast the outage for the other machines and the whole stack shuts down after 30 seconds and switches off the UPS at the very end. Gone through about 4 or 5 true power events now and double that in testing (overzealous I know) but the UPS is 2.5 years old now and is doing just fine. I have a spare battery because I heard ~3 years is normal but so far no indication it’s reaching replacement yet.
I think the important thing for these is to not run them down to 0. They’re only good for one event at a time and shouldn’t constantly be switching over without basically a full day of recharging again (more like 16h to recharge).
I can see consistent brownouts and events being a problem for these little machines. I’m planning on upgrading to a rack solution soon and relegating this one to my desktop in the other room (with a fresh battery of course).
I get that, it’s a valid point. But in OOP, objects can be things and do things. That’s kinda the whole point. We’re approaching detailed criticism of contextless development concepts though so it kinda doesn’t matter.
Properties are great when you can cache the computation which may be updated a little slower than every time it’s accessed. Getter that checks if an update is needed and maybe even updates the cached value then returns it. Very handy for lazy loading.
Unfortunately they stop caring after the child is born.
Great tip! I forgot about the demo. I find Fiteness Boxing is just a nice entry level trainer and it really depends on how honest you are with the movements and working to improve your form. I find it is good cardio but maybe that’s just me. I would call it a good supplementary workout for variety/changing things up with Ring Fit which can be a bit much some days (for me at least).
Nice, Fitness Boxing is a really great series I’m glad it’s continuing. Became one of my pandemic routines and has stuck with me. Great cardio.
The odd config files on inconsistent drive should just be symlinks (I think you want hard links?) so that your repo can contain all your actual code and file tracking. If necessary, keep a script on hand that can be run when mounted to recreate broken links.
This is a very strange setup and goes against standard practice separation of software and hardware unless this is some embedded thing in which case you wouldn’t have a repo on it at all.
This is why engineering managers need to come from engineering. If they couldn’t help out in the codebase in an emergency situation, they shouldn’t be making decisions like this. It’s not unreasonable for ELT to ask questions about this but if their reporters are not telling them the truth, the whole structure is broken.
Yeah! Very cool that he got there, my attention was just interrupted by not really connecting with what he was saying, but I’m glad I continued watching. I’m very much locked, relating to his discussion of no inner monologue.
20 seconds in and I already can’t relate, can’t see things when I close my eyes.
Or just make a bunch of static helpers >:)
I’d prefer GNU’s ddrescue just because I find it more robust and has better progress output. It’s functionally the same interface but lets you use a mapfile to resume sessions should anything happen to interrupt the copy.
Arguably I’m against this because you never know what’s going to happen and the conventional wisdom for appliances like this is to just backup any important configs, backup your containers and vms, then do a fresh install from the latest install media on the new disk followed by a restore of the backups. It might take a little more time but it’s negligible and allows you an opportunity to review your current configs, make necessary changes, and ensure your backups are working as intended.