91–100 of 259 posts
Earlier quoted context omitted.
I'll just leave this here for you: https://datatracker.ietf.org/doc/html/rfc7231#section-5.5.2
That's a good one. Since legacy code is less likely to change than the English language, I just call it a "referer" in writing unrelated to HTTP. That way, I'm never confused. (Everyone else? Good luck.)
“Tests pass, ship it”
> Apple will offer more price points for apps. Today there are less than 100, but the company is committing to increase that to more than 500 options. I really hope they implemented this as an enum, so someone has to wade through: enum PricePoint { UNKNOWN = 0; NINTEY_NINE_CENTS = 1; ONE_DOLLAR = 2; TWENTY_DOLLARS = 3; NINETEY_EIGHT_CENTS = 4; DEPRECATED_NINETY_SEVEN_CENTS = 5; TEN_DOLLARS_PER_MONTH = 6; PORTUGAL_NAT…
Complete with spelling errors, semicolons in place of commas, shouting snake case, and unnecessary explicit numbering. Definitely enterprise-grade.
> Apple will offer more price points for apps. Today there are less than 100, but the company is committing to increase that to more than 500 options. I really hope they implemented this as an enum, so someone has to wade through: enum PricePoint { UNKNOWN = 0; NINTEY_NINE_CENTS = 1; ONE_DOLLAR = 2; TWENTY_DOLLARS = 3; NINETEY_EIGHT_CENTS = 4; DEPRECATED_NINETY_SEVEN_CENTS = 5; TEN_DOLLARS_PER_MONTH = 6; PORTUGAL_NAT…
Complete with spelling errors, semicolons in place of commas, shouting snake case, and unnecessary explicit numbering. Definitely enterprise-grade.
Earlier quoted context omitted.
That's a good one. Since legacy code is less likely to change than the English language, I just call it a "referer" in writing unrelated to HTTP. That way, I'm never confused. (Everyone else? Good luck.)
I once saw this implemented as a regex. Unfortunately the regex was refer*er. “Tests pass, ship it”
Earlier quoted context omitted.
That's a good one. Since legacy code is less likely to change than the English language, I just call it a "referer" in writing unrelated to HTTP. That way, I'm never confused. (Everyone else? Good luck.)
I once saw this implemented as a regex. Unfortunately the regex was refer*er. “Tests pass, ship it”
Earlier quoted context omitted.
That's a good one. Since legacy code is less likely to change than the English language, I just call it a "referer" in writing unrelated to HTTP. That way, I'm never confused. (Everyone else? Good luck.)
I once saw this implemented as a regex. Unfortunately the regex was refer*er. “Tests pass, ship it”
Earlier quoted context omitted.
Lol, few things trigger my OCD more than misspelled words in identifiers. I legit missed important use case while amending legacy system just because someone decided to have “priveleges” in the variable name. I hope all those ways to spell number 90 are part of the joke.
The key is to write out the enums to long-term storage as the names instead of the numbers, that way nobody can ever fix your spelling mistakes.
Earlier quoted context omitted.
Lol, few things trigger my OCD more than misspelled words in identifiers. I legit missed important use case while amending legacy system just because someone decided to have “priveleges” in the variable name. I hope all those ways to spell number 90 are part of the joke.
The key is to write out the enums to long-term storage as the names instead of the numbers, that way nobody can ever fix your spelling mistakes.
Earlier quoted context omitted.
Developers are also not allowed to link to account management on a webpage if they signed up via a website, which contributes to lots of user confusion when it comes to cancellation of a subscription for instance.
I think this is exactly what is being changed here? Now you can link away to a web portal with your account and alternative payment options. Correct me if I'm wrong.
This is the only statement that might be construed as such from the article, but it doesn't say anything about management, and I'm really not sure what consent means - is it a popup that says "do you want to be informed about non-apple payment methods?". Maybe it is what is being changed, but I can't really tell.
I can say that customer confusion is often built into app store policies, and the amount of backend and customer service work to clean up users who sign up with multiple payment methods accidently is not a trivial cost.
Earlier quoted context omitted.
Lol, few things trigger my OCD more than misspelled words in identifiers. I legit missed important use case while amending legacy system just because someone decided to have “priveleges” in the variable name. I hope all those ways to spell number 90 are part of the joke.
I'll just leave this here for you: https://datatracker.ietf.org/doc/html/rfc7231#section-5.5.2
Unicode sidestepped the issue by naming the characters RIGHT/LEFT-POINTING DOUBLE ANGLE QUOTATION MARK.