I'm pretty sure that this sort of thing happens for stuff in big box home improvement stores like Home Depot and Lowe's, too. Things like plumbing fixtures that appear to be identical to counterparts in smaller stores will have off-by-one or suffixed product numbers, and are made with cheaper plastic internal parts than when purchased elsewhere.
I wonder if the author considered moving payment processing to Adyen from Stripe? They're also EU-based and a bit more... well known? I liked integrating with them in the past.
IMO one of the cool things about Wallet is the notification that appears on the homescreen when you're in proximity of the venue or time of the event and automatically displays the pass when tapped. I wonder if "create your own" will be able to do that (I'm not sure how it would)?
I said this elsewhere in the comments, but I think there's sort of a fundamental tension that shows up sometimes between DRY and "a function/class should only do one thing." E.g., there might be two places in your code that do almost identical things, so there's a temptation to say "I know! I'll make a common function, I'll just need to add a flag/extra argument..." and if you keep doing that you end up with messy "DRY" functions with tons of conditional logic that tries to do too much.
Yeah there are ways to avoid this and you need to strike balances, but sometimes you have to be careful and resist the temptation to DRY everything up 'cuz you might just make it brittler (pun intended).
I think there is often tension between DRY and "thing should do only one thing." E.g., I've found myself guilty of DRYing up a function, but the use is slightly different in a couple places, so... I know, I'll just add a flag/additional function argument. And you keep doing that and soon you have a messed up function with lots of conditional logic.
The key is to avoid the temptation to DRY when things are only slightly different and find a balance between reuse and "one function/class should only do one thing."
Yeah - I think it still a bit of a deterrent ... today, not everyone has a camera, and if I were a thief and one house had cameras while the place next door did not, guess which one I'm gonna rob?
But I wonder how much of that will wear off once everybody has one.
I understand your skepticism 100%, but I suspect you might change your mind if you, say, rented a car with it for a week. It's definitely a net positive for safety, and it probably costs the auto maker less than the seat belts (literally).
this is a great analogy despite it possibly coming off as snark.
I think it's hard for some people to grasp that programmers are motivated by different things. Some are motivated by shipping products to users, others are motivated to make code that's a giant elegant cathedral, still others love glorious hacks to bend the machine into doing things it was never really intended to do. And I'm sure I'm missing a few other categories.
I think the "AI ain't so bad" crowd are the ones who get the most satisfaction out of shipping product to users as quickly as possible, and that's totally fine. But I really wish they'd allow those of us who don't fall into that category to grieve just a little bit. This future isn't what I signed up for.
It's one thing to design a garden and admire the results, but some people get into their "zen happy place" by pulling up weeds.
Oh my god. This is me. If I were any better at writing, I could have written this, the author is even the same age as me (well, a year younger) and followed a similar trajectory. And a lot of what I've been feeling lately feels similar to burnout (in fact I've been calling it that), but it really isn't burnout. It's... this, whatever this is... a "fallow period" is a good term.
And I feel like an old man grumbling about things changing, but... it's not the same. I started programming in BASIC on my Tandy 1000 and went to college and learned how to build ISA cards with handwritten oscilloscope software in the Computer Engineering lab. My first job was writing firmware. I've climbed so far up the abstraction chain over a thirty year career and I guess I don't feel the same energy from writing software that first got me into this, and it's getting harder to force myself to press on.
I think (I'm an American so take with a grain of salt) even the "proper lawyer reviewing terms" part can be deferred quite a while by being conservative with PII (which you should be doing anyway) and using a service like iubenda to deal with terms and cookie warnings when you first start out.
I didn't do this, but I did use a spare unsigned short (used for memory alignment) in the Quantum Atlas 10K II disk drive's servo firmware to store my wife and I's anniversary date just for yucks. :P
It used to be the case that the middle digit of an area code had to be a 0 or a 1. All the O.G. "cool" area codes like 212 are in this format, and the less desirable new area codes like 646 are not (yes, this is an accidental Seinfeld reference).