Shudders
The post triggered PTSD and I want to go home and cry. You created your double entry, cool, now let's split it (because of million reasons) and add taxes. So now we deal with a basic 25 line document where some lines are doing nothing but move funds through certain tax accounts. Oh, no, there is a typo, but we cannot just create the reversal because for some accounts, the transaction should stay reflected in turnovers, for some it should not and for most it depends on fiscal period and stuff.
Don't forget that everything varies between countries. With all that let's create a financial statement for eg Walmart (who has every line item sold posted to SAP system when you buy things at store)
The state of "open Wi-Fi" security is actually really sad. I'm not aware of an easy way for the airline to actually do better than this!
I suppose they could use Opportunistic Wireless Encryption [1] and bind session authentication to that (i.e. authenticate a given OWE session, not a given MAC address) if the device supports it, as at least modern Apple devices do? But I have no idea how stable an OWE session is; it would be very inconvenient to have to login again every time my device switches between access points.
In any case, I'm sad that this isn't a solved problem yet, and paid Wi-Fi (as well as securing free Wi-Fi) still requires custom and clunky solutions like unreliable captive portals that need to pass through selective traffic (e.g. for 3DS, for payments, sometimes emails for password reset codes etc and more).
A standardized endpoint and API would also be nice, i.e. something to tell the client whether it's connected, restricted (i.e. able to only access a limited set of hosts such as the in-flight map as described in the article), or needs to pay/authenticate (and if so, at which URL). This could then yield an authentication token, to be provided for seamless reconnections for the same session.
There's "Hotspot 2.0" and WPA-EAP (i.e. WPA Enterprise), but these don't really have a good story for "pay via web portal" style usages and are more geared towards wireless carrier operated hotspot networks and corporate scenarios, respectively.
[1] https://en.wikipedia.org/wiki/Opportunistic_Wireless_Encrypt...
PS: I'm a couch expert so I have no idea if there's a problem with this idea.
I used to work for a bank and the policy is no comments unless absolutely necessary, because comments become out of date. Doxygen is the only real comments allowed.
When I worked at SAP where VCS for ABAP is ancient and has no analogue for git blame we had a practice of putting a SAP Note next to every code change, since some of the things that we had to implement are dictated by business/legislation, so you need a proper explanation from time to time. Without it, the code becomes unmaintainable.
Your password must include a number.
Your password must include an uppercase letter.
Your password must include a special character.
The digits in your password must add up to 25.
Your password must include a month of the year.
Your password must include a roman numeral.
Your password must include one of our sponsors:
The roman numerals in your password should multiply to 35.
Your password must include this CAPTCHA:
Your password must include today's Wordle answer.
Your password must include a two letter symbol from the periodic table.
Your password must include the current phase of the moon as an emoji.
Your password must include the name of this country.
Your password must include a leap year.
Your password must include the best move in algebraic chess notation. (picture of chess puzzle)
← This is my chicken Paul. He hasn't hatched yet, please put him in your password and keep him safe.
The elements in your password must have atomic numbers that add up to 200.
All the vowels in your password must be bolded.
Oh no! Your password is on fire. Quick, put it out!
Your password is not strong enough
Your password must contain one of the following affirmations:
Paul has hatched! Please don't forget to feed him, he eats three every minute.
A sacrifice must be made. Pick 2 letters that you will no longer be able to use.
Your password must contain twice as many italic characters as bold.
At least 30% of your password must be in the Wingdings font.
Your password must include this color in hex.
All roman numerals must be in Times New Roman.
The font size of every digit must be equal to its square.
Every instance of the same letter must have a different font size.
Your password must include the length of your password.
The length of your password must be a prime number.
Uhhh let's skip this one.
Your password must include the current time.
Is this your final password?
Their inability to produce anything useful with Copilot is the largest example of this, but there are others. They are getting lapped by a ~300 person software company in the race to consumer-ize an x86 PC a into turnkey gaming platform, even with $100 billion in game studios and owning the API that every major game is developed against. Their footprint in education is gone, completely replaced by Google who not only produced an operating system that could be effectively run and managed on commodity hardware, but also developed the centralized functions for school administrations to use to manage classrooms at scale.
The consumer situation for Microsoft right now might be even worse than it was when Nadella took over.