I think the question "how do I know if I'm good at programming?" is a non-helpful question if the ultimate goal is introspection or diagnosing professional deve

I think the question "how do I know if I'm good at programming?" is a non-helpful question if the ultimate goal is introspection or diagnosing professional development. Any mentor who hears such a question should absolutely take the time to get the asker to pull back and re-think what they're really asking, rather than dive-in and start giving specific pseudo-objective advice about "code". First, it is far too broad. What does "good" mean? Good enough? The opposite of bad? Compared to whom? And even "programming" is a ridiculously vague thing-- everyone who has worked even a year in the SW development profession will know that programming is only part of the job and that there are many different roles, many different kinds of skills. Next, what is the intent of even asking that question? What can one do with "the answer"?