Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
AI slop is good, actually. Slop is what enables fast parallel experimentation. The etiquette and skill is understanding the boundaries of where slop exists and the extent to which it should be cleaned up and how.
A few examples:
I’m working on the internals of some system right now. The API and GUI of this thing is fully zero shame slop. It’s horrible. But it lets me focus on the core quality while shipping a usable piece of alpha quality software to testers (transparent about the slop frontend).
Similarly, this system has plugins. We sent agents in Ralph loops overnight to generate dozens of plugins. The plugins are slop. The quality is bad. The plugin API/SDK is absolutely not done.
But we can test a full GUI with a full plugin ecosystem. When we change the API, we can regenerate them all. The cost of change is just tokens, the velocity is incomparable to before.
I built Terraform. We tested and shipped TF 0.1 with about 3 very weak providers. Because we ran out of time. Building was slow. And when we changed our SDK the cost was immense. Totally different today, 10 years later. Today, I would’ve slop generated 100 providers (again, with transparency and cleanup later, but just to prove it out).
As an anti example, I would not PR this (without prior warning) to another project. I would not throw this onto customers without full review or transparency (as I’m already doing). I would not accept first pass slop. It’s almost never right.
Slop is a tool. And like anything else it’s not blanket bad or good. The context is everything.
@RumpkeNews Actually this response does not apply. Each time, my trash was the only trash on the street leftover each of the 3 times this year. Monday pickup skipped, it's now Wednesday and still sitting on the street.
How do you like those numbers, Helldivers?💪
Through the Galactic War you’ve been crushing tyranny and spreading Managed Democracy with unrelenting firepower! Your dedication to the cause is nothing short of legendary. Keep exterminating threats, keep the bullets flying, and let’s give 'em hell!
Due to technical issues, as of May 9, all new Satisfactory players will be required to connect their Steam/Epic account to their dad's Disney+ account.
A new section on the Settings page could let you control how much RAM Edge can use, you can also choose whether this control is activated only when you are playing a game or always:
https://t.co/YiCu5igL0U
@playnewworld people would rather wait in a queue than join a different server (without their friends) and then pay $15 to transfer when servers unlock. Stop the locking...
Did you know that the backend of #MetaThreads is built with #Python 3.10?
It's running on Instagram's #Cinder fork that includes a JIT, lazy-loaded modules, pre-compiled static modules, and a bunch of other interesting tweaks against vanilla Python 3.10.
https://t.co/RiiGfQSLMJ