Earlier quoted context omitted.
What are the countries where this is practiced?
I know in Japan head shot and blood type are expected with a resume.
Blood type is weird but in Japanese cultural it's similar to adding your Myers-Briggs type.
My dad's resume and skills from 1980
361–370 of 611 posts
Re: My dad's resume and skills from 1980
#362Earlier 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'…
> there is nothing on the horizon which will plausibly replace it I'm not going to be making any bets - but the one project that has possibility is WASM. A mature, polyglot ecosystem on top of WASM runtimes with web-apis seem like it could displace JS in browser as #1.
Almost no languages run as WASM.
This is not likely to change anytime soon (if ever), as nobody is working on this, and there is even quite strong opposition to get features in that are fundamentally needed to run anything else than the very few languages that already compile to WASM. ("Nobody" is interested in invalidating their investment in JS ;-)).
Also WASM is actually slow, or better said, "it does not deliver its full potential".
It will need advanced JIT compilers to keep up with the other two mayor VM langues. But in this regard WASM is behind around 20 years of constant development and improvement.
My strongest hopes in this regard are currently with Microsoft (even I don't trust this company at all!), who are indeed interested to run their CLR stuff in a WASM VM, and could probably deliver on the needed features. But then, when you would run a CLR-VM (or a JVM) on top of a WASM VM, you know, you're building just the next Matryoshka… There are no real benefits to that besides "look mom, it runs in the browser".
Re: My dad's resume and skills from 1980
#363Earlier quoted context omitted.
For example https://german.dartmouth.edu/opportunities/working-germany/w... mentions family info, which seems bizarre to British and US people, as it's not something a candidate can control, so it seems unfair to discriminate based on this. I know German culture is different of course.
The provided link was fun to read (as a German). Personal highlights: > German employers simply don't know what to make of an Art History major who wants to take a temporary job in an accounting firm before going on to medical school. I'm still laughing. I guess actually nobody knows what to make of an Art History major in the first place. That's one of the typical things one would study if your only plan in live is…
> I strongly hope that we'll stop that madness at some point before our education finally hits the lows of the anglo-saxon equivalent!
Don't British and US universities significantly outperform German universities according to most rankings? I think there's just one Germany institution in the QS top 50 and it's... 50th.
Re: My dad's resume and skills from 1980
#364Earlier quoted context omitted.
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…
If I got this resume from a junior I would hire them assuming the interview went decently.
Half is empty - just graduated, can't expect that much stuff to put there.
Maybe I should have expanded more on the game but I was getting the impression nobody cared that much about personal projects.
The very first two things you do with a resume are match up the list of technical skills with the list of tech in your position requirements, and check the education requirement. That's why those two go at the top.
I'd dealt with a lot of config issues running Debian on various hardware in high school as well as installing it, dealing with apt, understanding chron, a lot of basic things. I don't think systemd was much of a thing yet.
I still fundamentally disagree that the resume is bad. Again, I'd hire this person, and I'm saying that as someone who's done interviews and hired people now.
Re: My dad's resume and skills from 1980
#365Earlier quoted context omitted.
Yep, I blame Microsoft. Now these sorts of interviews are done even by companies writing pedestrian web apps that don't require hard-core CS knowledge. Yet they test every applicant on it anyway.
> Yet they test every applicant on it anyway. If you have enough applicants, why not filter out so you have the best of them? (well, maybe not quite the best, there is some value in having someone less likely to get bored and move on PDQ).
I've never seen any evidence these interviews accomplish finding the best or even a competent candidate.
In my opinion the best interview process involves simply looking at the work history and having a conversation about it. If it sounds pretty good, you go with your gut and hire. A bunch of different people paid this person a lot of money for 5, 10, 20 years and you really think there's a chance they were all fooled? The conversation and your gut figure that part out with a decent success rate.
Re: My dad's resume and skills from 1980
#366Earlier quoted context omitted.
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.
The OP resume looks like a raw typewriter document to me. I don't understand what value it brings to go beyond - it's nothing but a tool to convey your skills and experience.
Re: My dad's resume and skills from 1980
#367If 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…
> can we also bring back walk-on hiring? This used to happen in the 80s. I went to interview at a startup company in Mountain View in 1987. There was some chit-chat then the interviewer asked me to wire-wrap a circuit (diagram was provided) and power it on and connect it up to the logic analyzer - he went away for about 1/2 an hour while I did that. He came back and complemented me on my neatness. Then he took me ove…
Pretty much my interview process. I ask them to program a contains(string, substring), then come back 30 minutes later to code scattered all over the place, sometimes with “// 54 upvotes http://stackoverflow.com/…”, code not compiling, and I’m still wondering whether I should accept them.
I wonder what’s so hard with my interview. 5 years ago, even interns could do it, one of them could even tell the difference between UTF-8 and UTF-16.
Re: My dad's resume and skills from 1980
#368Earlier quoted context omitted.
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…
Ah, I had the same experience as you when I graduated People will offer all sorts of wacky feedback about resumes when prompted, but the real issue is that recruiters just don't look at or care about resumes that much. For my last few jobs I just sent an unformatted text file as my resume, one that would make dist1ll's eyes bleed. The most recent recruiter was actually angry at me for how "unprofessional" he thought…
> You have to network your way into a job.
Not necessarily, but it does make it easier if you have that opportunity. Places like Tata are good for someone with no connections to get a footing.
Re: My dad's resume and skills from 1980
#369Earlier quoted context omitted.
> "I didn't thought this thing about computers would go too far." I almost didn't major in Computer Science because in the late 90s, there were so many negative articles in the New York Times, vis-a-vis software. People don't remember it now, but the media and the culture were utterly hostile towards us, and loved to say our jobs were going to India, that everything there was to know about Computer Science could be s…
You say it like negative articles about Comp Sci/Applied Programming/Really any Tech Co from the NYT is a thing of the past. It's with a sense of irony that articles denouncing Tech is easy, routine clickbait for them now.
Oh yeah, no and low-code is going to put all of us programmers out of work any day now.
Re: My dad's resume and skills from 1980
#370Two thoughts immediately jump out to me:
1. As much proprietary stuff as we still have to deal with, we've really come a long way.
2. The approach that our parents took of working at one company for many years (or a whole career) (and retiring with a pension) really disappeared quickly.