I'd say damn near 20yrs. I used it quite extensively about 10yrs ago and it was an odd one then, but was very useful for the purpose we had (semantic validation of XML payloads).
It's an uninterrupted treadmill cos you just spent 3 hours extra doing seventeen other things and realise you still haven't actually "fixed the copper" or whatever the heck it was you were meant to be doing :)
I appreciate that AWS Lambda has been a win for various people but this case study doesn't really mention what they tried to do with scaling. Whilst 0 to 100k sounds good, they also had seemingly chosen just one scaling solution of a big instance - several smaller instances behind a load balancer which scale up/down would surely have served the same outcome?
Lambda has been sold on "saving costs" but what seems to be often neglected is the developer time spent re-jigging into a "serverless" model. Developer resources are far, far more expensive than mere EC2 instances.
Initially I was that way too, only took a couple weeks and a few reference templates that demonstrated the constructs to get past that and haven't done JSON since. Definitely more efficient to develop with.
Absolutely agree! Have been smashing out YAML templates for 12mths with pleasure (3yrs of JSON templates beyond that), comments are the winning proposition, allows neat sectioning of various parts.
These "company managed" pension schemes have always fascinated me and would seem ripe for corruption / raiding by the company if they're short a few $$$.
Seems like in Australia we're in a pretty good position with "superannuation" https://en.wikipedia.org/wiki/Superannuation_in_Australia being compulsory since 1992 and is typically managed by completely unrelated parties to your employer.
The payments are generally made directly by your employer into the fund of your own choosing.
The biggest thing is once you've had this contributed to YOUR account, it is YOURS (drawable from age 65) and doesn't matter what happens to the fortunes of your employer(s) in the future.