I have a similar one for myself, let me scan in it: Front-end ninja 2006-2010 Full-stack unicorn 2010-present Follow me on twitter Times have really changed I guess.
My dad's resume and skills from 1980
131–140 of 611 posts
Re: My dad's resume and skills from 1980
#132Earlier quoted context omitted.
One day, long after I'm gone, people will finally accept that Python and JavaScript are no longer young languages. JavaScript is 26 years old, Python is 31. They both continue to grow in importance year-on-year, JavaScript because there is nothing on the horizon which will plausibly replace it, and Python because a large number of industries and programmers genuinely love it. I think there's a nontrivial chance they'…
Why did Python win the war with Ruby? Was it purely the math community deciding this is where we throw our weight and left Ruby the runt of the litter?
Why that all happened, IDK.
I write that as someone with a soft spot for non-Rails Ruby (after much consideration and repeated encounters, I kinda hate Rails). But it's rarely the best choice, unfortunately.
Re: My dad's resume and skills from 1980
#133Earlier quoted context omitted.
I've been reviewing a lot of resume's lately that call out the candidate's exact date of birth and marital status. Many even call out their parents' occupation. I've seen more than one that say "Mother's Occupation: Homemaker" . Although I now realize this is a cultural difference issue, it caught me off guard at first.
> Many even call out their parents' occupation. Are those German resumes? Very odd. Can't be used for anything except discrimination.
(German resumes frequently do have familial status though, and of course always with the fucking photographs...)
Re: My dad's resume and skills from 1980
#134Earlier quoted context omitted.
Why did Python win the war with Ruby? Was it purely the math community deciding this is where we throw our weight and left Ruby the runt of the litter?
It's funny, you don't hear much about the Python/Ruby war anymore. Python was more of a general purpose language and had decent web frameworks (Django and Flask primarily). Ruby's main claim to fame was, and still is, Rails. Rails has lost a bit of steam over the years, partly due to node.js and the microservice revolution, so to speak. If anything, Sinatra is a better fit for microservices and yes, sure microservice…
Re: My dad's resume and skills from 1980
#135Why does he call out that he is 5'4" I wonder? The "Health: Excellent" seems amusing in today's context too.
I've been to a military museum few days ago and I was surprised how incredibly small some of the cockpits are. I'm 6'3" and wouldn't fit in most of the fighter jets and other vehicles. Not that I wouldn't be comfortable with my legs pushed to something - my shoulders are literally too wide to get in, my thighs/ass are too wide to even try sitting there. Might be a problem for aerospace tech. And don't get me started…
Re: My dad's resume and skills from 1980
#136It is so simple. There's no "Experienced software architect with a proven track record of delivering high quality and performant blah blah blah" shit. What were the interviews like back then?
> "Experienced software architect with a proven track record of delivering high quality and performant blah blah blah" What's wrong with that? Each part of the phrase sounds like something an experienced developer should strive for, and is objectively testable (e.g. delivered projects in a work setting or not, well-written code or not, the software runs quickly or not, etc.). Junior developers in particular may lack…
You said it yourself: "Each part of the phrase sounds like something an experienced developer should strive for". Nobody will ever write the opposite. So it signals nothing.
Re: My dad's resume and skills from 1980
#137It is so simple. There's no "Experienced software architect with a proven track record of delivering high quality and performant blah blah blah" shit. What were the interviews like back then?
> "Experienced software architect with a proven track record of delivering high quality and performant blah blah blah" What's wrong with that? Each part of the phrase sounds like something an experienced developer should strive for, and is objectively testable (e.g. delivered projects in a work setting or not, well-written code or not, the software runs quickly or not, etc.). Junior developers in particular may lack…
Back in OP's Dad's day actual humans who actually cared looked at every resume and more often than not treated the interviewee like a human. For us, we just get fed into a machine and if we make it out of it maybe a human will glance at it.
Re: My dad's resume and skills from 1980
#138> My dad is 92 and we just put him in a home. Can you stay healthy enough to die of old age in a regular home? “Put him in a home” sounds so ominous and forceful.
If anything I suspect dying at your home would be easier if you weren't very healthy.
Re: My dad's resume and skills from 1980
#139Earlier quoted context omitted.
> Many even call out their parents' occupation. Are those German resumes? Very odd. Can't be used for anything except discrimination.
I've looked at a ton of German resumes and never seen this. Only once on someone from (and at the time of writing, in) South Asia. (German resumes frequently do have familial status though, and of course always with the fucking photographs...)
Re: My dad's resume and skills from 1980
#140Earlier quoted context omitted.
Up until the mid-late 2000s tech interviews consisted of a few conversations, followed by checking references. CS trivia interviews were largely introduced by Google, with other companies cargo culting that into their interview practices.
I've brought that culture back in our company. Hasn't failed us yet. Turns out for a CRUD web app you really don't need top hackerrank skills. In my humble opinion, people who excel in algorithmic code interviews want to overcomplicate everything and get burned out super fast with 'real world' tasks.
I think a far more likely explanation is that lots of interviewers are very bad at interviewing, and that interview anxiety, especially given the kind of shit that gets thrown at you in programming interviews, is a lot worse and more widespread than one usually supposes. Result: interviewers are convinced they're constantly catching "frauds" that they couldn't have caught otherwise, but they're frequently wrong about both those things—that the person was a "fraud"; that the interviewer couldn't have caught actual "frauds" with an ordinary interview.