Thanks dwbit. Obviously there’s no answer other than that, that you can give as a Bitwarden Employee. I’d have to say the same thing, if I was in your position.
But your developers on 3 separate occasions have released bugs showing they can’t even make sure a preference file has it’s values properly and permanently saved in the extension config reliably…and I’m supposed to assume they’re capable of regression testing, race condition testing, identifying buffer overflows and all the other much more complex tasks needed to produce secure code? Stretching incredulity is just the tip of that hypothetical iceberg.
@grb total props to you and all your efforts on the community forums…you do a great job not sure how you keep it up! ![]()
I have worked with at least 5 different dev teams over the last 30 years, developing documentation, handling tickets and end user support and have done QA in the past myself so I understand the struggle of herding developers, AND projects, AND release timetables. I also understand you’re developing inside multiple other environments (chromium with it’s infinite “chrome” shells (chrome/edge/brave/comet/etc), and Firefox/Gecko and whatever it’s wrapper language is) and they’re constantly changing their codebase under Bitwarden as you’re changing the extension. Bitwarden has a very hard CS problem. And I won’t go into the poor planning/implementation of your major UI rework…what was that, 1-2 years ago? End result wasn’t too bad, but your transition/no planning/major change in functionality the way you did it left much to be desired. Half of my deployed base had constant questions because everything had changed and they couldn’t figure out how to use the new version. Either there wasn’t an experienced UI/UX expert involved in that process, or they were ignored because the devs thought they knew better.