Follow Slashdot stories on Twitter


Forgot your password?

Comment Re:Record License Plate Number? (Score 1) 61

From Tesla:

The two RGJ employees and the Tesla employee were then met at the Jeep by a second safety manager at the Gigafactory. The two Gigafactory safety managers asked the RGJ employees to wait before departing, as security management and the Sheriff’s Department were en route to the scene. Disregarding this request, the RGJ employees entered the Jeep. As the Tesla employee attempted to record the license plate number on the rear bumper, the driver put it in reverse and accelerated into the Tesla employee

So second safety manager pulls up and then when the RGJ folks try and get away somebody gets a license plate? No camera rolling? Sounds like an episode of Mayberry RFD or the Wacky Racers. Barney Fife would be proud. At least a real cop (Sheriff) arrested one of them. As I previously stated, Elon needs better security if he's concerned about trade secrets getting out or a better PR department onsite so that RGJ doesn't somehow think that they need to trespass.

Comment Re:I find it amusing (Score 0) 91

Plenty of people are asking why we want to fork lift X out for something completely different. Lots of people are arguing the handful of real and actual problems that do exist with X can by solved by adding (some of which has already happened) a few more extensions and that if you don't care about the old X protocol stuff well don't use its mostly harmless to you just sitting there. So yes people are making that argument.

SystemD raised more neck hairs though for more people because, lets face it there just are not that many Linux desktops and nobody really cares much if a desktop PC hickups once and awhile Microsoft has proven that. I'd rather my desktop be rock solid but honestly if it does do something strange fix'ed with a reboot once or twice a year so frigging what.

Severs are different. Servers don't usual get X installer and probably won't get Wayland installed. So right there you have a lot of the most nervous folks not so worried about X / Wayland. Servers it matters a lot if anything goes A) wrong, B) I can't understand it *immediately* get it back up quickly, lastly C) determine a fix I can implement on my own to make sure it does not happen again. SystemD threatens that Wayland does not.

Comment How I stopped worrying and came to love the bomb (Score 1) 80

Looking at things from a purely selfish standpoint as an American I absolutely support a policy of denying additional foreign powers entry into the nuclear arms club while actively maintaining our own stock pile of weapons and ability to strike.

In fact nukes are pretty much the only weapons system I am completely okay with the Federal government having all to itself as using even the small ones in sort of domestic conflict either between Feds and the States or government in the more general sense against the public is darn near impossible to imagine. Imagine if Lincoln had the ability to nuke Richmond in 1863. Doing so would not have brought any sort of Union victory it would plunged the country in to even greater chaos, probably destroying support for even the concept of the United States continued existence.

On the other hand our national government having a strong nuclear capability provides the ultimate trump card. It means if we ever did see another Great War style conflict no nation, even the other large nuclear powers, can threaten our home land. If it ever does become a matter of fightin 'them' over here, they know we could push the button. Its nice to live under the safety of the nuclear umbrella.

See if you let more people with less to loose though join the club that is when things get dangerous. All it takes is one religious fanatic to come to power, conclude his dreams of destroying the infidel and creating a world wide caliphate/spaghetti bowl/coven can't be realized as long as we exist *boom* because (s)he might not care what happens in retaliation to their corner of this globe.

Comment Re:Horrible Article (Score 1) 32

yeah, you could always guarantee that on those kinds of RFPs somebody had too much information. At a private company, we had a bid out for a replacement for an NAS/6 mainframe so IBM came in and bid a 3083 at twice the price of what National Advanced Systems (Hitachi) came back with. When a board member heard about awarding it to NAS, he became upset since he was a former IBM guy. He convinced the board not to approve the funding and buy IBM. That 3083 was a big piece of shit but we had the foresight to have performance penalties in the contract so IBM basically gave it to us for free.

Comment The umbrella is to big. (Score 1) 184

There are really thee parts to what most people think of as comp sci - as I see it anyway.

1) Computer Engineering - The design and architecture of machines that do computation
2) Software Engineering - The design of computable algorithms for solving specific problems.
3) Information Theory - Analysis and classification of datums specifically the transmission, processing, utilization, and extraction of information from them. This usually feeds the 'specific problems' the Software Engineering guys are trying to solve.

Really only the last one is a 'science' in its own right. 1) has the sciences of physics under pinning. 2) Is really under pinned by 3 and other branches of mathematics. 3) Means mathematics most of the time but gets a little more science like in the 'scientific method sense' as you move into the quantum world.

Comment Re:sTEM (Score 1) 184

Sure, so where is the scientific method in comsci? Math proofs? They are self contained based on closed rule sets, they are supposed to be consistent within themselves but they do not measure anything, nor do they necessarily have anything to do with observable phenomena. Formal science, OK, but not just science, or STEM would be known as STE.

Comment Re:sTEM (Score 4, Insightful) 184

There are actually 4 aspects to software design and implementation.

1. Scientific: The discovery, proof, and design of algorithms. An algorithm is a basic set of rules to accomplish a task, and although more than one algorithm might accomplish that task (for example, sorting), the algorithm considered as a "black box" is invariant as to functionality. This is true science, with a mathematical slant.

2. Engineering. The ability to locate appropriate algorithms for a given task from the "literature" (speaking abstractly, since traditional printed textbooks are only a small part of the resources most of us tap these days). And to determine which algorithms are optimal for the specific project at hand.

3. Creative. This is the part Management hates. Ideally, software could be constructed by employing automated processes. In reality, there's almost always a creative aspect, and creativity is something that, so far, requires human beings. You can give 2 people an algorithm and they can implement it in 2 entirely different ways. Some of which are easier to read/maintain than others. Some of which are more flexible. Highest marks (in my book) go to implementations that are compact, readable, efficient, reliable (including fail-soft) and adaptable. I can name some sterling examples of such code. Low marks (again, my book) go to crap that's poorly-documented, ill-organized, unreliable and inflexible. Experience has taught me that if code has one virtue, it often has more, and, alas, the same thing goes for faults.

4. Mechanical. Code grinding. No matter how artistic a software project may be, there's just a certain amount of underlying concrete and rebar that demands less in the way of creativity and more in the way of just plain uninspired grunt work. If you're going to employ monkeys on a project, this is the part - and the only part - where monkeys should be employed. Don't undervalue them, no amount of inspired mathematical architecture and engineering can survive a rotten foundation. Although if we have a fault in that area these days its that the wallpaper-and-panelling crowd is valued more than the flooring-and-wall-stud group.

Of course, getting a project implemented is only one phase, even though it's where the ball gets built and started rolling. Other aspects not covered here include the support and maintenance, and the requisite planning and budgeting to ensure that the project continues for as long as it's needed and doesn't get hammered when IE8 support is dropped by Microsoft or some similar internal or external upset to the scheme of things.

Your own mileage may vary.