[braiamp]

How many companies of "size" you know of? Because that process looks HORRIBLY inefficient and only primed to extract as much money of the consumer. You just need to put it in the account screen. A big red button. Your _workflow_ is there to make excuses. If the move was the other way, you would gladly pay the cost, but because it actually hurts your "business model" then it is suddenly a problem. No buddy, I call BS on all that, and call BS on the law itself.

[claytongulick]

So, you're holding a strong opinion about something that you're completed uneducated about and have no experience with?

ANY software change in a non-hobby business goes through a change process.

One as significant as an entirely new account cancelation flow requires extensive planning, design and testing.

What if you have equipment like a set top box? What if a shipping label needs to be mailed out? What if there are state-by-state regulations that must be complied with? What if you have to issue prorated returns of prepaid subscription fees? What if different accounts have different cancelation terms because of bulk pricing? And a million other things that you have to think about, design for and test.

Of course you can solve all this. But it's certainly not "BS" that it'll take more than 24 hours.

The FTC knew this. They cheated their process to ram through a rule. But you like the rule they tried to cheat to implement, so it's ok then, I guess.

[jdlshore]

For the types of issues we’re discussing here, we’re talking about companies making more than $50mm yearly, which is about 75-100 employees. So successful small businesses and larger. I don’t have exact numbers, but this size business is very common. Most professional programmers will have seen the issues I’m talking about.

[bongodongobob]

Even a company of 100 people should have a change process. I work in infra mostly and to even shut down a VM that has already been decommissioned I have to go through a change process. You can't have a dozen IT/dev cowboys just doing things they think are fine on a whim because you have to take into account what all the other teams in the company are doing. We've got 30 people in our IT dept and change processes are absolutely crucial to not fucking things up on a regular basis.