Product ownership 101
Product ownership 101
“What’s the error message?”
“I don’t know, isn’t that your job to figure out?”
“No sir/ma’am/other honorific
My job is to figure out what the error message means and how to repair it.”
Sounds like you should respond to that with a 400 Bad Request
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Id ho with
415 Unsupported Media Type
or
426 Upgrade Required because it’s clearly the wrong protocol
Booleans have potentially infinite return states depending on error handling
Is this why a bunch of us senior engineers have been forced into a product owner role?
Because we can somehow deal with string parsing better? Jesus fuck we’re doomed
“Have I done well?”
HTTP status: 200 HTTP data: “{‘status’: ‘error’}”
"JAVA solves this problem by …"
Sometimes.
In those cases, “there isn’t a yes/no answer to your question because…”
I ask my jrs simple yes/no questions all the time.
Did you open a PR? Does it pass the CI pipeline? Did you write a test for scenario X?
I’m here to help you, but my time is unfortunately limited. If it takes half of our available time just to drag out of you where you’re at we’re all worse off for it.
the string:
“Yeah, no.”
I feel this. I’ve found that a good response in those circumstances is to say “sorry, can we put a pin in this? I feel like I don’t have the capacity to properly process what you’re telling me right now, so I’d rather we resume this conversation at a later point. Thanks for helping me figure out [bool question] though.”
It’s a useful response if one genuinely is interested to learn, but not at that moment.