I can definitely relate. I feel like we're in this kind of phase with dev.to a bit. Of course, a/b testing can solve a subset of the issues you are describing. But it's definitely not something you can rely on to solve all your problems.
I have more questions than answers, like you, but trying to establish some principles can help. Like, having a principled idea that the users will never use all the features so we should question adding more vs putting more work into existing ones. That might be a bit contrived, but finding things you can lean on to make consistently good decisions can go far IMO.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can definitely relate. I feel like we're in this kind of phase with dev.to a bit. Of course, a/b testing can solve a subset of the issues you are describing. But it's definitely not something you can rely on to solve all your problems.
I have more questions than answers, like you, but trying to establish some principles can help. Like, having a principled idea that the users will never use all the features so we should question adding more vs putting more work into existing ones. That might be a bit contrived, but finding things you can lean on to make consistently good decisions can go far IMO.