I worked for a small company that did work for a cross-border manufacturer. Coming from Canada, we were told explicitly that "meetings" was a perfectly good reason for a day trip, and we were never there "to work". US customs has been historically as humourless a bunch as ever existed, and the factory on the other side was unionised, so meetings it is.
What cracked me up was driving back late one evening, arriving back at the Canadian side. The agent asked where I'd been, and I mentioned the town just behind me.
I think the issue here is one of informed consent. You might say, "OK, this makes sense" when agreeing to location data for a weather app. In the context of whether it's going to hail soon, location is reasonable. What you only see in those GDPR-type banners is that the data is being re-sold off to 1001 "partners", none of whom are important for my hail-to-head concerns. Never mind all the cases where it's re-sold on to all the governments and personal-level creeps through aggregators.
On the other hand, the morels that seemed to come with a load of wood chips were great for the year or two we had them.
I tried growing a little wine cap bed once, and it hadn't gone well. Perhaps it was the chickens pecking at it, can't say. I do still get wine caps on occasion, but they have migrated to more far-flung parts of the yard.
> the morels that seemed to come with a load of wood chips were great for the year or two we had them.
You probably already know this, but for anyone reading, there’s a species of mushrooms that looks kind of like morels that is poisonous, potentially fatally so.
Along with all the general discussion, I found the concept of defensive parsing striking a chord when reading this as well: "The Seven Turrets of Babel: A Taxonomy of LangSec Errors and How to Expunge Them", https://langsec.org/papers/langsec-cwes-secdev2016.pdf
I'd love for these ideas to take hold at work, but I'm on the fringes in infosec, not a dev.
Back in the stone age, I worked at 7-Eleven while in university. Nothing was really computerized at the store level then, even cameras were rare.
What was done all the time was a simple, templated, paper-based process that managers went through each month. I believe the gist of it was that it recorded sales for each shift in the month (7am-3pm, 3-11, 11-7), and who worked them. Some simple stats highlighted low sales correlated with employees, to point out who was likely entering smaller prices in the till and pocketing the difference. Now it's all bar-code scans of course, but it was a common problem at the time.
Well, or they could release a patch that simply nerfs the license check on the binary. No risk in terms of lost profits, for software they no longer sell.
That assumes the (a) the source is still available (b) the build environment is still available and working, (c) a staff member is still available that understands the system and/or (d) the time to figure it out and rebuild, test, and create the binary diff/patch ....
Well, yeah. The point was that there are changes that could be made, without having to make it possible for everyone else to build, that would enable continued binary support.
What cracked me up was driving back late one evening, arriving back at the Canadian side. The agent asked where I'd been, and I mentioned the town just behind me.
"Oh, _meetings_, eh?" wink
reply