Live data from Hacker News

My dad's resume and skills from 1980

github.com

201–210 of 611 posts

Re: My dad's resume and skills from 1980

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

My experience from around 2017: Today's employers just don't like good simple resumes for some reason. They expect you to be a graphic designer to even look at it. I had a clearly formatted, simple resume and had a 0% success rate (besides one offer for 30k which was an insult) after hundreds of applications coming out of college to places far and wide or local, until a recruiter for a consultancy company cold contac…

There are many problems with your resume, and lack of fancy design is not one of them.

- Half of your CV is empty space

- Dates are formatted really badly, no one would be able to get a good grasp on your project and work timeline quickly

- You have a game project that spans several years, and you sum it up into one sentence. Why are you doing that? It's one of your main selling points, and you don't expand enough on it.

- The prioritization is not sound. I'm reading about your proficiency with vim (pretty much irrelevant) before I even know your work history.

- You mention Linux administration. That's pretty broad. You should specify more. Did you deal with network config? systemd? FUSE?

Overall your resume looks lackluster, unprofessional and bare-minimum. It's been more than 7 years now, and you still see nothing wrong with it? Sorry if that sounds harsh, but I'm doing you a favor by giving you a reality check.

Re: My dad's resume and skills from 1980

#202

Earlier quoted context omitted.

The libraries. Ruby has Rails. Python has... everything else (plus Django, so it also kinda has "a Rails"). You'll likely be using something less well-maintained and shakier if you use Ruby outside of Rails stuff, than if you'd picked Python. Python's basically the modern Perl. 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…

I genuinely love Python. Not in a shallow feature-to-feature way. But deeply that it has enabled a career and provides a livelihood to me and my family. It puts bread on the table. It taught me how to program and it taught me the power of computers. Life changing tool. No other tool in my house comes close to what computers + python has done in my life.

Oh, I like it too. It's got problems like most languages that see any actual use, but it's totally OK, even good. I didn't intend my post as a put-down of Python, so if it came off that way—whoops, not what I was going for.

Re: My dad's resume and skills from 1980

#203

Blue collar mechanical work during the war, used the GI Bill to get some college, went right to work for IBM, probably recruited by big blue. The Greatest Generation had both the worst and the best.

Looks like he also got quite a bit of training at what I assume is UCSD Extension program. I received a certificate in C programming from there in the early 90’s. I wonder if they still offer similar programs today.

It would appear so, albeit now it's an online program: https://extendedstudies.ucsd.edu/courses-and-programs/c-c-pr...

Re: My dad's resume and skills from 1980

#204

If the minimalist resume is appealing, can we also bring back walk-on hiring? In warehouse and construction work, if someone shows up at 7:30 AM on a Monday morning, odds are quite good that the foreman will have something for them to do. Maybe not that day, but maybe tomorrow, or maybe someone on the list above them won't show up that week and they'll get called. I made rent doing that in my early 20s and they even…

> bring back walk-on hiring?

This make sense for highly productive labor, that foreman hiring people for just showing up generally got a positive expected return for this. In fact, this is still how a lot of (sometimes illegal) day labors go about getting work: truck comes by, picks up people ready for work, work get done and everyone makes money.

> Why again does boutique startup need to interview 500 overqualified people?

Because these startups lose money as a matter of principle. The people working there aren't actually performing productive labor. All of that hiring is about creating a large illusion in the market place.

Most of my labor has gone to waste. More projects than not never ultimately shipped, but even the most valuable projects I did, still made money for companies that ultimately lose more money than they take in. Many of my best projects are for SaaS companies that don't exist any more.

The guy picking up a bunch of people in the back of his truck is about to go build something real and is going to get paid in cash, and the more people he can get in the back of the truck the more jobs he can get done in that day, which means more cash for everyone (and if you're on the paying end, it means that project you wanted done is done faster).

> It's just business for crying out loud.

I don't think this has been true in tech for over a decade. I had a COO once excitedly proclaim that if the company made more money than it cost to run, we would have unlimited runway. The COO seriously thought he had stumbled upon some brilliant realization about a company making more than it costs to run.

The guy with the truck knows far more about business than most execs at tech companies today.

Re: My dad's resume and skills from 1980

#206
post #156

Earlier quoted context omitted.

then why isn't construction automated? i think if your company's processes are so specialized and nuance, you should really take a step back and ask if they should be.

Are you saying the fortune 500 are bad at business?

A. Bank caused the financial crisis of 2008

B. Are you saying top banks are bad at banking?

Re: My dad's resume and skills from 1980

#207

Caught my eye: Listing gender, height, health on the resume (!) Can’t imagine getting a resume with that info these days. Listing corporate training under education. Again, wouldn’t expect to see that today. Not sure if that is because no one does employee training anymore, OR, if it’s just expected and understood that you’ll learn new stuff constantly as a programmer these days.

Perhaps not in the U.S due to labor laws and the EEOC, but in some countries you must also attach a head shot. Not only that, but HR can casually drop by your house unannounced to inspect your living conditions and make a note of anything "unusual". I know it sounds straight out of Severance, but that's how things would be stateside if unions and others hadn't drawn the line somewhere.

Re: My dad's resume and skills from 1980

#208

When I first entered the working world as a programmer and administrator of an "academic computing center", in the early 70s, you met men like Ray - ex-military, GI-bill educated, learned computers from the electricity on up in their mid-career, rather frequently, either as customer engineers for one of the big mainframe manufacturers (there were 7 or 8, depending on when and how you counted), or from the minicompute…

> even the people who taught it were still just learning it.

Still true today.

Re: My dad's resume and skills from 1980

#209

When I first entered the working world as a programmer and administrator of an "academic computing center", in the early 70s, you met men like Ray - ex-military, GI-bill educated, learned computers from the electricity on up in their mid-career, rather frequently, either as customer engineers for one of the big mainframe manufacturers (there were 7 or 8, depending on when and how you counted), or from the minicompute…

It reminds me of "Mel"in 1983 which was in response to "Real Programmers write in FORTRAN." https://www.cs.utah.edu/~elb/folklore/mel.html

> the IBM salesmen stood around talking to each other. Whether or not this actually sold computers was a question we never discussed.

Re: My dad's resume and skills from 1980

#210

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?

Growth of data science and AI/ML saved Python from being over leveraged on web dev backends. I’d say also it was more at war with node until data science took off.

Node didn't even exist yet when python and ruby were in competition.
Post reply on HN