Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Comment Bruce Schneier says we've already lost (Score 1) 259

http://www.schneier.com/blog/archives/2013/03/our_internet_su.html

But... if I were going to try and confound the system which can correlate almost all of your electronic records, you'd need to have a rolling list of sock-puppets who supply proxy identifying information to the cell towers. You'd need to have a bundle of SIM cards in the handset to do this, or to have electronics which fake the same data. Then, to make sure you can actually be contacted, you need to have a call redirection system sending you SIP calls (though if you're designing the hardware for this, you can encrypt the data streams carrying your voice over the existing cell transports - note that Skype may be encrypted but we don't know how well or who has a back door key). To avoid that being a single point of obfuscation failure, it probably needs to be a distributed network of TOR-like relays across hardware and cloud providers, and even then, it will probably need to be steganographically hidden in ordinary-looking traffic.

Not impossible, but still a pipe-dream since 1993.

Comment Re:Cost/Benefit Analysis (Score 1) 313

How extensive is the undiagnosed population, and how fast is that population growing, and how much will they cost to treat?

You have a 1 in 100,000 of a 20+year ailment giving you symptoms which cause its diagnosis and treatment. Most carriers are asymptomatic, and the article states that no-one knows how many people are carriers or how many more infections they cause.

I'll suggest that the undiagnosed population is a few million, but it's not growing fast because most people wash their hands after pooping and before preparing food. Your fiscal choice is to wait until it becomes a problem (cost:billions, using your number above) or to pay for preventative work which studies the problem and works to diagnose and lower the asymptomatic-yet-parasitised population (cost:millions). Your call.

Comment Which Linux Platform: Desktop or Android? (Score 1) 299

May I add my contribution to the many elucidatory and finely-expressed commentary as is usual here at Slashdot?

I've not seen anyone ask which Linux platform Steam is going to arrive on. There's desktop Linux, which may make a fine foundation for a 'Punk' or 'Boiler' Steam box*, or there's Android, which will help Steam sell to casual, mobile and hand-held users. Steam games on either would be quite welcome.

*: Steam Punk variety has ornamental gears and intricate woodwork (I'm sure you could see that one coming).

Comment "not sufficient to affect change" (Score 1) 284

"Being intellectually sound, however, is not sufficient to affect change"

Can we have the argument about affect and effect here? I would have used 'effect change' here, unless OP means that change, in some way, is to be altered.

Also, there an enormous issue about how invested we all are in the existing system, with jobs and housing provided by it. That makes it very costly to change - but it's quite costly to stay paying a mortgage which supports the lifestyles of the people who sold created and sold CDOs and which is also rescuing the present situation.

Comment Re:Avoid it. (Score 3, Interesting) 228

I'm a software tester in an organisation which has clear delineation between manual testers, software test engineers who build automated tests and developers (I gotta say that I speak for me and not them here - that's the policy out of the way). The first two of that list need to have a 'question everything' testers' mentality; the last two need to have a technical grasp of how the whole thing works, from the core OS, servers and transports to the libraries used and the UI.

A manual tester is concerned with the human experience of your software. Typically there will be a script of the exact actions or the class of actions the manual tester is expected to cover. Some firms roll regression testing and new feature testing into the manual tester's role, others have a separate user-acceptance testing team who stand between released software and deployment.

The automation tester's role is to make the computer test the software, by building a framework around the program and its installed environment to check the system as-a-whole does the intended job. Some automation testers also write unit tests in the core program code; mostly this is left to the developers, who are increasingly being asked to show that their code works - and doesn't break the existing code - before check-in. Some places operate a Behavior-Driven Development (BDD) process where client needs are expressed in testable ways - so that the evidence that your software does what a client wants is written down clearly for the client to see, the tester to test and the developer to build. Some BDD systems even build tests which show that these goals are met, and are known as Test-Driven because the proof of rightness is shown by the tests.

Preparing for an telephone screening or interview about software test engineer, you will need to show that you're technically-minded, that you've worked engineered a test system before, that you understand the benefits and shortcomings of building such a system (such as knowing when to build tests and when to leave low-hanging test fruit to manual testers), and that you're concerned for the quality of the product more than for building a new toy test rig.

I disagree with nearly every point made above, but I know this as a tester: there are a lot of people who shuffle into testing because it's the gateway to working in software. That's no bad thing. But mix it with the lack of confidence to apply for and get developer roles, and you will probably harm your sanity and your career. In every job, you need to be competent and confident. On top of that, you need to be personable so, for example, you don't make bug reports critical of the developers who made them (and know how to calm down a dev who's got that idea).

To be a good tester is genuine hard work requiring the best of your technical insight, pedantry and commitment to high standards, but to be a great tester will call for charisma, kindness, honesty, good working relationships, and the skills to help make a dysfunctional team work right.

If you're only a tester for a short while and move on to a developer role, you can either blame the economy for not having enough dev jobs (so you compromised in order to fulfill your passion for making software), or you can say that you wanted to improve your developer skills by learning what it's like to be on the other side of the fence as a tester. It's not a black mark if working as a tester makes it a benefit to you and a prospective employer.

Comment Re:"Kill" is hyperbole (Score 1) 424

Content too? I think that you could easily co-opt this by supplying a farm of content-producing people for Y-Combinator to invest in, making them subject to the same market forces -- or putting them in the same boat -- that the movie studios and record companies are.

The fix requires more and better entertainment, more and better news reporting, more better-aware citizens and more and better political engagement. Make reading up on news get you points in some kind of alternate-reality game (ARG), discussing news and being politically active gets you points, too. Perhaps points to make your shopping or recreation cheaper (but there's probably other incentives).

Comment Re:The users have to change too (Score 1) 443

Can I bring my laptop to you and you install a hypervisor and partition it up with some virtual machines so I have one partition for your work environment and one for my stuff? You can pick the hypervisor...

Nice dream, but this can never be a win because, soon as I have access to the hardware and run my instrumenting hypervisor, your disk encryption is compromised and any secrets you might want to keep -- and that's no matter how obscure the notion of a secret: logins, handshakes, keyfiles, and onward to company confidential or technical know-how -- those secrets are now theirs to leak.

Comment Re:Wow (Score 1) 101

They're racking their brains as to what to do next.

I would aim for kernel threads running directly through CUDA and the Scheduler knowing the performance profile of suitable work for the GPU and the message-passing cost of moving work to the GPU^H^H^H parallelism co-processor. Make the interface right and you should be able to shift tasks across heterogeneous processing units. Do it perfectly and you can have a Linux Virtual Processor model which allows you to start running a task on your desktop, shuffle it to a laptop for transit, pare it down to use on your mobile phone, buy some CPU time from an internet cluster to grind through some calculations before transferring it home. Choose x86: there's already enough x86 junk in other trees, and it might fix up the ARM shenanigans too!

Comment Re:Never used dotNet, but this guy is an idiot. (Score 1) 758

Expensify's got 7 people total in their huddle but they want more. They've trolled successfully to get your and my attention -- and got worldwide press for this. For a company at 7 seats, everyone has to pitch in at everything: 'not my job' and 'not my skillset' are unacceptable and only 'what can I do to help us get the win?' is the only thing that will get this company to success.

Maybe you didn't like the style and wouldn't work there. It reminded me that I enjoy being the sort of person who uses any skill and the best tool to do what I've chosen to get into. And it's good to know that there are other people out there who will celebrate and encourage that.

(But still, I've been trolled and this is a post in a troll thread.)

Slashdot Top Deals

It is easier to write an incorrect program than understand a correct one.

Working...