3 ms·

100% with you. Generally posts like these induce the HN crowd blinders, since people who typically post here are sympathetic to software developers. The same so

by RONROC 5y ago

100% with you. Generally posts like these induce the HN crowd blinders, since people who typically post here are sympathetic to software developers. The same software developers who are making money hand over fist. The same software developers who refuse to pay reasonable amounts of money for zero days. These hackers are fulfilling a market inefficiency whether users here would like to acknowledge that or not. It’s not the mean hackers or bitcoins fault. The blame should be squarely be placed at the doorstep of all the brilliant engineers who are responsible for the creation of the system architecture but for whatever reason are nowhere to be found when it’s starts to degrade. This is a major issue with software development that is simply not convenient to discuss because the incentives to frog hop from job to job massively outweigh the benefits of staying on board for the years the job actually requires. And yes, people will tell you, especially on here, that air tight code is a pipe dream. And maybe so, but the amount of severe deficiencies in code bases that millions of people rely on every day are simply unacceptable. When your earnings report is in the upwards of hundreds of millions, it’s really hard to play stupid.

Karunamon 5y ago
This sounds like you're laying the blame at the feet of developers. Unless we're talking about FOSS, most devs don't get to pick what to write; only how to do it, and then in a very limited way on artificially constrained (read: unreasonable) timescales. Start holding companies responsible for their shitty priorities and then things may change. Until then, this is doing the equivalent of yelling at retail workers for company policy. They are not the responsible party here. That responsibility starts at the C-suite and filters down.
- labawi 5y ago
  Currently the blame should be on companies and people from the top, as the developers don't really have much choice (without unionizing or whatever). OTOH, it doesn't have to be this way. As an example, electricians are licensed here (I think) and it is against the law to pressure them work faster. Architects and building engineers are licensed (need proper education + practice), and they are required to uphold certain standards. They give a stamp of approval and at fault (insurance compulsory) and can lose their license if there are problems with their designs, regardless of any pressure from investors.

by RONROC 5y ago

Karunamon 5y ago

This sounds like you're laying the blame at the feet of developers. Unless we're talking about FOSS, most devs don't get to pick what to write; only how to do it, and then in a very limited way on artificially constrained (read: unreasonable) timescales. Start holding companies responsible for their shitty priorities and then things may change. Until then, this is doing the equivalent of yelling at retail workers for company policy. They are not the responsible party here. That responsibility starts at the C-suite and filters down.

labawi 5y ago
Currently the blame should be on companies and people from the top, as the developers don't really have much choice (without unionizing or whatever). OTOH, it doesn't have to be this way. As an example, electricians are licensed here (I think) and it is against the law to pressure them work faster. Architects and building engineers are licensed (need proper education + practice), and they are required to uphold certain standards. They give a stamp of approval and at fault (insurance compulsory) and can lose their license if there are problems with their designs, regardless of any pressure from investors.