This is where I like things like Tilt. If you're deploying to a k8s cluster, it's probably a good idea to do local dev in as close to a similar environment as possible.
Bit more of an initial hurdle than "just run the docker image"; however.
I've look at Tilt and it's another abstraction for Kubernetes which rarely ends well at scale.
However, most of time, Devs don't need to develop on Kubernetes since it's just Container Runtime and Networking Layer they don't care about. They run container, they connect to HTTP endpoint to talk to other containers, they are happy. Details are left to us Ops people.
It seems contradictory to say that Tilt is an abstraction over kubernetes and say that won't work at scale, but then volunteer ops to be a layer of abstraction over kubernetes as a solution.
FWIW, Skaffold.dev is similar to Tilt, and has been working out great. "skaffold dev" on the cli or the corresponding button in the users IDE starts up a local kube cluster (minikube), the dev code in a container, any other configured containers, optionally opening a port to attach a debugger, and watches the code for changes and restarts the container with the dev code when there's changes. Developers aren't beholder to the capacity of whoever's on call on the ops team to manage the containers they need to be productive. The details of pods and CRDs and helm and ArgoCD and kubectl are abstracted away for them. They just run "skaffold dev" and edit code. Ops gets to run "skaffold render" to build and tag images, and generate the corresponding kubernetes manifest.
Ops is not a layer of abstraction over Kubernetes no more then Dev is layer of abstraction over Python. We both have different responsibilities and thinking that Ops is just missing one more library is why it goes so wrong.
Kubernetes is massive beast and I get it. It feels extremely overcomplicated for "Please for the love of all that holy, just run this container." However, trying to abstract away such complexity is like trying to use Golang with some Python to Golang cross compiler. It works until it you need some feature and then oh god, all hell breaks loose.
I have not played with scaffold either but I will say. scaffold render should not be Ops job, I find it goes best when Devs present artifact they believe is ready for production and I can slot into the system. Otherwise, the friction between Devs handing Ops what they think is possibly buildable artifact quickly becomes untenable.
Tidal is a pretty good general music app as a Spotify alternative and reportedly pays artists a lot more for plays.
I also fairly liked Qobuz, a French service, but ended up dropping it because it didn't have the kind of "just play something I like" feature that Spotify and Tidal have made pretty standard now (daily mixes, etc). I hate the laziness of it but I've gotten used to it; there are days/times I just want to listen to music of a certain mood while I'm working on something and don't want to think hard about what to put on.
The scantron forms that were in use while I was in high school had a sort of meta-data section, where students would put their name, the date, etc. One of those boxes was labeled 'key'. I always assumed it performed that function, but I never tried it to see.
Maybe the intention was to make it easier for teachers to identify a student maliciousmy marking it?
My recollection is that the "key" there allowed a teacher to give out multiple tests with questions in different orders, and then you would mark the letter for the test that you were given in that section. So test A would have questions in order 1 2 3 4 5, while B would be 2 5 4 3 1 and C would be 3 4 1 5 2. They could also change the letter of the answer, or really whatever you imagine.
Presumably it reduced people copying answers from their neighbors.
The major argument against adblockers (at least as far as I have seen) is that it deprives content creators a source of revenue. I can't disagree with this statement because it is true, it is a (read: singular) source of income that we (read: users of an adblocking program/method) are eliminating. I for one believe that they should ge something.et paid for their work, but ads just don't seem to be the right solution. I know there is paypal donations, and patreon subscriptions (or similar services) but these don't seem to draw people to contribute. I can't seem to think of any other alternatives to these, but I'm sure there must be something. Anyone have any ideas?
That people don't pay for content online is partly a social, historical, and technological problem. Crowdfunding is slowly but increasingly becoming viable, as it enters the social awareness/expectation for content creation.
Other options include government (known for relatively high-quality content in many parts of the world: for news, science, education, art, and other works that are widely considered to be a part of the common good).
But I'd like to see more of a rise in crowd-sourced "content pools" that, for example, would commission many works/creators in an ensemble centralized around broad topics (e.g. "participate in commissioning a cabal of high-quality tech blogs" if that's your fancy).
As sort of an aggregator of content or a commission based system? Or more like a business with employees that produce content, such as columnists / reporters for a newspaper?
I think content is becoming cheaper to create, but there will always be business models for high-end publishers other than advertising. (Like many other forms of art)
Bit more of an initial hurdle than "just run the docker image"; however.