←back to thread

Mozilla lays off 70

(techcrunch.com)
929 points ameshkov | 1 comments | | HN request time: 0s | source
Show context
strict9 ◴[] No.22058568[source]
Not sure of Mozilla’s financial or organizational structure but it seems to be part of a larger trend of de-emphasizing QA departments at software shops large and small over the past 10 or so years.

In many ways test automation tooling has become much easier to use, develop, and manage.

But I suspect the larger driving force is that it’s (arguably) a cost center for an org. The burden of ensuring software quality can be shifted to devs and PMs, though usually with mixed results.

For Mozilla, axing quality and security first is a bad look when those are crucial aspects of a privacy-first company value.

replies(7): >>22058757 #>>22058762 #>>22058953 #>>22059007 #>>22059065 #>>22059192 #>>22060314 #
crazypython ◴[] No.22059007[source]
Mozilla uses AFL, which is a genetic algorithm that tests code paths. They are also transitioning to Rust, which will give them a much bigger safety guarantee over most of their code and a much smaller audit surface for the rest.
replies(4): >>22059053 #>>22059115 #>>22059126 #>>22059331 #
Thaxll ◴[] No.22059053[source]
Rust has nothing to do with QA things since most bug are business logic / UI / UX related. QA don't test for those kind of errors.
replies(1): >>22059125 #
mffnbs ◴[] No.22059125{3}[source]
In my experience, that’s the exact sort of errors that a QA team our position tests for.
replies(1): >>22059269 #
1. newnewpdro ◴[] No.22059269{4}[source]
Their comment meant that QA don't test for the kinds of errors (safety) rust protects against.