Do what everyone else does - synthesize the abstract relations into views and limit the self-serve BI dashboard to the views that do make sense.
Users default to only seeing it from their perspective, so have alternate methods to let them see it how they think it works.
I'm aware of a product that uses time-based attendance for education, because not every day, every school, or every campus uses the same timetable quilt and often you have to be flexible (school sports carnivals, relief swaps, joint class activities, or 14-day rolling timetables for example). Doesn't mean there isn't a view that synthesizes the quilt into class-based attendance, or even just AM/PM for those users that think that way.
I liked the old Cisco where if there was a sufficiently high CVE, you could call TAC and have your long-passed (or retired but now running the home network) device get the latest security patch in that train. Better for the internet as a whole, to have patches available.
Now all the vendors hide their severe CVE fixes behind the maintenance contract. I get putting new feature branches behind the contracts, but in the meantime, it'll be their name in the news when the equipment gets exploited.
Anyone know of a good list of consumer routers to avoid, regarding lax software/firmware updates past the 12-month warranty (which is sometimes it's artificial EoL)?
The reason I run a router based on open-source, is I know it's going to get updates for years. Previously I've encountered a number of vendors that either only provide updates for their flagship models, hide behind the latest revisions of their hardware getting updates, or they just ship the occasional major update when a CVE hits the news (ie too late to provide protection).
Same. It took a couple seconds to proc that statement wasn't some kind of unique misprint or accidental slip up. Same thing happened when i first got a summary of IoT security in general.
Was a sanity saver for WSL1 with split WFH DNS with company Windows VPN client.
DNS has been a lot better with WSL2, but the config has remained in place.
It's been happening for years. Anything to limit the number of onsite visits needed because that takes a lot more time.
I know insurance brokers who have revisited a clients renewal, because Google Maps and/or the council's GIS photography shows activity or buildings counter to the client declarations.
Is it a final decision? No. It's used to prompt the client to review their coverage and amend their submitted documents. Sometimes, those amendments mean the brokers are no longer able to get coverage, and the clients go somewhere else.
