yipinwong

Great to implement a DB just like human memory, unstable, and untrustworthy.

Online queues just is to enforce backpressure in the downstream.

I never heard of "AirDosh" so if implementing the alternative mentione in the doc is worth their effort for ROI.

Not as customer forced but trade-off should be made based on their resource availability

That's where my analogy breaks as all of them do.

My point is that @pluc comments suggests too specific and I wanted that his examples break down in different levels of expertise.

Nothing I mentioned deals with disposability of engineers.

Agree up to certain levels but your examples are too specifc.

Understanding should come in different levels abstraction of what you are building,and managing.

There are different levels SREs, from beginner to say Fellow level.

Do you expect the Fellow level to understand nitty gritty details of each component his apps or services are interacting with and how each of them start? No. Especially when they have to deal with hundres or thousands of services each of them hosted by different teams, orgs, or different companies.

junior SREs, yeah probably got their hands dirty with those nitty gritty details you listed because they tend to deal with smaller or lower levels of components

So my point is, I agree withyour "Understanding" but not specific details as they differ per one's level of experience

I was promoting Google models (more like Google ecosystem) for what Google was doing with their models. Making it accessible to non-technical people (which is what I am doing).

e.g. NotebookLLM was one that got me interested in Google's ecosystem. It was easy to use and explain even to my parents.

Now, their models (and NoteBookLLM merging to Gemini, making it extremely hard for non-tech people and other stuff) release very slowly, their models lie their ass off, very politically skewed, etc.

Not to mention blocking API usage with subs.

I never use any google models for any agent work any more, in case they block me.

Started migrating gdrive, and gmail to other providers at this point after horror stories in HN, that they lost access to their gmails, etc.

gemini.google.com (Pro plan).

AGY never even update often, and only has gemini 3.8 flash (for Google model).

Doesn't mean jack without access to it.

I used to defend Google's models months ago, but switched to Luna for less intelligent models.

But with this bs of not making it even public, pushing off release of newer models late, I lost faith in Google.

Mine showed up after clearing cache for some reason.

I do not agree.

As an example, Linux distros say, Ubuntu got its project "names" as well as SEMVERs. But people rarely use project names but uses versions.

You tell me, I use "Jammy Jellyfish". I will be like WTF dood. You tell me 22.04 LT (which is one I use), oh yeah, that's a good one.

Same thing here. companies can call whatever SOTA whatever they want. But in the end people will refer to them as just Gemini 4 or Ultr/Pro/Lite however people like to use.

Just leave it to company's discretion. Don't enforce anything. People will figure out how to call it.

---

And wtf, a peaseant?

I use your so-stupidly-called ultra/med/lite but in diff situations, and when I use lite that doesn't mean I am peasant, I am being sensible

It was great to use during college years.

I regret ever using X/Emacs for 5 years with two reasons.

The biggest reason is, I have arthritis on my left pinky thanks to Emacs. Now I need to use an expensive ergo keyboards (thumb for ctrls)

The second reason being, vi is what I am forced to use for many linux default editors. I never learned it, and always look up google for commands.

(optionally, extending Emacs is pain as I never understood the point of lisp).

The prompts build impressive clips.

I am more interested in how to make consistent "participants" and "environment" with multiple clips so they look like one longer clip.

Will that require same dev/coding harness and spec-kit-like engineering flow?

Like create a spec on how a movie will look like, feed contexts, create tasks so that multiple clips look congruent?