Hacker News new | past | comments | ask | show | jobs | submit login

> 4 whole months?

I didn't state 4 full months. It was however something that I spent my free time researching over the course of 4 months. I also did a lot of other things though :)

>Read about the Dunning-Kruger effect and avoid coming off as overconfident at all costs, when interviewing young developers/technical people that is a giant red flag in my experience.

Don't worry, when doing interviews a bigger risk for me is coming off as too unsure of myself. I like to state my opinion as directly and confidently as I can on HN. Mainly because it's good writing practice and because there's nothing at stake (I care very little if some of the readers on HN get a bad opinion of me because they don't agree with what I'm saying).

> No, that's not an Ad Hominem

It very clearly is an Ad Hominem. He's trying to refute my point by arguing against my person (You don't have the right kind of experience to be talking about this) instead of refuting my arguments on their own merit. This happens often as I'm not shy about what I've done in the past and enjoy saying things that I believe in but that I feel many others don't like to hear (makes for good discussions ... well at least if they try to refute my points)




This is clearly in the fuzzy definition area since your argument is that you have gained enough experience in this area to give subjective life advice, the argument against simply has to involve a judgment of your level of experience.

In the same way that I can't meaningfully ask "am I attractive enough to professionally model?" and respond to every "No" with "ad hominem!", when you bring your person into the argument as support, either implicitly or explicitly, the scope of things classed as ad hominem fallacy is constrained. Ad Hominem's are also in the class of fallacies that can still inform a decision even if, like all logical fallacies, they cannot prove anything.

To exit the pedantic logic argument for a second: That confidence and directness is a good practice, and writing practice and avoiding seeming unsure are great reasons to do it. In my experience if you also use that confidence and directness to preemptively address potential weaknesses in your argument (as in "I know I'm new at this but here is exactly why, in this case, I am right anyway") you are even more convincing.


>your argument is that you have gained enough experience in this area to give subjective life advice

Nowhere do I use my "authority" to try and support any of my statements. I give a list of what I thought are his mistakes and then I go off into giving some advice (the snippet) based on my own (successful) experience doing phone screens.

> In my experience if you also use that confidence and directness to preemptively address potential weaknesses in your argument

I think that is very sound advice. But one my motivating factors is to stir up a conversation. If I leave some of the thorns on, I tend to get more replies as people inevitably find themselves caught up in them and feeling the need to reply :)


haha, well that's definitely true isn't it!




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: