3 ms·

These hacks better be glad this industry isn't regulated like other professions where the individual professional is liable for his work. If these developers w

These hacks better be glad this industry isn't regulated like other professions where the individual professional is liable for his work. If these developers were doctors or engineers they personally would be liable for damages. Right now we have laid blame at the feet of the company, but this company doesn't seem to understand they don't have the technical know how to be building websites for their customer base.

readme 14y ago
Please don't give the government ideas
- chubbard 14y ago
  Well it might not be your government that institutes this idea. Given this is a bank in the UK you or I might not be allowed to vote on this type of thing, but if general populous begins to see the choice of technical decisions are more in the hands of the professionals and not so much the company it could very well change. And it might be companies that push legislation like this if they feel they don't want to bear the legal risk. Now usually there is professional insurance that consulting companies have to purchase for liabilities just like this. If you are consulting firm implementing systems for banks they will require you carry $2 millions/dev of insurance should there be a screw up like this. Maybe this is the best option because I'm not exactly behind supporting measures to certify or regulate our industry, but I fear bad behavior like this might force it. This is a hack rookie mistake. I'm fully aware of the ramifications of doing something like this, but I'm not immune to mistakes that could result in the same damage. However, a law like this would treat me the same way as these hacks.
delinka 14y ago
The company certainly should be responsible. The alternative (which I'd say would be good for us seasoned software professionals, bad for the companies, and not very good for the indie software profession) is Computer Software Creators get their own professional, gov't-approved certifications, a large pay increase to go with the risk increase, and a legal requirement for these businesses to only hire certified Computer Software Creators. Ain't capitalism grand?

readme 14y ago

Please don't give the government ideas

chubbard 14y ago
Well it might not be your government that institutes this idea. Given this is a bank in the UK you or I might not be allowed to vote on this type of thing, but if general populous begins to see the choice of technical decisions are more in the hands of the professionals and not so much the company it could very well change. And it might be companies that push legislation like this if they feel they don't want to bear the legal risk. Now usually there is professional insurance that consulting companies have to purchase for liabilities just like this. If you are consulting firm implementing systems for banks they will require you carry $2 millions/dev of insurance should there be a screw up like this. Maybe this is the best option because I'm not exactly behind supporting measures to certify or regulate our industry, but I fear bad behavior like this might force it. This is a hack rookie mistake. I'm fully aware of the ramifications of doing something like this, but I'm not immune to mistakes that could result in the same damage. However, a law like this would treat me the same way as these hacks.

delinka 14y ago

The company certainly should be responsible. The alternative (which I'd say would be good for us seasoned software professionals, bad for the companies, and not very good for the indie software profession) is Computer Software Creators get their own professional, gov't-approved certifications, a large pay increase to go with the risk increase, and a legal requirement for these businesses to only hire certified Computer Software Creators. Ain't capitalism grand?