Gregory's Server@freakazoid @littlealex My wife (former software QA person) complained for decades as her QA people were systematically eliminated in the name of “efficiencies”. “The programmers can test the code as they write it”, they said. And somehow the code always worked perfectly when run with the perfect little test system the same programmers created!
|
4 comments
@nicovanmourik @freakazoid @littlealex My small software company was bought by a larger company. For years I tried to stop layoffs of staff who supported legacy products. Those making the decisions had no idea what those people did, and assumed the legacy systems weren’t important because they had never heard of them. I lost the battle about 50% of the time, and usually within a year something crashed because a critical system had not been updated.  @nicovanmourik The thing I realized working for startups is that the thing that's most likely to kill you is being late to market. One startup literally put one of its customers out of business by losing all their data. Now they're a public company storing data for some big names. @nicovanmourik Point being, killing or severely harming one or more of your customers is just one of many risks in the risk register. |
@MarkAB @freakazoid @littlealex ow! This sounds quite familiar to me. Apparently it’s the same everywhere. Our (tiny) company is usually cut out of the project whenever profits are not as high as expected. To be hired back again when the shit hits the fan. In other words: too fucking late to be really effective.