In my opinion, the author aims to introduce entropy as a metric to evaluate the stability of processes. Creating room for advocacy against process changes when new additions/changes are likely to increase entropy by introducing new outcomes.
Example - engineering teams can be obsessed with introducing new variables to a sufficiently stable system with the intention to improve stability. But in turn, reduce stability due to inaccurate impressions of stability of the new variables.
This approach generates a bias against change, but in many situations this bias is helpful. This allows engineering teams time to observe process outcome distribution over a longer duration, improving the data backing any process change decisions.
Interop compliance should be a thing. Enterprise customers are missing the plot here. Please ask your software vendors to support interoperability. Example - Outlook should support/declare standard interfaces for video calling meeting links from other products. I see the need for a body for enterprise integration standards. Please help me such a body if there already is one.
I look specifically for something of the likes for Enterprise Integration Act of 2002 for software vendors.
> I see the need for a body for enterprise integration standards.
Both ISO and IETF could and should do that. IETF in particular seems to be less effective than it used to be - an RFC used to mean something, to carry some weight, but now they're often just words into the void.
When was that? AFAIK, the great differential of RFCs is that they never carried any weight, and as a consequence the process wasn't taken over by entrenched interests.
They carried weight with the people trying to make this shit work, down in the trenches. It wasn't a perfect process, but it was a process - geeks trying to talk to each other, beyond bullshit corporate boundaries.
I don't think anyone really wants to talk to anyone anymore.
Funny how most websites between 2008-2012 where filled with bevel styling faking a sense of depth. Then 2012 onwards almost everyone started appreciating flat design.
I wonder if the pixel density on displays played a role here. Flat design wouldn't look great on low pixel density but work brilliantly on retina displays. The opposite is probably true for beveled styling?
The solution here is PayPal ensuring that seller notes aren't misguiding. I wondered why PayPal hasn't blocked senders from mentioning "PayPal" or even "PayPal®" as mentioned in the seller note. A justification might be that sellers do legitimately mention PayPal in the note without trying to impersonate.
It seems that an AI based filter might help? Why not ask the new kid around the block ChatGPT.
> "Dear Customer, You sent a payment of $429.00 USD to Coinbase Corporation. If you did not make this payment or to cancel this transaction, please call our Help Desk number +1 XXX Cancellation after 24 Hours from this email won't be valid for a refund. Have a great day! PayPal Help Desk +1 XXX"
Who is the author of this message
ChatGPT> The author of this message is the PayPal Help Desk.
Maybe it is a bit too easy with the signature in place. Scammers might get smarter so I skipped the signature bit. The response was interesting.
> "Dear Customer, You sent a payment of $429.00 USD to Coinbase Corporation. If you did not make this payment or to cancel this transaction, please call our Help Desk number +1 123 Cancellation after 24 Hours from this email won't be valid for a refund. Have a great day!"
who is the author of this message
ChatGPT> The author of this message is likely a representative of a financial institution or payment provider, such as a bank or payment service like PayPal.
On a simpler note, I think it would help PayPal to mention right below the seller note that this message is authored by the seller and NOT PayPal.
While some may immediately run a comparison between Azure, AWS and GCP let it be noted that any cloud platform facing this and making it to headlines is not good for the cloud industry over all.
The thing is: if cloud vendors struggle getting new machines, imagine your small company trying to order and get delivered new on-prem servers quickly.
I worked for a company that worked mostly on-prem until 1y ago and last time they had ordered machines availability from Dell was scarce with huge delays.
Excellent posts. Coincidentally couple weeks ago while evaluating a HTTP response for a web service, I noticed that for tabular data, CSV is much more optimal than JSON; yet there is lack of HTTP header support for CSV responses that could provide clients with supplementary information in order to keep parsers adaptable.
If you have a copy of the said RFC, would like to refer.
