It's precisely the "this is the way it's done" approach you mention, which means they now have to pay a human to do the work their web stack ought to do!
It's not "this is the way it's done", it's "this is how it should be done". Shipping information is much like the rest of the order information, you want a de-normalized price on the order and each line item in the database, not a normalized cost based on the price of things now. You want a denormalised record of which card was charged, not a normalized record showing what their current card is, etc.
I get little bursts of joy about 3-5 times per week when I see some low-effort misinformed comments, followed by that brain urge to set the record straight, followed immediately by discovering the fact that someone with specific domain knowledge, experience, or both has taken the time to write a thoughtful reply like this one, educating everyone who reads it.
This isn’t an isolated case: as I mentioned, I see it at least a few times per week and I imagine this happens at least a dozen times a day here in some thread or other.
Storytime: As part of moving to another city, I put a chest freezer on an auction platform, specifying that it must be picked up from my location. While that auction ran its course, I minded offline and online services and updated my address to the new address so that letters would already arrive at my new location. Now came the day where somebody would come pick up the freezer. Which address do you think did the auction platform give them where it could be picked up?
Well the Librem 5 is not another 'widget in a warehouse'. It was always going to be a long wait to delivery, due to the enormity of the undertaking. This was not a surprise to anyone. Addresses will need to be updated after order in this case! Every implementation is different.
Precisely! So picture some, however oversimplified, code which
searches a customer's orders,
determines which is a phone product id, remembering they sell other stuff which we would not want to update in flight order details on,
then updates the embedded customer address on the order.
I would like to hear some original thoughts on why this is so difficult that a human is doing this work instead.
Obviously maintaining a different behaviour for a class of product ids is painful and not beautiful code to look at, but it is the real world.
flukus|5 years ago
sneak|5 years ago
This isn’t an isolated case: as I mentioned, I see it at least a few times per week and I imagine this happens at least a dozen times a day here in some thread or other.
Thanks for being awesome flukus. I love HN.
lolc|5 years ago
shermanmccoy|5 years ago
Aeolun|5 years ago
shermanmccoy|5 years ago
I would like to hear some original thoughts on why this is so difficult that a human is doing this work instead.
Obviously maintaining a different behaviour for a class of product ids is painful and not beautiful code to look at, but it is the real world.