Is it worth bringing up inconsistent accountability with my director?
retained text
Is worth bringing up to my director or if I should just let it go. Recently, a dba and I were troubleshooting an issue with one of our APIs that dynamically builds database connection strings. After some debugging, I discovered that the user ID and password were no longer being included in the connection string. Turns out my team lead had removed them and was planning to release the changes to production. Without those credentials, the connection would fall back to Windows Authentication. The problem is that nobody on our development team has access to the database server through Windows Authentication, outside of the DBAs. When I asked about it, my team lead explained that we had been audited and needed to remove hardcoded passwords. What confused me was that the credentials weren't hardcoded. They were being retrieved from Azure Key Vault. On top of that, none of this was communicated to the team. The lead dba eventually got involved, and my team lead is now working on fixing the issue. I spoke with the lead dba afterward, and we both agreed this was a pretty serious, especially for someone in a team lead position. The dba also mentioned that it didn't seem like she was taking the issue particularly seriously. I ended that conversation by saying: "We were one release away from finding out how many internal employees and clients have Windows Authentication access to our production database, or finding out that nobody can access our reports and statements features. Either way, that's awful." **Here's where my frustration comes in.** A two months ago, my director called me out during a standup because a project I was working on was taking too long. The issue was that I was waiting on UAT changes to an API that I needed before I could continue my work. On another project, I had my api fail two test cases that me and a front-end dev came up with in our test environment and was told that I needed to do better. What bothers me is that I feel like the expectations and accountability aren't being applied consistently. I'm being criticized for delays caused by dependencies and for test failures caught before production, while my team lead nearly introduced a change that could have broken three applications in our web portal. I've already made the decision to start looking for another job next year, so part of me thinks it's not worth bringing up and I should just move on. Would you bring this up to your director, or would you just let it go and focus on finding another job? EDIT: I learned that the Lead DBA informed the director of what happened.
document fetched 2026-10-31 00:25 · canonical https://reddit.com/r/ExperiencedDevs/comments/1xjq39m/is_it_worth_bringing_up_inconsistent