Skip to main content

Nott Tuesday 09-02-2010

I went to the Nott Tuesday event last night. There were some interesting points raised about who owns data about you and how it is used. It's a difficult subject for me because I find it a little tiring. In fact I find it very hard to write about, so I will make it brief.




The presentation was about the "man" coming down on you and taking all the data they record about you and using it for purposes that you may not want / agree to. Ah ok, I don't like the sound of that. Mmm ok so there is a problem there but surely the best way to sort it is to just firm up the Data Protection act and legislate in favour of the people whose digital information is stored. In addition to this, if you are collecting certain data they could insist that you sign up with a register (list of companies) that do collect data, or it could be a voluntary thing but people would lean towards sites and services that are members of DatSecure (my new name for it). Once we had this then these companies could be audited. Obviously the web can be border-less so there would need to be a little bit more thought put into it then that. I'm an ideas man not a details man so best to leave the legal discussions and details to others (some sort of slithering administrator creature with no technical / artistic skills).

He did make some good points though about collective movement. That was really interesting. I think they already use some technology like this in large shopping centres where they track mobile phone movements (they don't record all the details they say). However people were not overly keen on this. But if there were assurances such as audits on the data collection then that could possibly give people the confidence to accept it. The idea would be that if a group of people were moving down the street in one collection, clever software would know that about that time and on that street the number 36 bus was supposed to be there. This would be achieved by collecting live information on how the bus was progressing from individuals phones on the bus.


Like I said, it was interesting.. I don't think it is the best idea though. I would just prefer to see trackers on the bus enforced by legislation so they had to do it. If I was using the buses every day I would even probably pay a small fee for the live information.


Ultimately the argument is purely academic because as we all know, Robots will inherit the Earth about the year 2020 anyway.

Comments

Popular posts from this blog

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second

Accessing the UI Thread with Tasks in F#

I have a Windows Forms program written in F# that can deploy a code base to n number of sites at once (you select the sites you would like to deploy to and it goes off and completes a number of tasks (backing up current sites, various unpacking and moving of files etc... ). Once you start it, it begins it's merry journey and begins to update the UI with what has happened. At the moment this method of updating the UI is not pretty because the threads I am doing the work on can't update the UI so I perform some fiendery to make that happen (don't ask). I knew there was a better way using some newer .NET features but I just hadn't got round to having a fiddle yet. I have now found that if you use the built in Task class but break your code up in a nicer way and then chain the tasks together you can then pass the correct context into the task that you want to talk to the UI. Here's a little script to give you a feel for it. You can press the "start" butt

NESTA - Next Gen.

via nesta.org.uk Following on from an article on the BBC about Raspberry Pi, this next gen report has some interesting findings. The scariest stat which I picked out from the BBC website was "out of the 28,767 teachers who were awarded Qualified Teacher Status... in 2010, only three qualified in computing or computing science as their primary qualification" Having worked as a computer science teacher for a year in a school that was a specialist in Computing I can concur that the uptake in Comp Sci was woeful. 2 Students for A2... The other teachers backgrounds in Computer Science was also fairly woeful (most knowing a bit about Office but still a paltry amount even about that). I couldn't speak for my counterpart that I was covering however. I suspect they were fairly up on things. All in all what kills me is that Computer science is not a secondary level subject. Areas are often covered, a little in IT, a little in DT subjects (if kids choose Systems and Contr