nyrikki

13 ms·

121.
by nyrikki 9mo ago
Note that while containers can be leveraged to run processes at lower privilege levels, they are not secure by default, and actually run at elevated privileges compared to normal processes. Make sure the agent cannot launch containers and t
122.
by nyrikki 9mo ago
To add to this, The concept of connascence, and not coupling is what I find more useful for trade off analysis. Synchronous connascence means that you only have a single architectural quanta under Neil Ford’s terminology. As Ford is less re
123.
by nyrikki 9mo ago
Like most cults, you ignore direct links with cites from multiple governments agencies, but here is another. https://www.upturn.org/work/comments-to-the-cfpb-on-data-bro... > Most employers we examined used an ATS c
124.
by nyrikki 9mo ago
Google "doesn't sell your data" but RTB leaks that info, and the reason no one is called out for "buying Google searches and denying applicants for searching for naughty words" is because it is trivial to make legal
125.
by nyrikki 10mo ago
> If an assistant offered up suggested code, the code ran successfully, and the user accepted the code, that was a positive signal, a sign that the assistant had gotten it right. If the user rejected the code, or if the code failed to ru
126.
by nyrikki 10mo ago
> In the documentation, IBM warns that setting auto-approve for commands constitutes a 'high risk' that can 'potentially execute harmful operations' - with the recommendation that users leverage whitelists and avoid w
127.
by nyrikki 10mo ago
Be very careful with that assumption. The distros try, but one complex problem with a project that holds strong opinions and you may not have a fix. The gnome keyring secrets being available to any process running under your UID, unless tha
128.
by nyrikki 10mo ago
While practically useless in reality /usr/local is `site-local software`, E.G. software that if you nfs mounted /usr, would be local to the `site` not the machine. The BSD ports explanation is a bit revisionist I hate to sa
129.
by nyrikki 10mo ago
Much of the podcast problems were due to Honey leaking any promo code to the world, including employee discounts and customer specific discounts. When Intuit is scraping every browser tab, there is no way to link a podcast campaign with eng
130.
by nyrikki 10mo ago
TLA+ is not a silver bullet, and like all temporal logic, has constraints. You really have to be able to reduce your models to: “at some point in the future, this will happen," or "it will always be true from now on” Have probabil
131.
by nyrikki 10mo ago
I resorted to a local forgejo + woodpecker-ci. Every time I am forced back to GitHub for some reason it confirms I made the right choice. In my experience gitlab always felt clunky and overly complicated on the back end, but for my needs l
132.
by nyrikki 10mo ago
This script does nothing to solve that and actually exasperates problem of people over specing. It makes assumptions about pricing[0], when if you do need a peak of 8GB it would force you into launching and consuming that 8GB immediately,
133.
by nyrikki 10mo ago
> Once the code for all destinations lived in a single repo, they could be merged into a single service. With every destination living in one service, our developer productivity substantially improved. We no longer had to deploy 140+ ser
134.
by nyrikki 10mo ago
IMHO there are some serious problems here that won't relate to many situations, and is not really "waste" in the way claimed and will actually probably result in greater spends. > Memory waste: request - actual usage [0] M
135.
by nyrikki 10mo ago
As we are talking about micro services, K8s has two patterns that are useful. A global namespace root with sub namespaces will just desired config and current config will the complexity hidden in the controller. The second is closer to your
136.
by nyrikki 11mo ago
I am working on a larger project about containers and isolation stronger than current conventions but short kata etc… But if you follow the podman instructions for cuda, the llama.cpp shows you how to use their plugin here https:/&#x2
137.
by nyrikki 11mo ago
I am running a container on an old 7700k with a 1080ti that gives me vscode completions with rag with similar latency and enough accuracy to be useful for boilerplate etc… That is something I would possibly pay for but as the failures on co
138.
by nyrikki 11mo ago
The problem is that math is not some universal language, it is a broad field with various sub domains with their own conventions, assumptions, and needs. Polysemy vs Homonymy vs Context Dependency will always be a problem. There are lots of
139.
by nyrikki 11mo ago
To add to the other responses, cloud-init is also not a secure delivery mechanism, you shouldn’t be using it to deliver sensitive information, but you could use it to kick off scripts that access more appropriate mechanisms, like in AWS whe
140.
by nyrikki 11mo ago
You seem to have a misunderstanding of what namespaces accomplished on plan9, or that it was extending Unix concepts and assembling them in another way. As someone who actually ran plan9 over 30 years ago I ensure that if you go back and lo
141.
by nyrikki 11mo ago
The tooling for that exists today in Linux, and it is fairly easy to use with podman etc. K8s choices clouds that a little, but for vscode completions as an example, I have a pod, that systemd launches on request that starts it. I have ngin
142.
by nyrikki 11mo ago
The 100% test coverage metric is far more then "entirely useless" it is typically incredibly harmful. Brittle meaningless tests tend to lock bad decisions in, and prevent meaningful refactoring. Bad tests simply are code debt, a
143.
by nyrikki 11mo ago
I expect the downvotes here but it is important. It doesn’t matter if you get there through Trakhtenbrot or Rice. Codd’s normal form is a projection, it will turn your fancy model logic into classic logic. IMHO it is always something to loo
144.
by nyrikki 11mo ago
Hindsight bias is always easier but: > FAANG-style companies are unlikely to adopt formal methods or relational rigor wholesale. But for their most critical systems, they should. It’s the only way to make failures like this impossible by
145.
by nyrikki 11mo ago
And move to rootless ASAP.
146.
by nyrikki 11mo ago
> You’re also missing an important factor: Many drives now reserve some space that cannot be used by the consumer so they have extra space to work with. This is called factory overprovisioning. This has always been the case, thus why eve
147.
by nyrikki 11mo ago
> Contrast this with equivalent code that is full of logistics, where I’m using only basic Python language features and no special data wrangling package While I am not a python cheerleader, but a user because the reality is that it is a
148.
by nyrikki 11mo ago
You can run pods, with podman and avoid the entire k8s stack or even use minikube on a machine if you wanted to. Now that rootless is the default in k8s[0] the workflow is even more convenient and you can even use systemd with isolated use
149.
by nyrikki 11mo ago
I just gave up and built an AM4 system with a 3090 because I had 128G of ddr4 udimms on hand the whole build was for less than just the memory would have cost for an AM5/ddr5 build. Really wish that I could replace my old skylake-x sys
150.
by nyrikki 11mo ago
For the crowd I ran in the lack of real branching and the need to use DirState or Queues for selective commits made Mercurial feel too much like p4, where git felt so freeing, especially with spikes etc...which would be forever in the repo

More ›