The bitter-sweet taste of humble pie.

I had the privilege of a very long talk with my skip boss. What started off with niceties about skiing quickly moved to discussing a major problem at work.
Earlier this week we discovered a necessary change to the database required to move forward with what had been a trivial value-add in our app. The change required was to modify the format of a "God property," a field from which all the downstream metrics are derived. What was a four-week project is now a four-week project that will only go live after a four to sixth month project. He is not amused, he is "concerned."
He is concerned because I failed to appreciate that this change has system-wide effects. While I am not expected to understand the entire system, no one can, I also am expected to seek out to domains experts, which I did not do. I had my reasons -- mere excuses -- and clearly I should have considered this.
Furthermore, we had a meeting to discuss this smaller project and get the green light from our product board to start working. He was discouraged that I didn't push back against product and delay the "green light" meeting until I had a full understanding of the data change. I fully concede this was a moment of weakness and oversight on my part.
While my ego feels bruised, I want to be perfect, I am grateful to have this person in my work life who holds me to a higher standard. I have the choice to consider this as criticism, and wallow in self-pity, or see that he is giving me his time to point out my blank spots and help me be a better contributor and leader.
Constructive criticism is not enjoyable but it is invaluable.