Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This right here. We often talk about "Communication skills". This isn't separable from "being able to describe a problem or solution using standard terminology".

It's no less important to know what common things are called, than it is to know how common things work.

There is no brighter red flag to a than people who just "gets things done" or "solve problems in unorthodox ways", so a candidate who describes themselves as a problem solver that might not know all the "words" for it is to me a big red flag. This isn't gatekeeping or saying everyone needs a CS degree to be a decent developer. Terminology is a trivial addition to the skillset and ignoring it just means one doesn't care about communication.



...and then, there's spending 27 years, working for a conservative Japanese corporation, where they don't know the jargon (but are seriously good engineers). I learned to make things fairly clear, without jargon, and deliver very maintainable code (I'd have been fired, otherwise).

Listen, I understand that researching people before we insult them is passé, but I'm a really good co-worker. I wrote the above in a manner that was all focused on me, not anyone else. I am sad that you saw it as an opportunity to attack.

Maybe we would not get along IRL, and that's fine (but sad). I've spent my entire adult life, working with some of the most difficult folks on Earth (not in the tech industry). I have learned that we all have a story, and we all have value.

If the only way that we can measure our personal worth is to compare it favorably against others, I can't help, there, except to say that it didn't work for me.

YMMV




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

Search: