• 10 Posts
  • 783 Comments
Joined 3 years ago
cake
Cake day: August 11th, 2023

help-circle





  • Honestly we need bidirectional human gates for this not more AI arms race imho.

    I want a job post cryptographically signed by the lead of the team I am applying for and I’ll sign mine the same. Ideally with a token system that requires human input, like pin + bio(bio is useless on its own and should be local to the device only). Ideally we both have some FAQ supplement attached like -+25% pay range for them for the position, I’ll put my asking offer in the app. Include a pending negotiations application type as well.

    We get past that? Send me an email asking for follow ups based on my resume or what wasn’t covered, ill ask you follow ups. Schedule a paid audition/meeting after that with the team just to be sure I can actually do the role and that the role is in fact what they said it was.


  • One idea that I think would be neat would be to expand it beyond written texts. For example: https://chewydecimalsystem.org/

    I am somewhat biased in this regard too though, while physical location has to be tied to a singular thing, with digital mapping tag systems, even better if they are scalable, make for much more accurate catalogs.

    For example the arch wiki is a reference source, but of what info? Hierachical stacking helps but falls apart when now the gaming sections of the arch wiki can’t be found next to the Windows gaming sections because they are isolated by OS instead of by gaming, or you are digging through every OSs collection of gaming information when you do have an OS specific question.






  • Context collapse and hallucination in the face of anything novel has been my experience 90% of the time. I even tried context compression by trying to do the research, test spec, plan, code tests, product spec, plan, code product method, but then the issue was the plan satisfied the AI too quick (“actually we already test all of the code, you can see that by reading the “we test all of the code” spec”).




  • They are both declarative. The main difference is NixOS has the package build system built into its package management vs Microos which uses zypper and the Open Build System for package building.

    Both have declarative config files you either activate via command or get automatically referenced on reboot.

    For microos it both ignition, AND combustion.

    I’ll be honest though both have been a total pain in the ass (I say with love they are still opensource and Linux in the best of ways).

    There is a tool kit for sle micro (and I assume microos too) called elemental that builds them from ContainerFile/DockerConfig files that just feels more sane to me. If it gets too complex for a containerfile I’m doing something wrong anyways imho. That said I do really like NixOS/Guix ability to have the dev build tool, package build tool, distro build tool, and sysadmin tool all be the same language.


  • I use VMs for OS isolated and hardware isolation. I run containers on top of OSs for apps.

    That said I use Harvester so I can run containers on bare metal AND VMs as containers.

    Even on one bare metal I do this, so I can spin up a test VM of harvester to confirm configs. If you one node is super beefy a neat trick is to have VMs running a cluster so you can have a kind of high availability even if your infra is a single point of failure.