941 karma · joined July 3, 2017
I know this probably isn't the most ideal place to post this, but I've seen a few sellers around here, so I thought why not!
The suspension was for "suspicious billing activity", tried appealing twice with the correct billing address, and was told the suspension is final (some automated email) both times.
They won't take my calls because the account is suspended, which leaves me not being able to advertise on the #1 service to do so.
It's completely unacceptable, especially for a business in their position. One tiny mistake leads you to a lifetime of suspension to a service vital to almost any business.
All trades would be looked at by an actual human, making sure that everything made sense and lined up.
I have my own doubts about a purely algorithmic approach (for now at least). Computers are great for many tasks, but for something as inherently irrational as the markets I think that should be at least partially moderated by a person with a deep understanding of the markets.
I sell on FBA and recently had to create new listings that force the Amazon barcode instead of the manufacturers, which is where the commingling happens.
I’m sure this isn’t all products (large brands are probably still using manufacturing barcodes), but it should help nonetheless.
52% US 5.2% UK 4.7% India 4% Japan 3.4% Canada
The incentives on the business’ side are nowhere near aligned with my side as a user.
Additionally, in no way am I advocating for no comments, that's obviously not possible (like your example). Comments are useful, even necessary, for code that might have an otherwise confusing logic to them.
I've seen plenty of code with documentation for a method with nothing more than:
/**
* Bills the user
*
* @param user The user to bill
*/
public void billUser(User user) {
//
}
In my opinion, that comment is completely redundant, and I think it's driven by the idea that we should comment EVERYTHING.I just meant simple to understand variable, function, and class names. That combined with small classes and functions, makes following the logic of your program extremely easy.
Following concepts like DRY (don't repeat yourself) and the single responsibility principle ensure that you're making more easily testable code, and I'm sure less overall LOC.
There’s nothing worse than going back to a codebase from a year ago and seeing a couple magic numbers and having no clue how they came to be, haha.
And if your code is clean, you shouldn’t have a bunch of redundant comments explaining the obvious.
They also have settings depending on password requirements (no special characters, etc.).
I'm unsure what the URL really has to do with it, you could just generate a new password for the new URL and change it.