ngoede

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.

https://en.wikipedia.org/wiki/Verizon_Communications_Inc._v....

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.

-Not a lawyer. Not legal advice-

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).

Because stuff like product announcements for Docker ect. which regularly appear on Hacker News are not?

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.

Just for the record this would work out to about $220B in modern money.

Not to nit-pick but the CEO of IBM is a woman.

I didn't think their arguments that Backblaze's early drive failures(First week or what have you) can be explained by their purchasing methods. My understanding is that they still see this well after they have stopped buying from Costco ect.

The tweaktown article did talk about temperature. I think you were right to feel they were being silly with that. Temperature MAY correlate with failure but Backblaze found it did not do so within the ranges they actually see in their environment. Something about which it appears they would have more than enough data to be able to compute.

Some grocery stores and walmart's have RO water machines outside their stores also. However, if you choose to use those it would be good to invest in a tester as they do not always change the filters on schedule.

Haha, yeah I shared a dial up connection for a bit of all things. Then when my family got @Home cable internet it was much better for that.

It is my experience that these figures are well on the high side for Philly though.

I am pretty sure Rand Paul just votes against Budget bills in general and this has nothing to do with CISA being part of it.

They should also provide the same fixed size pipe to everyone if they want to charge by total bits transmitted.

Of course they also tend to fail for the same reason as gravity slowly pulls them off the lathe.

Having had the fun that is working for a company that gets bought by IBM I wish their workers the best of luck.

Hope they enjoy the Blue Washing(TM)

Buy other companies.

Yeah, also the big difference it seems to me compared to say the idea of legalizing drugs is that this is a market of theoretically finite supply. Therefore, as the supply shrinks it increases the incentive to find other sources. This is in contrast to a legal drug market which would include legal production and therefore, in theory, crowd out the illegal supply.

The existence of parallel construction is huge problem with the idea that the only result of gathering evidence illegally is that that evidence is excluded from legal use.

The police/NSA/whomever can still use that information to inform their investigations to discover other legal evidence that they could otherwise only have found by chance. Not to mention the possibility of just leaking information like this later to discredit or punish a political enemy.

Also LinkedIn Testimonials are approved by the person being reviewed.

I can get behind the message that Scrum has been problematic because it focuses too much on selling PMs on practices to the exclusion of developer practices.

XP was much more balanced in this regard. I think Scrum loses a lot in both being so free-form to start and in being so often something that PMs or management bring to the table. XP in my experience always seemed to be more of a developer lead movement and ultimately a development process without developer buy in becomes a command and control process that kills creativity and stifles feedback.

What percentage of the tests are full system, integration, and unit tests?