Ask HN: Where can you apply for a programming job when you are a Class A asshole
I don&#x27;t understand why this is so hard for so many programmers. As the person frequently on the other side of the table, I can tell you this process is pretty easy to get right.<p>Engage with the question. I&#x27;m asking it for a reason; you might think it&#x27;s stupid, but I wouldn&#x27;t ask if I didn&#x27;t care what your answer was. You can tell me you think it&#x27;s stupid, but even better would be to _answer_ the question then _ask_ why I want to know.<p>If the technical problem is easy for you, then demonstrate that it&#x27;s easy. I actually don&#x27;t care if you solve the problem (and very few interviewers I&#x27;ve spoken with care either). I care that you can think through a problem, articulate your thought process, and then explain to me the solution you&#x27;ve arrived at.<p>Software development in a team setting is a collaborative process. That collaboration often manifests itself through answering stupid questions, writing pseudo-code on a whiteboard, explaining why your code does what it does, and asking others (politely) why their code is the way it is.<p>The longer I do this work, the more convinced I become that the software part of it represents less than 30% of what makes a good developer, and the interview is not to find the programming savants, rather to weed out people who will make working on a team a nightmare.