This post has been de-listed
It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.
Hi everyone,
My question is on methodology and where skill level should be. I’m a junior dev 1 year in, very little tech background. I’m competent at solving coding problems and debugging and building new features. Recently I’ve been asked to do more database work in a pretty wild heath insurance solution. I’m talking pretty extreme cursors, cte’s, unions, pivots. I’m trying to learn as fast as I can, but with a code problem I feel like I can always get something working. Not with this.
I had a database problem a week ago, that I figured out where it was going wrong, tested it on our test server, it worked, cleared it with my manager made the update to production. The next day it broke in production, because I had missed small reference in a stored procedure. I’m fine with getting ripped a new one, I can take people yelling at me, it doesn’t phase me. But my boss did that but AFTER she emailed back to the product owner and throwing me under the bus in the email, rather than just saying this was the big and we fixed it, which is what she normally does for other co workers.
Am I wrong for being ticked off at this? Like I said, I messed up by not tracking down any reference and it was fine it test because in prod they’re working with data maybe a month ahead. I own my mistakes. Apologized. I want to get better, but privately I’m irritated. I’ve been a manager in previous jobs and 1. I don’t treat employees like that, and worse mistakes have been made by my employees and 2. My background in SQL was writing selects and joins. Not scripting stored procedures, table value functions and stupid cursors. It’s been sticking with me for a few weeks. Please tell me I need thicker skin and need to get better.
Subreddit
Post Details
- Posted
- 8 months ago
- Reddit URL
- View post on reddit.com
- External URL
- reddit.com/r/learnprogra...