21 karma · joined October 8, 2012
You should trace how major features or specific functionality actually works according to what the code does (trace all paths and weird edge cases and bug scenarios), then present that this is how 'x' actually works, and if the customer wants to do 'y' here is what we have to do to make it work. You have to take initiative to do deep dives without someone telling you what to do or hand holding.
Then when your PM or manager discusses adding new features you'll know what scenarios can break or need to be re-tested. Everyone else will have no clue and then they'll naturally start asking and looking to you for handling and leading maintenance and new features.
I asked them to delete my account a couple years ago as well and they never did then either.
I will never, ever trust this company or use their product. There are other options out there just as good and not sketchy.
PS I like how the email went out on a Friday night too, even more sketch to try and limit # of people who opt out.