2 ms·
I mean, OK, yes, regulation costs money. So? "It costs money" is not, in and of itself, a reason not to do something.
by emodendroket 11y ago
I mean, OK, yes, regulation costs money. So? "It costs money" is not, in and of itself, a reason not to do something.
- AnimalMuppet 11y agoWell, when "things" (regulation, or taxes, or transport, or transaction costs, or whatever) cost less, then more things become economically viable, so more things happen. That is, the overall economy grows. We've had a stagnant economy for the last 6 years (at least). It is my impression that we have also had an increasing burden of regulation in that time. Are they related? I can't prove it, but I suspect yes, at least to some degree.
- emodendroket 11y agoAnd what is that impression based on?
- AnimalMuppet 11y agoIt's primarily based on working in business. But it's hard for me to tell if the regulations are becoming more burdensome, or if I'm just becoming more aware of them as my role becomes more senior. It's also somewhat based on my perception of how many regulatory hoops I'd have to jump through to start a business. Again, though, I don't know if the hoops were always there and my awareness of them grew, or if the number of hoops increased.
- jameshart 11y agoBut when regulations are absent, amon the things that happen, more bad things happen. So if removing regulation increase the amount (or value) of things that happen, but it also increases the cost of the things that happen, then - depending on the balance of cost and value, removing that regulation may be a net negative.
- pm24601 11y agoIn this case the stagnation was caused by a lack of banking regulations. Look up Glass-Steagall Act ( http://www.nytimes.com/topic/subject/glasssteagall-act-1933 http://www.nytimes.com/topic/subject/glasssteagall-act-1933 ) The act was repealed and banks blew up the economy - the same way they did in 1929.
- curun1r 11y agoMy view of this is obviously colored by having worked as a developer, but I see the legal code as being analogous to writing source code. They both establish rules by which processes run. It's almost like source code that's being run by millions of humans rather than machines. And similarly when you write source code, adding a couple of if clauses or function calls to verify data doesn't really impose a performance penalty or make the code unreadable. But, over time, if you continue to litter your code with these small conditionals, it becomes harder and harder to reason about and the combined weight of those little changes can introduce some performance penalty. This is often referred to as technical debt and requires that the programmer delve into all of the various conditions that have been added and attempt to understand and simplify them such that the overall behavior is more or less unchanged. I see this article as not a call for reduced regulation but, instead, as a call to address our legislative debt. We need our representatives to stop simply piling on new regulations and, instead, distill everything we currently have into something that makes compliance easier without losing the spirit of the legislation. This won't be easy for many reasons, not least among them that laws don't have refactoring tools and unit tests to ensure that the simplified version maintains the existing behavior and our combative, partisan system means that refactoring our laws would introduce opportunities for partisan politics and debating over the existing behavior, but that doesn't mean we shouldn't try. Because the alternative is all the bad things listed in the article. And from my experience with technical debt, the longer it's allowed to accumulate, the harder it is to fix and the less likely people are to even attempt a fix.
- emodendroket 11y agoIt seems to me like the problem is the complexity of the laws; the author complains about enforcement/compliance issues. I don't know how you can really more efficiently ensure employers aren't cheating workers of their breaks.