Latest Source Code Cyber Hacking Getting Closer To Autonomous Cars 

 Latest Source Code Cyber Hacking Getting Closer To Autonomous Cars 

By Lance Eliot, the AI Trends Insider  

Source code is at the core of software, and we all know that software eats the world. Since source code exists as the essential underlying heartbeat of it all, here is a foundational and quite crucial question for you: Should source code be kept closely guarded and under strict lock-and-key or should it be made openly available for all to see?   

Those are the two strong-headed opposition camps about how to best treat source code. Let’s unpack this.   

One belief is that source code ought to be kept close to the vest.   

Keep the source code proprietary, hidden from view, and treat it like a deep dark secret that can only be seen by those that have an absolute need to take a glimpse. The thinking on this is that the source code is a form of revered Intellectual Property (IP) and should be housed under abundant lock-and-key safeguards. This is not simply due to retaining legal protections (which, certainly seems warranted as a result of significant costs involved in the labor to craft the programming code), but also because the source code might reveal the inner workings of the secret sauce or other vital machinations that should not be widely known (so it is believed). 

The moment someone whispers or somehow leaks even the tiniest snippet of your source code, you need to immediately and with a great show of force put a stop to the leakage.   

The other camp is the polar opposite, namely, let all source code be free to roam.   

Often referred to as open-source, the assertion is that you’ll never really be able to keep source code tightly under wraps, thus you might as well throw in the towel and make it readily available. Anyone that wants to see the source code is welcome to do so. In a sense, by proclaiming your source code to be free from the bonds of locked room confinement, the otherwise overbearing stress of trying to prevent others from seeing the code is completely deflated and not one iota of concern remains in that regard.   

Like most things in life, some depict these two diametrically opposed stances as regrettable and altogether unnecessary extremes on a spectrum that might instead allow for a type of middle ground. These centrist proponents would likely suggest that some of your source code is fine to be padlocked and kept unseen, meanwhile other parts of the source should be openly displayed to the world at large. This seems like a potentially reasonable perspective, these mediators assert.   

Not so, say the extremists, since this is the worst of both worlds’ contrivance rather than a best of both kinds of compromise. By opening the door to any of your source code, you are inviting further intrusion. The teasers revealed will simply whet appetites for more to be divulged. Furthermore, it could s

[...]

Source - Continue Reading: https://www.aitrends.com/ai-insider/latest-source-code-cyber-hacking-getting-closer-to-autonomous-cars/

webmaster

Related post