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

341–350 of 408 posts

Re: My dad’s resume and skills from 1980

#341

Post by Justsignedup »

phyller wrote: post #325

Wow, I wish I was an engineer in that era. 25 years at the same company, 3 languages over 13 years. And when he needed to learn a new language he actually went to school for it. I just started a new position, I have to learn at least 2 new languages (on my own time) which I need to be proficient in basically immediately. My very first project was, fix something in this new project which uses a new language, you have…

I got fairly proficient in RoR some years ago. In that I understood most of the magic and was thinking on what is the best ways to design the program for readability / maintainability.

Then I got good at Java + Spring

Then I got good at React + Redux

Now I gotta get good at Python + Django and the damn magic it does.

Next I gotta get good at Scala.

It is frustrating. And I feel that had I spent 10 years in any of those I could really make amazing things in each one. But instead I feel like a generalist. Jack of all trades.

And that's just the last 5 years. Before that was dozens of java frameworks, knowing differences between 4 different databases and wielding sql like a master, and more.

The worst parts are:

- Front-end engineers are looked down upon while I LOVE coding in React + Redux + ES6js. Wish it was TypeScript.

- React changes damn near daily.

- I really want to deeeeeeep dive in a tech but I feel lots of FOMO that if I don't study a hot new tech I'm screwed. (Except Vue. Vue is the same paradigm as Backbone / Ember)

- I have a kid, time is limited to learn new languages.

Re: My dad’s resume and skills from 1980

#342

Post by jxub »

adventured wrote: post #287
metaphor wrote: post #55

If I lived through 3 wars and had a strong career alignment with major defense contractors, I suppose I'd be inclined to disclose health and height out of habit...but was this generally expected on a resume back in the 80s?

Here's the resume of Bill Gates from 1973 (lists height and weight) - https://i.imgur.com/btFE99N.jpg And Paul Allen's - https://i.imgur.com/0pDSVBS.jpg

Height, weight, age and current salary. Yikes.

Re: My dad’s resume and skills from 1980

#343

Post by pinewurst »

otras wrote: post #260

If anyone's interested, I made this resume in LaTeX. I might have to try this out as my next resume template! https://www.sharelatex.com/read/cqscsqsqmskm

My personal custom LaTeX template isn’t that different, but I defined all the sections and items as macros in a separate style so I can keep content and format apart.

Re: My dad’s resume and skills from 1980

#344

Post by technofiend »

MaggieL wrote: post #108
mbrock wrote: post #14

Contemporary programmer: spends a whole weekend tweaking CSS parameters, asking web forums for LaTeX templates, finding a cool fresh font pairing on Google Fonts. 1980s programmer: sits down at the typewriter and bangs out a fixed width table, finishes with a signature.

Real 1980s programmer: sits down at IBM 3278 mainframe terminal, edits resume into text file containing DCF/Script markup. Prints mailing copies on IBM 3800 laser printer using typewriter font, hoping operations staff running printer doesn't notice (unlikely considering speed printer runs at). --signed, real 1980s programmer (also 1970s programmer, 1990s programmer, 2000s programmer, 2010s programmer) current resume…

After getting into the guts of unix's typesetting system I decided to use it for my resume. I customized the macros used for online help called man pages. Man pages have a reference across the top which cite the command and section so man itself reads man(1).

My resume read RESUME(8) across the top. One person got the joke. One. I went back to using TeX until everyone refused anything but a word doc. Mostly so they could take your information off and replace it the agency info.

Re: My dad’s resume and skills from 1980

#345

Post by ninjakeyboard »

Justsignedup wrote: post #341
phyller wrote: post #325

Wow, I wish I was an engineer in that era. 25 years at the same company, 3 languages over 13 years. And when he needed to learn a new language he actually went to school for it. I just started a new position, I have to learn at least 2 new languages (on my own time) which I need to be proficient in basically immediately. My very first project was, fix something in this new project which uses a new language, you have…

I got fairly proficient in RoR some years ago. In that I understood most of the magic and was thinking on what is the best ways to design the program for readability / maintainability. Then I got good at Java + Spring Then I got good at React + Redux Now I gotta get good at Python + Django and the damn magic it does. Next I gotta get good at Scala. It is frustrating. And I feel that had I spent 10 years in any of tho…

IMO You don't need to specialize on a language or famework, but a problem domain, either technical (eg distributed systems, machine learning) or not (manufacturing, video, etc).

It's better to be a good programmer that's deeply experienced in a domain, then a great scala developer that doesn't understand the domains he's working in.

I'm more in the distributed space so I know elixir and scala very well with actor model and distributed coordination tools in my toolbelt. I'm not the best scala engineer but I can get shit done and it will be correct and work through all of the pathological conditions because I've seen a lot in this area. If you asked me to build a webpage I'd fall apart but I'm good at that specialization and have all of the tools I need to work with the technology I know today, and to build on to learn whatever technology is needed tomorrow (eg I've been working with elixir for a year but I'm extremely proficient at it because of my 6 years of akka experience)

Re: My dad’s resume and skills from 1980

#346

Post by notyourloops »

School-Cotton wrote: post #340
gukov wrote: post #335

Earlier quoted context omitted.

The LinkedIn profile is that photo now.

A LinkedIn profile is not the same thing as a resume. I don't look at someone's LinkedIn profile before interviewing them...

Many people treat it that way, though. Personally I don't care for LinkedIn, but apparently that's strange behavior.

Re: My dad’s resume and skills from 1980

#348

Post by gambiting »

phyller wrote: post #325

Wow, I wish I was an engineer in that era. 25 years at the same company, 3 languages over 13 years. And when he needed to learn a new language he actually went to school for it. I just started a new position, I have to learn at least 2 new languages (on my own time) which I need to be proficient in basically immediately. My very first project was, fix something in this new project which uses a new language, you have…

I'm a games engine programmer. I pretty much only know VS and C++, plus some bits of C# for an occasional tool. I feel like what you described is only applicable to Web programmers - my coworker has been at the same company for the last 26 years and he only knows assembly, C and C++, and uses windows batch for scripting. No need to learn anything else - that's enough to build the latest AAA games.

Re: My dad’s resume and skills from 1980

#349

Post by Pokepokalypse »

rmwaite wrote: post #208
quietbritishjim wrote: post #140

Earlier quoted context omitted.

Surely you just means "ops"? I thought the point of someone being "DevOps" is that the developer also does operations, so it would be their own problem. I wonder if that word has become so diluted that its lost the reason that it came into existence in the first place.

Devops is more about dev working with ops and vice versa instead of siloing. That necessarily ends with some crossover of skills but it isn’t strictly necessary

During my brief time in Devops, I have learned that; if you're getting paged at 3am from your server being DDoS-ed, you're not going to be very effective as a developer . . .

Yes: it helps the developer to learn to code much more defensively - which is a very good thing. But then, that developer has no time to code. Defensively, or otherwise.

(depending on the environment, and management's willingness to invest in infrastructure - yeah, you can really get bogged down in this stuff).

Post reply on HN