Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My dad's resume and skills from 1980

github.com

Post reply on HN
Print view View original

231–240 of 611 posts

Re: My dad's resume and skills from 1980

#231

Post by dsr_ »

lake_vincent wrote: post #229
dsr_ wrote: post #124

Earlier quoted context omitted.

I see obviously not-the-original resumes from basically every recruiter. If you tell a recruiter "we need someone with senior FOOlang experience", the next day there will be six resumes, one of which has an organic "brought in FOOlang to orchestrate object frackers, reducing development time" and five of which have "N years FOOLAND" inserted into a Skills section in a different font.

This is interesting...what do you suspect is behind this? Do recruiters just tell candidates "Hey, make sure to put FOOlang on your resume before you apply to this job."

No, I'm strongly implying that many recruiters will just change resumes with minimal regard for the truth. Note the difference between FOOlang and FOOLAND, among other things...

Re: My dad's resume and skills from 1980

#232

Post by mattbillenstein »

macintux wrote: post #230
rmnclmnt wrote: post #6

Can we bring back this form of resume, please? Information is clearly organized, easy to read, easy to remember. No need for 5-star skills ratings, dual-colored backgrounds, unreadable fonts, and whatnot...

Mine is still plain text. Basho at least found that charming.

Mine too - works for programming gigs - also, searchable. https://vazor.com/resume.txt

Re: My dad's resume and skills from 1980

#234

Post by morelisp »

chrisseaton wrote: post #198
zwaps wrote: post #196

Earlier quoted context omitted.

Family info in this context means whether you are married and have children or not

What relevance does that have to do on whether you can do your job or not, though? And here's another example of specifically parent occupation: https://qz.com/1055416/americans-would-be-shocked-by-common-...

While that site is basically correctly, "not that long ago" should be interpreted more like "within post-war era", not "a few years ago".

Photo yes, Familienstand yes still today for conservative companies, parents occupations not since probably the 80s in most places that would consider foreigners at all.

(It is, as you say, all fairly obvious bullshit designed to make sure the right social class gets preferential treatment...)

Re: My dad's resume and skills from 1980

#235

Post by gsich »

chrisseaton wrote: post #198
zwaps wrote: post #196

Earlier quoted context omitted.

Family info in this context means whether you are married and have children or not

What relevance does that have to do on whether you can do your job or not, though? And here's another example of specifically parent occupation: https://qz.com/1055416/americans-would-be-shocked-by-common-...

Paid parental leave maybe?

Also if you have children you might be absent because they are sick and whatnot.

So yes probably discrimination.

Re: My dad's resume and skills from 1980

#236

Post by scruple »

nsxwolf wrote: post #162
insightcheck wrote: post #130

Earlier quoted context omitted.

> "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…

Well, I don't think there's necessarily anything "wrong" with it (It's actually from my own resume), I just cringe when I read it. It reminds me that I operate within a world obsessed with jargon and eye-roll inducing business speak. It all feels so unnatural to me.

When I see things like that on a resume I instinctively smell bullshit. Right or wrong, that's my reaction. "Proven?" Show me the proof. "High-quality and performant?" I better not be able to quickly and easily find end users complaining about your companies software.

Re: My dad's resume and skills from 1980

#238

Post by lelandfe »

ndr wrote: post #161
dspillett wrote: post #99

Earlier quoted context omitted.

> people will finally accept that Python and JavaScript are no longer young languages > JavaScript is 26 years old, Python is 31 I can't speak for Python, but Javascript has changed¹ massively in recent years, more so (I expect) than Fortran or COBOL every did in their active history. It could be argued that what we have now is a younger language with the same name. > but I'd bet my bottom dollar that they'll at leas…

> but Javascript has changed¹ massively in recent years Does anyone have any good resource to learn modern JavaScript? Not any of the weekly js framework, but the updated language, capabilities and patterns.

I have found https://javascript.info/ to be a good resource for both learning and reference around modern JS. I visit it instead of MDN with regularity for practical examples of JS features.

The grammar can be a bit spotty in places - but it is open source and has gotten a lot better.

Re: My dad's resume and skills from 1980

#239

Post by hondo77 »

gomox wrote: post #144

Whoever can type a resume of that length in a typewriter with no errors I would instantly hire. Such level of attention to detail is extremely rare these days.

Back in the 80s I would type up a resume and make corrections with correction paper (big upgrade from liquid paper!). Then I would go to a print shop and have them make copies of it but on nice paper. The copies would not show any signs of the corrections. The same thing could have been done with the cover letter in this case, since only the date and addressee at the top would need to be changed for each company.

Re: My dad's resume and skills from 1980

#240

Post by marcodiego »

nervousvarun wrote: post #223
marcodiego wrote: post #218

Earlier quoted context omitted.

My father was a physicist. He learned to program in FORTRAN in the university in the 70's. Decades later I, still a teenager, asked him something like this: "Dad, you were a FORTRAN programmer and physicist in the 70's, you could be a very well paid developer anywhere in the developed world... why didn't you?"; he answered me: "I didn't thought this thing about computers would go too far."

We probably are close to the same age. My dad was an engineer who also learned to program FORTRAN in the 70's. When I asked him a similar question his reply was (quotes are paraphrased): "It was way too tedious to do. You'd spend hours getting the cards just right. We used to put them in a shoebox and mark them with a pen in case we dropped them on the way to the lab. Then you'd wait until the next day to get your re…

This is something my father told me too. He said he spent some time writing the code on paper, thinking a lot about it; then when he was somewhat sure about what he had written it was time to punch the cards. He used to leave the batch on Friday and went back on Monday to ask the "computer operator" about results and sometimes the result was "syntax error on line 1."
Post reply on HN