Except that at least two of these resulted in Comcast and then Verizon suing and getting to continue doing each of them because the courts said they couldn't regulate against those practices unless they became Common Carriers.
Yeah the way to write better code is to write better code. I happen to find TDD a useful tool in that but doing things badly is still possible.
Someone mentioned DI not getting rid of coupling and I agree. DI is a tool you might use but the way to get rid of coupling is not one simple thing but a process of a bunch of different tools and techniques. You can't just slavishly fallow some process and expect it to fix all your issues. You have to think and do work yourself to fix it.
That is not at all the assumption. The assumption is that you have some idea what you want a particular piece of code, method, or class to do and you write a test for a small piece of that and then after it passes you do that again.
At no point does TDD suggest you should know all the tests you want upfront. In fact I would expect if you know that then you don't need TDD. TDD is about learning what tests you need and what you want the object or code to look like one small piece at a time.
I am reasonably okay with my FIOS service. But only really in comparison to the hell that Comcast put me through. I am sure at some point Verizon will fuck it up. Too bad I am out of providers to try.
Lawsuits are absolutely governed by the constitution. You are using the force of the government to bring about your will. So the first amendment absolutely factors into how a speech related lawsuit plays out.
The judiciary is capable of awarding civil sanctions and damages to a private person - natural or artificial - even if those damages are on a claim on the basis of speech.
To create your version of reality, it would require a radical interpretation from the Supreme Court, or a new and separate laws passed from Congress and every state and territory to limit the powers of the judicial branch.
As it stands there is no framework in this country to uphold your version of free speech. If you feel it is inadequate for the era that we live in, then sure, keep advocating for it. This has no bearing on the correctness of Yelp's pseudo-legal interpretation in their sounding board. They are equally within their right to censor their own forum, with their disproportional influence, but their rationale does not make it accurate.
I have heard that there is the impression that the values they have gotten from private investors(i.e. VC) are higher than they would get on the open market. Which means either VCs are much better at investing than the market at large or there is a bubble(or a bit of both).
A product announcement is far more upfront and honest with its reader. It wasn't until the last third of this post did any action items emerge, 4 of the 5 being use a tool that starts at $337.
Not to mention Docker is open source and has a valid free (as in beer) tier.
I'd also complain about a Docker blog post that lulled you in and then recommended you buy a Docker Datacenter account.
I agree adding testings around legacy code is very difficult. One thing I found very helpful when I first started working in a large mostly untested codebase was "Working Effectively with Legacy Code" by Michael Feathers.
It is really nice because its chapters are arranged around specific problems you will encounter wrapping existing code in tests so you can easily find the write chapter via the table of contents.
https://en.wikipedia.org/wiki/Verizon_Communications_Inc._v....