Kadin
Beanplate enthusiast and crouton-petter.
Everyone involved is listed at the end with their job title.
There's a lot of what might be called "politics" involved in that too, although much been codified over decades (particularly due to unions). Whether or not someone gets listed in the front vs. end credits, in what order, and what they're listed as, is a big deal and can be subject to some fairly intense negotiations.
Some of the titles, e.g. "Associate Producer", "Best Boy", do not necessarily mean what I suspect viewers unfamiliar with the industry think they mean, too.
It is a bit surprising, given that print journalism is not a new industry, that it doesn't have very well-codified rules as well. Maybe that's because of the lack of an overarching union to push for uniformity?
Welp, so much for #Github #Copilot Pro — it was a pretty good deal at $100/year, and the billing based on prompts made more sense to me than billing based on "tokens".
Just to ensure anyone who wants to ride out their annual plan gets thoroughly screwed, they're doing away with the "0x" (free, mostly older) models and increasing the multipliers on the remaining ones. Nice touch.
Quite the #enshittification speedrun. Bravo, guys.
Dominos Pizza apparently DDOSed their own website to death with their NFL Draft promotion.
How do you think they apportion the blame between the Marketing department and the IT department?
@CrabbyIT@infosec.exchange I am not normally a fan of developing in virtual environments but this strikes me as a potentially valid use case.
Discourage running LLM tools directly on developers' real hardware; instead, have a template VM that you can spin up, with all the tools pre-installed (make it easy and low-friction!), and then sandbox those virtual workstations at L2 (VLAN) / L3 (subnet) on the network.
I am not sure if I would trust purpose-built LLM sandboxing tools currently, and LiteLLM in particular concentrates valuable API keys in a way that seems risky. I'd want per-user API keys, I think.
The controls come at the border between the LLM workstation network and the broader corporate network, with firewalls and reverse proxies to control hits to internal APIs and other resources.
Basically, they are locked in a dev/sandbox network and code gets promoted "out" via a PR process with human review before it can touch actual production systems.