writing code != building things.
In my org, seniors spend a lot less time building things: writing components, etc. They do spend a lot of time navigating office politics. But they are engineering specific office politics: how does system A interact with system B? What are the architectural implications? Ownership of long term data and technical and business strategies?
The "art" of negotiation can be ass-kissing but quite often genuinely with the goal to advance the projects they own and the enablement of the "people who actually build things", which at some point also involves the seniors. You need to build raport and relationships to negotiate seriously.
So, I guess you could have some sort of escrow third party that isn't Crowdstrike or MS to do this "audit"?
Or see this for a much better write up: https://stratechery.com/2024/crashes-and-competition/
In 2024, tax software ought not to have the tax rules hardcoded, but instead ask the tax authority for a fresh set of rules at startup every time, and alert the user if the rules database ever gets more than 30 days out of date.
Nearly every government makes tax rule changes every year - it just isn't reasonable to hardcode them and require the user buy/install new software every year.
The changes go beyond tax band thresholds and percentages across NIC & IT. Eg the (now-scrapped) Health & Social Care Levy would've been a completely new tax - you need a complex schema to encode that and even then the Treasury will come up with something you haven't thought of next.
Meanwhile, in the 2010s they expanded Haneda and started accepting international flights, and you can get to Tokyo via a variety of normal trains (and buses if your destination is on the Shinjuku side of things) in 15 minutes.
The whole thing is landfill, so no residents to be mad either.
Last time I flew to Haneda they made all the flights from the US arrive and depart at times when public transportation wasn't running, to discourage those flights, but it seems like they stopped doing that. So now it's more convenient for everyone, and Narita is largely pointless for everyone that isn't an extreme budget traveler (but I think Haneda built Terminal 3 for that use case... so... is there any reason for Narita to exist if you aren't visiting Chiba?)
Examples for what that means given by the EU itself [1] include "cookies that allow web shops to hold your items in your cart while you are shopping".
And on the policing - there are a lot of laws that cannot be "policed". It requires trust, goodwill, collaboration and savy users to report violations to the webmaster or relevant ICO.
I’ve often wondered why no one has come up with a new product in this space. I think the long term demise of Flash has put off anyone even trying.
There are so many great uses for animations on the web, even if we don’t need full blown user interfaces of them and intro screens like we did back in 2002.
Great job!
And what people always fail to mention when it comes to supersonic flights is one of the main issue is neither a technological nor an economical one nor a supersonic boom one.
Traveling west bound is great: you leave in the morning and you arrive, local time, before the local time of your origin point. But traveling east bound isn't that great: you still have to leave in the morning and you land in the evening, so the only thing you gained is a shorter flight time but not a full day of work or shopping or what not.
So on regular flights (because Concorde was profitable, at least on the French side, thanks to charter flights), people would fly Concorde to go to NYC and fly back on a red eye...
As someone who worked for and flew on Concorde, I think what they're doing is amazingly cool though and I hope they succeed. But I'm still unsure what the long term plan is...