Become a fan of Slashdot on Facebook


Forgot your password?

Comment: Re:Oh I live in this world as well (Score 1) 263

by SlowMovingTarget (#48868313) Attached to: The Tech Industry's Legacy: Creating Disposable Employees

The trouble is you've forgotten who's sitting between you and the developers. The developers themselves often don't make the call between fixing a bug or adding a feature. Unhealthy Scrum practices often lead to "stakeholders" usually Product Management or Marketing prioritizing features over defects and technical debt.

I've seen the organizational vertical slice approach work very well in the past, but you have to have management team that enjoys responsibility. Once the company goes down the Matrix-Management path, it's more about spreading blame around and abrogating accountability.

Comment: Concurrency bugs found in highly concurrent langs (Score 1) 217

by SlowMovingTarget (#48317791) Attached to: The Effect of Programming Language On Software Quality

That would make some sense if the projects themselves were intended for highly concurrent operation, thus the choice of language, thus the defects in that category because that's what the code is for.

I will say that the all of those languages have very particular models for concurrency, such that misunderstanding the models can lead to design errors in the code. Harder problems plus clever code often yields brutal bugs.

Comment: Re:I informed you thusly... (Score 1) 410

by SlowMovingTarget (#46832881) Attached to: F.C.C., In Net Neutrality Turnaround, Plans To Allow Fast Lane

You forgot to mention that the Democrats had provisions that allowed the FCC to dictate "balance" for political opinion sites. They tried to sneak in censorship provisions, and a fast-lane (in the deal with Google), in the final version of "Net Neutrality".

There is zero correlation between the name of the proposed law and its effect in practice. If you draft legislation and call it "The Save the Babies Act", then include provisions for removing arsenic regulation in the water supply coupled with a gag order, the law is bad and should be struck down. This is especially true when one side blocks amendments that would fix it (*cough* Democrats). You'll have to suffer the opposition and the media trumpeting about how you "hate babies" and have investments in pitchfork factories, but you really should work to kill that proposed law.

Comment: Re:That popping sound (Score 1) 270

... whereas catestrophic failures of nuclear plants are always going to happen and likely to be injurious to human health. In conclusion I don't think we can conclude that nuclear is safest, I think wind looks safer from those Forbes figures.


Fukushima: Built in the late 60s and early 70s.
Chernobyl: Began operation in the 70s.
Three Mile Island: Constructed in the late 60s and early 70s.

We have far newer designs for nuclear reactors for which it would be physically impossible for them to melt down or fail catastrophically. 40+ years experience in how to do something better can count for an awful lot. For example:

Comment: Re:When Egypt or Libya does it, it's bad, of cours (Score 2) 513

From the EO:

Section 1. Policy. The Federal Government must have the ability to communicate at all times and under all circumstances to carry out its most critical and time sensitive missions. Survivable, resilient, enduring, and effective communications, both domestic and international, are essential to enable the executive branch to communicate within itself and with: the legislative and judicial branches; State, local, territorial, and tribal governments; private sector entities; and the public, allies, and other nations. Such communications must be possible under all circumstances to ensure national security, effectively manage emergencies, and improve national resilience.

So government communication takes precedence over all other kinds of communication.

5.2(e) satisfy priority communications requirements through the use of commercial, Government, and privately owned communications resources, when appropriate;

They can "seize" when this new "committee" decides it's necessary.

He also revokes Reagan's EO which says this:

3.e.1. [the government must] Plan for and provide, operate and maintain telecommunications services and facilities adequate to support the National Command Authorities and to execute the responsibilities assigned by Executive Order No. 12333;

That EO says the government must maintain its own facilities, and outlines war powers and non-war emergency powers, but says the government has to make sure its own crap works in emergencies. This new order says the new "committee" has the authority to ensure that private communications assets work in emergencies so that the government can seize them when such an emergency is declared. The committee also has the authority to decide when such an emergency exists.

No tinfoil required, to see this as another power grab.

Comment: Re:Big bang has nothing to do with it (Score 1) 1276

The problem with the usual derision surrounding this subject is that it's based on a standard interpretation of the English word "day". The actual ancient Hebrew (or Aramaic, I forget which) word in that particular text means "an indefinite period of time". The Bible merely indicates separate periods of time in which those creative acts took place, but gives no actual finite duration for those acts.

Believing the universe was created in 6 24-hour periods is incorrect. Believing that the Bible says the universe was created in 6 literal 24 hour periods is also incorrect.

I think there's a world market for about five computers. -- attr. Thomas J. Watson (Chairman of the Board, IBM), 1943