Genuine question, what does “knowing how to code” even mean? The ability to produce code? With modern resources there’s not a lot of need for practice, technique, or offhand knowledge. The ability to write code (without reference?) Useful for saving time on common problems but how often are you spending time coding the same shit you’ve done before? Feels antithetical to the medium. The ability to read and debug code? Kinda feels like you’re focused on memorized common pitfalls, typos, tests, and abstracting the problems, doesn’t feel right to say that’s “coding”. Maybe I’m just unfamiliar with other people’s workflows.
>>110130367To me, asking a question is communicating a request for voluntarily provided information. As for your comparison, I don’t think it holds up. Someone saying they’re going to ask a question gives you a pretty good idea of what actions they will take submit a request for voluntary information, likely in the language you’re communicating in the moment. Someone saying they’re going to code has far more undefined variables, and those unknowns are what I’m asking about. What do people generally think of when they hear that someone’s “going to go code?” What actions does this look like?
>>110130587You could just say you can’t answer. Or don’t respond, I dunno, anything other than getting angry over nothing.
