In essence:
Logs mark some event in the system.
Metrics model some measurable, quantifiable state.
In high volume systems both can then be observed through various sampling techniques. A key item is that sampling is good to handle separately to application logic creating those signals as it may change over time or be dynamic.
> The moment of capturing a measurement is known as a metric event
Which suspiciously reads like a log.
In practice, a metric is an aggregate of events (the "metric events") when you're not interested in the individual event but, but in the aggregate itself. For practical reasons this is not implemented with logs but with more primitive technical events emission.
This is not fundamentally incompatible notions. If you do an electrocardiogram, you might be interested in your BPM, but it is deduced by the full log of each beat. The segregation we do in computing is more practical than fundamental.
I would like to know what this measures exactly.
The reason I often prefer writing to talking is because writing lets me the time to pause and think. In those cases the bottleneck is very clearly my thought process (which, at least consciously, doesn't appear to me as "words").
How is that not worse or at least equivalent to a back door?
The product is ChatGPT, actually.
If LLMs are a bubble, then you should expect most of OpenAI's revenue to come from its API (which is used by startups which have raised money to do "magic AI stuff", and the bubble would pop when investors would stop giving the money). But according to https://futuresearch.ai/openai-revenue-report, revenue from the API accounts only for 15%, the other 85% being the different subscriptions offers, including 55% of ChatGTP Plus subscriptions -- that is, _direct consumers_.
This doesn't prove that it isn't a bubble (the consumers could realize it's useless and then leave some time later), but it makes it less likely IMO.
Most of my colleagues finish their intakes very quickly, finish projects early and most (not all) have a huge amount of time of aftersales and aftercare. They usually call this aftercare 'out of scope'.
My finished projects usually do not have any aftercare. They work, because i invested a lot of time in the beginning. I call this 'the actual scope'.
I've been fixing some of my colleagues projects recently. Some of these projects should have ended 18 months ago... Most take be about two weeks to fix.
They eventually will learn :)
The reason it ended is because the general public doesn't care.
How garbage the web has become for a low-latency click action being qualified as "impossibly fast". This is ridiculous.