In the US, charging more for credit card is allowed. Charging more for debit card is not. If paying with a debit card you should demand the cash price.
I would guess two things. First, continued growth the percentage of sales where a card is used for payment. Approaching 100% for many businesses. Second, emergence of high interchange premium rewards cards from Mastercard and Visa. The merchants pay 3 - 3.5% on these.
Wow, 10% is way more than any interchange. So I suppose it a 10% discount because the cash goes right into the owners pocket, and is never taxed. I do wonder to what extent small business complaining about card interchange, are just small businesses complaining that business was so much better when many cash sales were never reported as revenue and never taxed.
Boomers are not a very valuable market for advertisers. The youngest boomers are 60 or older, and old people are mostly set in the products they buy and less influenced by advertising.
Card network rules in the US prohibit merchants from adding a surcharge for payment with a debit card. Most merchants are either unaware, or prefer not to care. If you are using a debit card at a business that assesses a card surcharge, point out that your card is a debit card when paying and refuse to pay the surcharge. If that does not help, there are online forms available from both Mastercard and Visa where you can submit a merchant complaint.
I have not had much experience with DB2, but given that the relational data model and normalization was invented at IBM (Codd) and IBM's implemenation of those concepts was DB2, DB2 performing poorly with a normalized data model seems strange.
My recollection was that DB2 did not support multi version concurrency control like Oracle and Postgres did. The result was a lot of lock contention with DB2 if you were not careful. MVCC was eventually added to DB2, but by then it was too late.
My initial reation was 'What is a CMS'? Naming your company or an initialism and never saying anywhere in the product description what the initials mean is not welcoming. Now I know that anyone who does not know that a CMS is a 'Content Management System' is probably not a likely customer, but you never know, and expanding the initials somewhere shold probably be possible.
I think more effort should have been made to live with 65,536 characters. My understanding is that codepoints beyond 65,536 are only used for languages that are no longer in use, and emojis. I think that adding emojis to unicode is going to be seen a big mistake. We already have enough network bandwith to just send raster graphics for images in most cases. Cluttering the unicode codespace with emojis is pointless.
This article is nearly 15 years old (2013). According to center on budget and policy priorities, the number of SSDI beneficiaries has fallen from is peak in 2014. So this article was written about a trend that peaked a year after its publication and had reversed over the past 15 years. Odd that it would be reposted today.
Seems to me that if Congress would prefer that any disputes arising from the implementation of their laws be handled by the admistrative agency charged with enforcing it, all they need to do is say so in the law. Not sure how the courts could get around that.
I think whats more harmful than unit tests are code coverage metrics for unit tests that devs feel compelled or are required to achieve. The easiest way to achieve code coverage goals for tests is to write lots of small tests that test individual methods, but test very little of the interaction between them.
I feel that the goal of unit testing should be to test the largest unit possible without requiring external dependencies. In the language of domain driven design, this means to test the domain model. If you can get extensive coverage of the domain model as a whole, system tests can be used to test the complete system.
Alas, I have seen very few software systems with high quality domain models. It is not an easy thing to achieve.
You need to spend $16,666 just to cover the $500 annual fee. That’s a lot for many people especially when many low end retailers don’t accept AmEx. As already state rewards cards are a subsidy for the rich, or at least for people who spend a lot.
They can but they generally won’t. Use of the chip on the card shifts fraud liability from merchant to issuer. Burner card numbers are for card not present transactions.
That’s not true. Java has 2 types of exceptions checked and unchecked. Checked exceptions are what this thread has been calling errors, and unchecked exceptions are what this thread has been calling exceptions. Maybe it was a mistake to call them both exceptions, but Java also has 2 types of errors.
Here is an example. Go let’s structs be passed by value or by reference. The programmer needs to decide, and that adds complexity that is largely irrelevant for modeling complex business logic. Java does not provide a choice, which keeps it simple.
In the Lost Updates section, a more straight forward solution is to use the FOR UPDATE clause in the first select statement. This locks the record and prevents concurrent updates.
Is this really a Google OAuth issue, or more failure my many service providers to properly verify the OAuth token assertions before allowing access? Seems to me the latter.
I found a chestnut tree of moderate size on my property this year, and for time thought it might be an American Chestnut. Alas I eventually concluded that it was a Chineese Chesnut. Still a nice tree, but hardly as exciting.