4 ms·
The "lite" version of certification in tech could be a requirement for a programmer equivalent of a Professional Engineer to sign off on any piece of software t
by TeMPOraL 6y ago
The "lite" version of certification in tech could be a requirement for a programmer equivalent of a Professional Engineer to sign off on any piece of software that becomes used in a product or service offered to people (whether commercial, public or by non-profit orgs).
This way, I'd be free to develop my Open Source library and engage in exploratory coding, and you'd be free to play with it internally, but if you want to use it in a product you sell to people, you'll have to get a licensed software person to sign off on your project. You probably won't want to waste their (and your) time on untrustworthy projects, so I'll have to get a licensed software person to sign off on particular releases of my library to certify quality, to make it more likely someone will want to use it.
This would introduce some inertia in software - not enough to be stifling, it won't pry away Turing-complete languages from the hands of curious children, but perhaps it'll be enough to introduce some sanity into the industry.
- balsop 6y agoIt seems to me that all kinds of existing certifications in software have introduced insanity. It will create another layer of bureaucrats who are after certifications but cannot program. It will further kill "open" source software, which already is destroyed by corporations. I think programming is too open ended for certifications.
- WrtCdEvrydy 6y agoLook at the cloud certifications... you don't need them to use AWS cloud but you get incentives to certify your people.
- TeMPOraL 6y agoExisting certifications in software are just attempts at making money off gullible people (EDIT: at least to my experience, most are). I'm talking about real, government-backed certifications: that is, you can't sell serious software products that don't get a sign-off of someone licensed, and that licensed person then has career liability (and in extreme cases, monetary penalty or even jail time) for failures of that software. As far as I know, software is the only field that can get away with something like this: THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Imagine finding something like this on a pack of aspirin.
- WrtCdEvrydy 6y ago> Existing certifications in software are just attempts at making money off gullible people I'd argue the AWS ones are worth it... we get a workload credit for certifying people.
- TeMPOraL 6y agoFair enough. I shouldn't have generalized; there are some that are valuable in certain niches. MS and Cisco certs come to mind (and back when I was studying at university, the learning resources for Cisco certificates were our go-to sources for understanding computer networks). But in my impression, it's an exception to the rule.
- voxic11 6y agoI found something pretty similar on this chemical supply company that sells acetylsalicylic acid (aspirin) for educational purposes. The purpose for which you advertise your wares matters. I don't think such a disclaimer is unreasonable on certain software projects. > IN NO EVENT SHALL DISTRIBUTOR, DISTRIBUTOR'S SUBSIDIARIES OR AFFILIATES, OR ANY SUPPLIER BE LIABLE UNDER ANY LEGAL THEORY (INCLUDING BUT NOT LIMITED TO CONTRACT, NEGLIGENCE, STRICT LIABILITY IN TORT OR WARRANTY OF ANY KIND) FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES (INCLUDING BUT NOT LIMITED TO LOST PROFITS), EVEN IF WE OR ANY OF OUR SUBSIDIARIES, AFFILIATES OR SUPPLIERS HAD NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. https://www.fishersci.com/us/en/footer/legalnotices.html https://www.fishersci.com/us/en/footer/legalnotices.html https://www.fishersci.com/shop/products/acetylsalicylic-acid-99-acros-organics-3/AC158180500#?keyword=acetylsalicylic+acid https://www.fishersci.com/shop/products/acetylsalicylic-acid...
- WrtCdEvrydy 6y ago> could be a requirement for a programmer equivalent of a Professional Engineer to sign off on any piece of software that becomes used in a product or service offered to people To be honest, it's funny graduating from a 4-year college with an Engineering degree, being offered to be inducted to the order of the Engineer, getting the ring and being told not to sign off on designs that would harm people while being offered thousands of dollars to get people addicted to software. I wonder if we should call it "programmer's guilt"?
- TeMPOraL 6y agoYeah. As long as the industry is run by ad people, you can forget about ethics in it. Best way is to stay clear of that, but it's getting increasingly difficult.
- leetcrew 6y ago> The "lite" version of certification in tech could be a requirement for a programmer equivalent of a Professional Engineer to sign off on any piece of software that becomes used in a product or service offered to people (whether commercial, public or by non-profit orgs). this makes sense for software that handles PII and/or where bugs could cause loss of life or limb, but this seems like overkill for a lot of commercial software. but suppose I'm selling some desktop application that doesn't have either of those qualities. wouldn't the certification requirement be a bit overkill in this situation?
- TeMPOraL 6y agoYou may be right, and perhaps it would be better to relax the requirements, letting them flow from the critical software (PII, risk to life and limb) downwards. So if I want to make a new radiation therapy machine, I won't be able to pull in random crap from NPM. My software will need a PE sign-off, and so will my dependencies. This will hopefully lead to some OSS libraries getting certified (perhaps with corporate interest funding the certification), creating an excuse/incentive for other companies. Now some bank will notice that a third-party app they use internally has eaten their data several times, causing monetary loss, and it'll decide that going forward, PE-certified software is prioritized during procurement. Creating incentive for non-critical software vendors to get their software certified. Etc. I'm not sure if the dynamics would play out this way, but it seems plausible. The goal here is to retain free experimentation - I'd hate to end up in a world where you aren't allowed to use a Turing-complete language without a license - while at the same time forcing responsible software practices where they matter.
- leetcrew 6y ago> You may be right, and perhaps it would be better to relax the requirements, letting them flow from the critical software (PII, risk to life and limb) downwards. agreed, I think this would achieve a lot of the positive downstream effects without placing an undue burden on developers of less critical commercial software. to go back to the desktop app example, it probably needs to authenticate serials for authorized users. you could write a small self-contained auth server and have it certified, while continuing to ship your behemoth desktop app that can't be fully evaluated.