It depends on what you mean by password managers and trust. If you have an application that you trust (be it track record, inspection or known-good controls),

It depends on what you mean by password managers and trust. If you have an application that you trust (be it track record, inspection or known-good controls), and that application happens to also be a password manager, then the trust in the manager itself should be fine. If, however, you use a third party service, i.e. something managed by a company that holds your data, that is a different topic because you're talking about trusting a company. A password manager can be KeePass on your local FDE storage medium. A password manager can also be a web app hosted elsewhere. It can also be both. You can even mix it up and have the storage medium be remote storage in stead of local storage. If you currently have a file called "passwords.txt" stored in a public S3 bucket, that would be your 'own method' but would that really be good? Or perhaps you have an RSA-wrapped AES-encrypted spreadsheet you store locally with no back-ups, also possible. Too many unknown parameters. At the end of the day the solution that gets you strong unique passwords per entity in a way that you don't lose access to personally but also don't give unwanted access to towards third parties is better than not having a solution at all. (this includes physical paper password books, those are 'unhackable' after all)