It reads like any of those tech blogs, using big words where not strictly necessary but also not wrong

Don't know about your LLM feeling

It contains the word "delve", a word that got way more popular in use since the introduction of LLMs.

Also this paragraph sounds a lot like it has been written by LLMs, it's over-expressive:

    We systematically advanced through each tier, commencing from tier 5 and descending to tier 0. At every tier, we organized the clusters into manageable batches, ensuring a systematic and controlled transition process. Before embarking on each stage of the version upgrade, we actively involved the on-call teams responsible for each cluster, fostering collaboration and ensuring comprehensive oversight.

The paragraph uses "commencing from" together with "descending to". People would probably write something like "starting with". It shows how the LLM has no spatial understanding: tier 0 is not below or above tier 5, especially as the text has not introduced any such spatial ordering previously. And it gets worse: there is no prior mention of the word "tier" in the blog post. The earlier text speaks of stages, and lists 5 steps (without giving them any name, but the standard term is more like "step" instead of "tier").

There is more signs like "embark", or that specific use of "fostering collaboration" which goes beyond corporate-speak, it also sounds a lot like what an LLM would say. Apparently "safeguard" is also a word LLMs write very often.

It doesn't get much better if you translate that paragraph from corpo speak to normal language: "We did the upgrade step by step. We did each step in batches. After we already decided how we were going to upgrade the clusters but before actually doing it we asked the teams responsible for keeping the clusters running for their opinion. This helped create an environment where we work together and helped monitoring the process"

I'm sure there are people who write like that. LLMs have to get it from somewhere. But that part especially is mostly empty phrases, and the meaning that is there isn't all that flattering

People write like that to sound good to higher-ups who don't understand what's going on underneath.

There's A LOT of that kind of content to learn from. A brief glance at LinkedIn is all you need.

Relevant pg thread on twitter: https://x.com/paulg/status/1777030573220933716

This [1] is a good piece on it. Here's [2] anorher good one.

We don't just carry out a MySQL upgrade, oh no. We embark on a significant journey. We don't have reasons, but compelling factors. And then, we use compelling again soon after when describing how "MySQL v8.0 offered a compelling proposition with its promise of substantial performance enhancements", just as any human meatbag would.

[1] https://www.latimes.com/socal/daily-pilot/opinion/story/2024...

[2] https://english.elpais.com/science-tech/2024-04-25/excessive...

If the meatbag was a salesperson though… very believable! ;)

Nah this isn't a big word salad issue. The content is fine. It's just clearly a text written by humans and then rewritten by an LLM, potentially due to the original author(s) not being native speakers. If you feel it's natural English that's fine too ;)

I always thought 90% of what management wrote/said could be replaced by a RNN, and nowadays LLMs do even better!

Isn't that the same of how you select multiple files in most file managers?

Shift+Click: select from currently selected item to clicked item

Ctrl+Click: add/remove clicked item to set of selected items

Sure, but the idea you can share multiple windows this way.

Can Google Meet (or hangout or w/e they call it now adays) do some of this?

I don't see a foot gun, you just need to check if you have consumed the whole input. Which is the norm in nearly any streaming api

I didn't see a foot gun either, but somehow my foot went missing.

I get that this is a super low level API, but yet, my expectation about an API that parses a buffer with length to a number and which has a specific enum for error cases as its return type would be that when asked to parse "9not a number" that I would get an error response and not a "the number you asked me to parse is 9 and everything went well" as the result.

The whole reason for returning a result enum would be so I don't forget to also check somewhere else whether something could possibly have gone wrong.

Especially when there is a specific result type.

But now you need a different API to compute where a number starts and end and that API must use exactly the same definition of number.

There could be an enum value for "read a partial number"

In what way is it streaming? It takes at least the entire numeric string as a string in memory, you can't stream in more data as needed