4 ms·
The company and its developers should be liable. Developers know it is wrong and yet they do it anyway. The fact management told them to do it doesn't matter.
by matheusmoreira 5y ago
The company and its developers should be liable. Developers know it is wrong and yet they do it anyway. The fact management told them to do it doesn't matter.
Real engineers don't sign off on a project if they think the building is going to fall apart. If a company starts ignoring security for the sake of profit, developers should react by literally walking out and refusing to have anything to do with the project. Anything else means they share the blame.
- chousuke 5y agoThe problem is, what power allows the developer to refuse? If they do, a manager can find someone who won't, and developers who stand by their principles will lose to competition. A building engineer could probably drop a hint somewhere and have all kinds of inspectors come knocking, but there's no "building code" for software except in very specific cases; it's perfectly legal to develop insecure software otherwise, and to keep that insecurity a secret from users.
- josephg 5y ago> The problem is, what power allows the developer to refuse? One power we all have is how valuable we are in the jobs market. If you’re a decent engineer in today’s climate, you could get a new software job in days. And it’ll take your company weeks to replace you if they’re lucky, and months to bring your replacement up to speed on what you were working on. The idea that you’re stuck simply working at the whims of management is a self defeating illusion. It is only as true as you believe it to be.
- username90 5y agoThere are tons of engineers out there who aren't decent, what would you say they do in this scenario?
- bsenftner 5y ago...but that is an illusion power, because all we'd be doing is shifting from one poorly managed code dump to another, just shifting the faces on the pointy haired bosses. Finding a technology developing organization that is not a shit show of unmanaged personalities and a teetering tower of technical debt is extremely difficult.
- wonderwonder 5y agoI find most employees over estimate their importance. Everyone is replaceable especially a software developer, there are hundreds of just as good developers waiting to take your place if the salary is right. In addition if they fire you on the spot, you are the one that has to deal with that. If the developer does not have a very good emergency fund that further compounds the stress to do as you are told. Not everyone in software makes a US FAANG, SF, NYC salary.
- voakbasda 5y agoAs a remote only 10xer, it take me months to find a new position. Last two search took over six months. I cannot afford to be principled and walk out every time my employer wants to ship buggy code. And we ship bugs pretty much on a weekly basis, because there is no profit in doing things correctly.
- josephg 5y ago> I cannot afford to be principled and walk out every time my employer wants to ship buggy code And your manager can't afford to fire everyone who pushes back on shipping insecure code. And its not a black and white thing. There's almost always paths which work for everyone. Actively looking for those paths isn't the sign of a bad employee. Its the sign of leadership. In my experience people who step into that sort of responsibility don't get fired. They get promoted.
- KronisLV 5y ago> And your manager can't afford to fire everyone who pushes back on shipping insecure code. I feel like they actually can, since: - most people want to get paid and to have a job, not get fired over principles - therefore, they will bend to the whims of management and release whatever they're told to release - they don't actually have any sort of leverage, as most developers, and are easily replaceable It is good that your experience is so positive, yet that's not the reality in numerous places. Here's a similar post from today: https://news.ycombinator.com/item?id=27629543 https://news.ycombinator.com/item?id=27629543
- bsenftner 5y agoThis is the key reason. Because software products are compiled black boxes, and there is no logical way for a 'software construction building code' or the existence of an 'independent outside-the-company software infrastructure inspector" to exist the industry must develop these roles and must empower them to enforce a structure that the line working developers are not paid to prioritize. It is an extremely tricky mess, of the nature Nobel Prizes in Economics are awarded.
- willcipriano 5y agoThat doesn't seem to be how anything else works. For example, when tech companies colluded to lower wages (anti-"poaching" agreements) I don't believe HR or the executive team was held personally liable. The same holds true for firms who have engaged in racial discrimination in hiring, or covered up risks with a new drug coming to market. Time and time again firms are asked to pay fines in response to executive malfeasance rather then the executives themselves, why is this different?
- IncRnd 5y ago> Time and time again firms are asked to pay fines in response to executive malfeasance rather then the executives themselves, why is this different? It's an indication that engineers know in some cases they are releasing broken software, and management may not be aware. Just look at this page and it's article, developers know about this, because they congregate to discuss how they release broken software, know they should do better, yet don't always tell management about faults in the product. A business shield only protects people when they are conducting business.
- willcipriano 5y agoIf I'm taking the lion share of the risk on shipping a product, I'm also collecting the lions share of rewards or I'm not interested in participating. As new vulnerabilities are found every day, I'd expect those rewards to be ongoing, so they would look more like royalties, I'll need to be paid as long as you are using the software. Further I'll need to be able to invalidate that license when I no longer wish to carry the risk. I think under those conditions most firms would prefer to own the risk themselves.
- IncRnd 5y agoThose conditions aren't realistic for an employee, since anyone working for someone else who feels that way is bound to be extremely frustrated. The point that you missed, however, is that an employee should not accept the risk but should transfer the risk by notifying the employer. Otherwise, articles such as this are fodder for putting the blame of exploited vulnerabilities squarely on employees who knew of the risk and, according to some of the comments here, plotted not to tell their employers.
- Aeolun 5y ago> The fact management told them to do it doesn't matter. It absolutely does. If you hold any legal power to reject a deployment (like a true engineer), then you can sue the company when they hold it against you, so they won’t. If you do it in any other situation you are just being difficult.
- tremon 5y agoSo, rephrasing your statement, it absolutely doesn't, because software developers don't hold any legal power to reject a deployment (since they aren't true engineers), so they can't sue the company when it's held against them. If software developers do that they are just being difficult.