Live data from Hacker News

My dad's resume and skills from 1980

github.com

111–120 of 611 posts

Re: My dad's resume and skills from 1980

#111

Why does he call out that he is 5'4" I wonder? The "Health: Excellent" seems amusing in today's context too.

My first real job was 1986: Having a "stable" personal life was something employers would "need" to know. And god help you if there was a gap on your resume; it was advertising your deviancy.

Such attitudes all changed drastically just around that time, not in small part because the demand for EE and CS people started outstripping the supply.

Re: My dad's resume and skills from 1980

#113
post #22

The interesting bit about this post is that with that resume, you can still feed a family in 2022 (okay, you won't need any assembler, and one from the set { Fortran, COBOL } will do). I wonder if Python and JavaScript will get you that far 50 years from now?

> I wonder if Python and JavaScript will get you that far 50 years from now?

AngularJS itself singularly powers surprisingly large number of Enterprise applications. So even assuming the unlikely scenario that those languages are dead, and the only useful work is from dinosaurian companies who was too slow to switch, the answer would still be yes. :)

Re: My dad's resume and skills from 1980

#114
post #22

The interesting bit about this post is that with that resume, you can still feed a family in 2022 (okay, you won't need any assembler, and one from the set { Fortran, COBOL } will do). I wonder if Python and JavaScript will get you that far 50 years from now?

I've been writing code professionally for over 25 years now (and I'm 49). I feel like I could keep writing code for the rest of my life. 50 years doesn't sound like that long.

It's not.

Hug your parents, spend time with your family. If you must code, do so on something you really feel strongly about from here on out.

Re: My dad's resume and skills from 1980

#115

Earlier 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?

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 microservices aren't a perfect fit for all use cases, but they do exist now and are reasonably popular compared to when Rails first came out.

Additionally, Python made significant inroads as a teaching/academic language and a scientific/math/ML language.

Way back in 2004, I had been using C/C++, Java and Perl and was ready for something new and useful. I'd heard about Ruby and Python at that point and tried both. Ruby felt too much like Perl for my tastes (no surprise, it's kind of like OO Perl) and while I didn't love the significant whitespace in Python, it just looked cleaner and simpler to me.

I have been using Python off and on ever since. I have worked with Ruby a bit as well. What's funny is that they are fairly similar and I've long argued that the two language communities would be better and stronger if they "joined forces".

But of course people have strong opinions about programming languages. Myself personally, I like Python a lot more than Ruby, but I've been using Go for a few years now and it's my current language of choice.

Re: My dad's resume and skills from 1980

#116

Earlier 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?

Python is easier to use if you come from a C/C++ style coding background.

Could you point out specific parts of python that are easier for someone with C/C++ background as opposed to Ruby? I remember starting with Ruby (after rudimentary CS50-level C), and finding it quite reasonable and logical, and nicer than python. I still think it's nicer than python, although I've long since stopped using it.

Re: My dad's resume and skills from 1980

#118
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...

Also: I kind of like the concise wording when the writer doesn't feel they need to adhere to STAR. "Duties Included" is the only meat I want to see when I read a resume. I don't care what the specific challenge you faced was, or if your hard work transforming protobufs from one format to another resulted in "23% year over year revenue growth and 3 industry awards" for a product that uses your protobufs 5 layers up th…

I've had the opposite experience--if you don't list accomplishments you don't get a call back. Job duties alone are considered an insufficient resume.

Re: My dad's resume and skills from 1980

#119
It's sad how a fraudster can abuse knowing a persons full legal name, date of birth, past home address and phone number. All of which was on this resume posted to the internet, and should probably be masked out.

As an aside: loved reading the resume.

Re: My dad's resume and skills from 1980

#120
post #84
post #52

Earlier quoted context omitted.

I’m assuming you’re concerned with resume manipulation? Or is there another reason you prefer to submit your resume in a non-editable format?

Yep, I've been surprised by the contents of my resume at an interview set up by a recruiter once. "It says on your resume you have extensive experience in X." "I do not." They also have a thing for stripping your name and contact details out and pasting their ugly letterhead over the top. Which I suppose they could still do with a PDF if they have Acrobat Pro.

They only "came across" your résumé -- similar to how San Franciscans come across turds. 99 times out of 100 they didn't even bother to read it.
Post reply on HN