4 ms·
Here's how I would do it: No degree, but rather a programmer publicly signs off on his code, and gets both credit and blame for it. Anyone who wants can regis
by ars 10y ago
Here's how I would do it:
No degree, but rather a programmer publicly signs off on his code, and gets both credit and blame for it.
Anyone who wants can register for a programmer ID (in practice a public key). There is no test, just an administration fee.
When you write code you sign off on it, perhaps with some accompanying text describing what parts you worked on.
No more anonymous code shipped by a company entity, instead do it like how movies are done: Every single person gets credit (including QA and administration), every tool used gets credit.
- fao_ 10y agoEither the key can be replicated easily without signing, or there is the probability of an overlap between different keys. Either way there is the probability for forgery.
- CM30 10y agoInteresting idea, but... Seems like a great way for company bosses to say "nah, we didn't know about this, the rogue programmer there made the decision". Unless you have some way to also blame the management responsible for deciding such a design should be implemented.
- ars 10y ago> Unless you have some way to also blame the management responsible for deciding such a design should be implemented. Their name is on it as well, with text describing what they approved.
- CM30 10y agoWell, that makes it a lot better then. Nice to know this issue was considered in some form.
- mattwinslow 10y agoThis happens to various degrees in the clinical research industry, depending upon the nature of the work (partly thanks to 21 CFR Part 11!). Several years ago I worked in data management on a maintenance team for clinical trial databases. Company-wide, there was a rigid system in place that captured electronic signatures as change requests were documented, code was modified, and tests were completed. Anything that was done flowed through at least those three distinct groups (data team lead, maintenance programmer, & QA). We could easily tell how a study's database had been modified in the past (including who had requested the change, who programmed the change, and who tested the change)...there was always an expectation that every i was dotted, t was crossed (or semicolon was in place) before anyone signed off on their work since it would permanently enter the record and couldn't be erased.
- notmything 10y agoSounds dangerous - mistakes happen - will I get thrown under the bus by the media if a bug in my code causes an accident that no QA process could have reasonably picked up on?
- ars 10y agoYes, that will happen. Consider an analogous situation: You made a mistake designing a building. Should you be able to shrug it off as "mistakes happen"? This has actually happened in the real world with buildings, and when it does if you are responsible and work diligently to correct the problem people are understanding. Do the same here.
- notmything 10y agoI'm not saying you should shrug it off - I'm saying you should't have your life ruined over a mistake in some code you wrote. I'm yet to see a building collapse around me in my city - I see software fail all the time though - I think we are better at building tall buildings than we are building software.
- ars 10y agoOr, it might be the exact opposite: For a building the engineer and builders are required to take personal responsibility. Not so for software. Perhaps if you change that software might change.
- notmything 10y agoNothing would ever get built if individual devs were held liable by the public. The liability sits with your employer.
- MyNameIsFred 10y agoSorta. The basis for your concern underlines one of the problems. When such gaffs happen in engineering, the firm is blamed. Within the firm, individual actors are blamed. In software, on the other hand, your major system might have responsibility for a critical system spread across a total of 1 persons, so he gets all the blame. Is that really okay for one hip-shooter to take this on in the first place?