I once came across a similar "solution". The signing algorithm was directly executed from the update package. How would we otherwise be able to update the signature algorithm? Worst part was that it was correct at some point. It was an introduced regression because of a signature change due to " post-quantum safe" signatures now being required by the security team.
Maybe I develop games. Maybe I develop IoT devices. I might even be working in a high-stakes environment where formal verification is needed, who knows.
Whatever the case may be, we all have our reasons for choosing certain technologies. Not everyone is building run-of-the-mill 'backends' after all.
So please, let's stuff that neckbeardy arrogance away. It serves no purpose and distracts from the discussion.
Working with agents and current-generation coding tools to me still feels relatively cumbersome. You have to do a lot of /manual /skill invocations and go through many review cycles before I consider code even close to workable, let alone commitable. I believe orchestrating this whole ordeal can probably be automated/improved through making good use of coding pipelines, thereby reducing manual intervention in the coding phase itself.
So, to minimise reviewing and AI oversight efforts, I was looking for a good way to orchestrate my local pi agent fleet. I found 'synapse' via this Reddit thread [0], in which the author (not me!) also asks for feedback and collaborators. The tool seems very interesting/promising to me!
Final note: I do _strongly_ believe that supervision of the coding process is still a _strict_ necessity. It's just that I think it can probably be more streamlined.
Rohansi was basically asking 'why', you keep on reiterating that DDR uses more power than LPDDR, but fail to answer why this is the case. Is it clock speed? Is it voltage? Is it a protocol/specification difference? 'various reasons' is not an answer.
I understand trimming input fields is typically a useful default, but in this case this prevents me from searching for a space. So maybe it'd be worthwhile to add a `if (trim(str)=="") return str` exception or something similar?
Can confirm. Have encountered many on-prem and lift-and-shift solutions with no automated means of updating certs. The worst contenders are usually 1) executables on windows server (version 2012, of course), 2) old, obscure or very outdated database servers and 3) custom hardware firewalls. They are the worst.
To make things easy they usually all use different cert formats as well, requiring you to have an arsenal of conversion scripts ready.
We have an OCR job running with a lot of domain specific knowledge. After testing different models we have clear results that some prompts are more effective with some models, and also some general observations (eg, some prompts performed badly across all models).
Sample size was 1000 jobs per prompt/model. We run them once per month to detect regression as well.
The A3B part in the name stands for `Active 3B`, so for the inference jobs a core 3B is used in conjunction with another subpart of the model, based on the task (MoE, mixture of experts). If you use these models mostly for related/similar tasks, that means you can make do with a lot less than the 35B params in active RAM. These models are therefore also sometimes called sparse models.
Exactly there's so much stuff you simply cannot configure otherwise. For example disallowing applications to take sole ownership of a mic, in-detail power plans, etc. If they remove the old control panel, your machine basically becomes unconfigurable.