Trouble is Magsor this is not really a piracy debate (at this point anyway)- the guy in question abused a position of trust (allegedly?) to take a bunch of code that the bank contracted (or hired people to) to develop* with the intention of providing them with a commercial advantage and/or do their job (something I will argue what most code that is ever written is done with the intention of doing and certainly what the vast majority of paid programmers do).
Before this ruling (and presumably the logic going into it with regards to the charges) was that doing as such (it is generally assumed if you have it you have the potential to do something and will be stung accordingly although actually doing something with the info tends to make for harsher sentences) would have left the bank at a disadvantage by potentially allowing someone else to use their methods (banks frequently employ some bloody clever people at serious cost to them to cook up schemes by which they can make some money or provide the services they need to provide) or know how things work and react accordingly (placing them at a competitive disadvantage by way of having their information that was illicitly obtained used against them**). Such acts introduce elements of industrial or possibly financial espionage and trade secrets as well as the more traditional/viable? charge of taking some information/code that did not belong to him which is what this ruling seems to largely deal with (although the espionage stuff seems to have been dismissed by way of the ruling as well).
For an example of a similar case (although without the sale of aspect) http://www.theregister.co.uk/2012/04/09/intel_ex_engineer_spy_pleads_guilty/ and there are other ones involved the theft of information databases (were I to be employed by you and then upon leaving your employment I took your database of clients and associated numbers and you found out would I not end up in some form of court for wrongdoing?). Depending upon how the code works/was written it might even have incorporated elements of the examples I gave (code, data and UI is supposed to be separated but that is just an ideal not a requirement).
*there is also the related thing where companies will often get you to sign away anything you make, even for you, on their machines and sometimes they go further and extend that to anything you develop when you are working for them even on your own time/equipment.
** using internal memos and such leaked to you to move accordingly in financial markets is known as insider trading and tends to see you in front of the beak and financial regulators having to explain yourself.
Short version- this is not so clear cut as you make it seem.
Before this ruling (and presumably the logic going into it with regards to the charges) was that doing as such (it is generally assumed if you have it you have the potential to do something and will be stung accordingly although actually doing something with the info tends to make for harsher sentences) would have left the bank at a disadvantage by potentially allowing someone else to use their methods (banks frequently employ some bloody clever people at serious cost to them to cook up schemes by which they can make some money or provide the services they need to provide) or know how things work and react accordingly (placing them at a competitive disadvantage by way of having their information that was illicitly obtained used against them**). Such acts introduce elements of industrial or possibly financial espionage and trade secrets as well as the more traditional/viable? charge of taking some information/code that did not belong to him which is what this ruling seems to largely deal with (although the espionage stuff seems to have been dismissed by way of the ruling as well).
For an example of a similar case (although without the sale of aspect) http://www.theregister.co.uk/2012/04/09/intel_ex_engineer_spy_pleads_guilty/ and there are other ones involved the theft of information databases (were I to be employed by you and then upon leaving your employment I took your database of clients and associated numbers and you found out would I not end up in some form of court for wrongdoing?). Depending upon how the code works/was written it might even have incorporated elements of the examples I gave (code, data and UI is supposed to be separated but that is just an ideal not a requirement).
*there is also the related thing where companies will often get you to sign away anything you make, even for you, on their machines and sometimes they go further and extend that to anything you develop when you are working for them even on your own time/equipment.
** using internal memos and such leaked to you to move accordingly in financial markets is known as insider trading and tends to see you in front of the beak and financial regulators having to explain yourself.
Short version- this is not so clear cut as you make it seem.














