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.
Most likely, someone with the initials "sd" typed out that resume rather than Ray Livesay
My dad's resume and skills from 1980
171–180 of 611 posts
Re: My dad's resume and skills from 1980
#172Earlier quoted context omitted.
If software was so regular like construction, we could automate most of it.
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.
Construction in the US is highly mechanized, the vast majority of laborers have been replaced by machinery.
Re: My dad's resume and skills from 1980
#173Earlier 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.
Python is easier to use if you come from almost any background, programming or not. I believe this is primarily b/c there isn't a lot of "special syntax" in Python, it's all very explicit and common. The same is not true with Ruby.
Re: My dad's resume and skills from 1980
#174Earlier 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?
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 kinda hate Django (ducks). The data model being so intricately tied to the business logic makes it impossible to refactor.
Re: My dad's resume and skills from 1980
#175Earlier quoted context omitted.
I eventually gave up on Word templates and now keep my resume in LaTeX. Neat and organized - not unlike this example only with more detail and nicer fonts :) Occasionally a recruiter will ask/demand I give it to them in MS Word - I've learned it's always a bad idea to give recruiter a resume in an easily editable format.
I just downloaded the MS annual report (don't ask why) which is in Word, naturally, and it was marked "Final" just to discourage / prevent editing. I have no idea how hard it is to get around that, but probably too hard for most headhunters.
Sounds like you dont have a culture where docs with "2022 Budget FINAL v2 - my copy (3).xls" aren't normal :)
Re: My dad's resume and skills from 1980
#176Can 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…
You don't need it to be fancy, you just need to be one step above the raw Word appearance you have there. It's the equivalent of having the same pair of pants but it fits you. But as you've said it's moot now that you have a job.
Re: My dad's resume and skills from 1980
#177Earlier quoted context omitted.
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'm deeply skeptical of claims that you can't suss out "fakers" like this. For one thing, people who were that good at faking could be making a lot more money leveraging that skill directly rather than trying to sneak into mid-paying software jobs. 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 th…
You are right, it happened once, but that's what probation periods are for, in my opinion. Also I'd add we don't hire a lot, so this approach probably doesn't work for places which are hiring a lot of people regularly.
Re: My dad's resume and skills from 1980
#178Earlier quoted context omitted.
If software was so regular like construction, we could automate most of it.
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?
Re: My dad's resume and skills from 1980
#179Earlier 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…
> What's wrong with that? 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.
But as I also wrote, at least one occurrence of this in a resume is still a good signal that the candidate understands what a hiring manager is looking for, and also signals that the candidate isn't totally junior.
If a candidate is totally junior and still writes that they are are a junior an "experienced software architect with a proven track record of delivering high quality and performant..." but fails to back it up, they end up being judged next to people who actually do have this experience.
In that case, it could be better to emphasize the "willing to learn quickly"/"excellent team member"/soft skills aspect to set expectations right, and/or develop better technical skills so a candidate can actually claim that. So, it's only really beneficial to write if you actually do have experience, and thus could be a worthwhile signal to include at least once in the resume to show you're at that level.
Re: My dad's resume and skills from 1980
#180Earlier 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…
The problem is it's already given by the extensive job history. Typing that is just a dance we have to do to get past automated filters that look for keywords. By my estimation we are now in the "black hat SEO" phase of resume design. Soon, not even that will work. 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 ju…
I started doing my MSc in large part to get past automated filters in the aftermath of the dot-com bust. The irony is that I could have left it at that: Just adding "Studying towards an MSc in ..." got me a marked uptick in responses, and recruiters asking about it.