Hexing the Technical Interview (2017)
aphyr.com
aphyr.com
Including a reference to the first 8 hex characters of every Java class. Such detail and prose!
Besides programming suddenly becoming more of a "bro" thing than before, due to the dotcom gold rush, there was sexism that hit close to Java.
Kim Polese was business leadership for Java, but there were sexist slights in the field, like, IIRC, an article in the business press suggesting that she was able to get lunch with anyone because (the article said) she was an attractive woman. Nevermind that Java obviously had monumental promise at the time, both for software development in general, and for the future of the skyrocketing Web, and Polese was arguably the person to network with, if you could.
Here's one quick, incomplete introduction to the environment at the time: https://www.telegraph.co.uk/technology/people-in-technology/...
When that started happening, 0xCAFEBABE felt like something one might've chosen to do differently, had one known all the overt sexism that would be going on, including targeted at one's colleague.
The article references that, implicitly, by making the aforementioned babe male in this story.
However, that vision did not come to pass, so there was no mobile object format. 0xCAFED00D eventually got used in the Pack200 format, which has now also fallen by the wayside.
I think if you were cool in the '90s, "babe" and "dude" seemed like perfectly natural, even rad, ways to refer to people. Particularly if you only had access to hexadecimal digits.
You probably wouldn't pick those terms today, sure.
(grin)
- Your HR department would filter it, as they would check its LinkedIn account and realize the author account has been suspended due to chicky photos ( how unprofessional...)
- Your manager would filter it out, as the author does not have a formal CS Education. Also certainly does not come from a "good university" per Silicon Valley standards.
PS: Kyle if you are reading this...We have a statue of you in every spaceship refueling dock at the Belt!
EDIT: Here we are! https://news.ycombinator.com/from?site=aphyr.com
What’s it mean?
(The writer did misspell it though.)
I'm not sure what rule prefers susurrantial over susurrantal. To my eye, the former appears correct, but I can't explain why.
“So, erm… Perhaps you could tell me a bit about your background?”
He hasn’t read your resume. No man can.
Not necessarily. It gives the applicant a chance to highlight the cool details he did but perhaps can't put on a resume. It gives opportunity for poking more questions. And it is a question the applicant prepared for and can talk about a lot, a good way to "break ice" It's just something every interviewer starts off with and frankly, is a waste of time.
It may be a waste of time for you, but as an interviewer it seriously helps nervous candidates find their footing by starting something that they're super comfortable and confident with. It can be intimidating to jump right into questions without a bit of social lubrication.I normally start my interviews pointing out that we indeed have your CV, so it would be helpful to know how all the pieces came together in your last project. I find the conversational-style of interviewing more productive than the inquisitional-style, and past projects is a nice entrance to deeper questions
EDIT: And in some cases we dont even have your CV. I'm testing a new hiring pipeline where instead of asking for a resume we instead ask a few open-ended questions. This is to see if we can reduce any unconscious bias in the first selection of applicants. In this case, starting with a short summary _is_ new information
A reference to Duke, the Java mascot.