As the founder and CEO of a software development house I can assure you that linking to this article will in no way hurt their chances of getting a job in the future. It shows an intellectual interest in justifying new things rather than jumping on hype trains without thinking through the rationality.
To suggest that being anti-TypeScript would reduce your hireability is to think that everyone must agree with you in order to work together, and that would be a pretty bloody boring place to work I would imagine.
I hire independent thinkers who are not afraid to speak their mind and ask questions. Imagine what the inverse of that kind of person would be and ask yourself what kind of value they would bring to your organisation or team... yikes.
Well, yeah, the job description is to question things, learn things, and change things. I wasn't speaking to the Socratic notes so much - but the arguments (against something new to OP) are riddled with comments that hint at less-than-complete understanding of the platforms (eg: the confusion over targets, modules, etc). That, and the main heading is "it's so complicated".
Together, it paints a picture of someone who a) subscribes to "we do it this way because we've always done it this way" and b) just plain doesn't want to leave their comfort zone.
It would be different if the arguments had stronger foundation, and that's the nature of questioning: Argue what's in front of you, but do so objectively, not emotionally.
My favorite part of interviewing is when I ask "why did you do it that way?" Almost always, that's the deciding moment.
You used k8s for that, great! But why?
Some would say "cause it's cool" and others say "because it enhanced our SLA while at the same time condensing our resource usage and end-of-month bottom-line".
I take the second person in all cases, regardless of what I'd personally do. It shows deliberate, educated consideration of the platform and the spec.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As the founder and CEO of a software development house I can assure you that linking to this article will in no way hurt their chances of getting a job in the future. It shows an intellectual interest in justifying new things rather than jumping on hype trains without thinking through the rationality.
To suggest that being anti-TypeScript would reduce your hireability is to think that everyone must agree with you in order to work together, and that would be a pretty bloody boring place to work I would imagine.
I hire independent thinkers who are not afraid to speak their mind and ask questions. Imagine what the inverse of that kind of person would be and ask yourself what kind of value they would bring to your organisation or team... yikes.
Well, yeah, the job description is to question things, learn things, and change things. I wasn't speaking to the Socratic notes so much - but the arguments (against something new to OP) are riddled with comments that hint at less-than-complete understanding of the platforms (eg: the confusion over targets, modules, etc). That, and the main heading is "it's so complicated".
Together, it paints a picture of someone who a) subscribes to "we do it this way because we've always done it this way" and b) just plain doesn't want to leave their comfort zone.
It would be different if the arguments had stronger foundation, and that's the nature of questioning: Argue what's in front of you, but do so objectively, not emotionally.
My favorite part of interviewing is when I ask "why did you do it that way?" Almost always, that's the deciding moment.
You used k8s for that, great! But why?
Some would say "cause it's cool" and others say "because it enhanced our SLA while at the same time condensing our resource usage and end-of-month bottom-line".
I take the second person in all cases, regardless of what I'd personally do. It shows deliberate, educated consideration of the platform and the spec.