Where I work we have code reviews at various degrees. I find someone else just reading over my code and emailing suggestions helps tons; It spots obvious errors, ways code could be done better, and just a ton of other things. It helps improves my own coding style too.
Now, being at Manchester university, this is obviously great and all that (if nothing more than proof they're actually doing something with my tuition fees). But what I want to know is, why can we do this, yet I *still* can't register my module choices properly in the backwards campus solutions software:)
I know i'll probably get slaughtered for this, but I agree with this statement completely.
I'm completely pro open source, and started off with Ubuntu as my first linux distro about a year ago, as everyone was raving on about it. Really impressed with the package manager, but I was completely lost when it came to installing stuff that wasn't in there.
I'm on Mandriva now, which is a massively improved user experience, where most of my stuff worked perfectly out the box (except my wireless, which took a bit of work, but I got there eventually). However, I'm now in a position where I want to install subversion and tomcat, and it's really not easy. Windows wins in this situation, because of the ease of automated installers. Which is a great shame, and I know I'll get lambasted because I haven't done enough research or put the effort into to learning the basics of installing on linux properly, but for it to ever be accepted in the mainstream by your average Joe, things like that need to "just work".
With the original swipe system, the liability was with the bank; If you got frauded, then the bank had to re-emburse you. With the introduction of chip and pin, this remained the same; If you're chip and pin is frauded then the bank is still liable. FYI, if your swipe is frauded, it is now the place the fraud happened (e.g. the shop) that is liable, something that was introduced to basically force most companies to change over.
I can verify that the bank take liability, as my girlfriend recently had her card details stolen from an ATM (still not sure of the method, but there were about 100 students I'd guess who got done too, so i'd guess a some sort of magnetic swipe + camera job). She had about £200 taken, and the bank refunded all of it to her.
As for the actual security of chip and pin, as many people here have reiterated, everything is liable to be cheated some way or another, it's a sad fact of the technological world. However, all you need to do is look at the figures (thanks to chip and PIN, in 2005, there was a reduction of nearly £60m in counterfeit and fraud on lost and stolen cards (a drop of 24%) compared to 2004. [http://www.chipandpin.co.uk/overseas/success.html ]) to see that there is a clear reduction in fraud. The long term reduction in France has been even more significant (estimated to be 80% [http://www.whatprice.co.uk/financial/chip-and-pin -credit-card.html]). So the technology may be liable to fraud, but significantly less so than swipe.
Stuff like this is scaremongering and will stop people using cards when they're safe. Just like happened with internet shopping, which is actually safer than real life shopping (1/3 of adults frauded in real world, just 15% online according to research from paypal [www.easier.com/view/News/Finance/article-80950.ht ml]).
1) Just to give context to who I am; I am a placement student in the third year of my degree (UK based), therefore holding no power.
2)XP is for some and not others. Having researched into it a while a go, I wasn't taken by it. And to get people to change their practices is always difficult.
3) I work in the IT department for a company that offers careers advice for students; the stuff I work on is web based: Written in java and jsps.
4) We are gradually transitioning to a CVS; all new stuff is put into one, it's the old code that isn't in the right format. The idea of this thread was to try and find intermediary measures/ additional features to aid in my job.
5) There are quite a few simultaneous projects, say 4 or 5, and a coding team of about 20-30 people.
6) We already have a staging server, and all changes are made on the files on there, which is why the changes sometimes get uploaded without being ready... We have coding guidelines and tools to aid development, but most don't use them.
7) Much of the problem arises from the fact many of the changes are minor, to one or 2 lines of code. As a result they are released ad hoc, and as they are only small there is no project manager. Everyone in the team can release content, and generally they are left to their own devices for testing and suchlike.
8) As for emailing everyone to tell them about re-usable code, what about people joining the team at a later point? And what about when someone comes to work on something that could find the code useful, but doesn't remember the email?
Sorry if that's a lot of very non sensical information in one go, but it gets the point accross.
Thanks to everyone so far, it's really good hearing these comments. All comments welcomed, and i'll keep you posted as the changes happen.
Slashdot Mirror
Where I work we have code reviews at various degrees. I find someone else just reading over my code and emailing suggestions helps tons; It spots obvious errors, ways code could be done better, and just a ton of other things. It helps improves my own coding style too.
Now, being at Manchester university, this is obviously great and all that (if nothing more than proof they're actually doing something with my tuition fees). But what I want to know is, why can we do this, yet I *still* can't register my module choices properly in the backwards campus solutions software :)
I know i'll probably get slaughtered for this, but I agree with this statement completely.
I'm completely pro open source, and started off with Ubuntu as my first linux distro about a year ago, as everyone was raving on about it. Really impressed with the package manager, but I was completely lost when it came to installing stuff that wasn't in there.
I'm on Mandriva now, which is a massively improved user experience, where most of my stuff worked perfectly out the box (except my wireless, which took a bit of work, but I got there eventually). However, I'm now in a position where I want to install subversion and tomcat, and it's really not easy. Windows wins in this situation, because of the ease of automated installers. Which is a great shame, and I know I'll get lambasted because I haven't done enough research or put the effort into to learning the basics of installing on linux properly, but for it to ever be accepted in the mainstream by your average Joe, things like that need to "just work".
With the original swipe system, the liability was with the bank; If you got frauded, then the bank had to re-emburse you. With the introduction of chip and pin, this remained the same; If you're chip and pin is frauded then the bank is still liable. FYI, if your swipe is frauded, it is now the place the fraud happened (e.g. the shop) that is liable, something that was introduced to basically force most companies to change over.
I can verify that the bank take liability, as my girlfriend recently had her card details stolen from an ATM (still not sure of the method, but there were about 100 students I'd guess who got done too, so i'd guess a some sort of magnetic swipe + camera job). She had about £200 taken, and the bank refunded all of it to her.
As for the actual security of chip and pin, as many people here have reiterated, everything is liable to be cheated some way or another, it's a sad fact of the technological world. However, all you need to do is look at the figures (thanks to chip and PIN, in 2005, there was a reduction of nearly £60m in counterfeit and fraud on lost and stolen cards (a drop of 24%) compared to 2004. [http://www.chipandpin.co.uk/overseas/success.html ]) to see that there is a clear reduction in fraud. The long term reduction in France has been even more significant (estimated to be 80% [http://www.whatprice.co.uk/financial/chip-and-pin -credit-card.html]). So the technology may be liable to fraud, but significantly less so than swipe.
Stuff like this is scaremongering and will stop people using cards when they're safe. Just like happened with internet shopping, which is actually safer than real life shopping (1/3 of adults frauded in real world, just 15% online according to research from paypal [www.easier.com/view/News/Finance/article-80950.ht ml]).
And the real question is, can it play doom?
1) Just to give context to who I am; I am a placement student in the third year of my degree (UK based), therefore holding no power.
2)XP is for some and not others. Having researched into it a while a go, I wasn't taken by it. And to get people to change their practices is always difficult. 3) I work in the IT department for a company that offers careers advice for students; the stuff I work on is web based: Written in java and jsps.
4) We are gradually transitioning to a CVS; all new stuff is put into one, it's the old code that isn't in the right format. The idea of this thread was to try and find intermediary measures/ additional features to aid in my job.
5) There are quite a few simultaneous projects, say 4 or 5, and a coding team of about 20-30 people.
6) We already have a staging server, and all changes are made on the files on there, which is why the changes sometimes get uploaded without being ready... We have coding guidelines and tools to aid development, but most don't use them.
7) Much of the problem arises from the fact many of the changes are minor, to one or 2 lines of code. As a result they are released ad hoc, and as they are only small there is no project manager. Everyone in the team can release content, and generally they are left to their own devices for testing and suchlike.
8) As for emailing everyone to tell them about re-usable code, what about people joining the team at a later point? And what about when someone comes to work on something that could find the code useful, but doesn't remember the email?
Sorry if that's a lot of very non sensical information in one go, but it gets the point accross.
Thanks to everyone so far, it's really good hearing these comments. All comments welcomed, and i'll keep you posted as the changes happen.