201–210 of 408 posts
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.
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?
If you have an active security clearance you're long since accustomed to giving out personal/private information to government bureaucracy (OPM, etc).
Earlier quoted context omitted.
Umm, that time still exists. My resume is exactly like this, just says what I did and doesn't contain BS. IDK what you mean about "logging every second your time" but all government contractors require a daily timecard and did so in the 80s as well (according to my coworkers - I was a kid in the 80s). The reason being was so they know how much time to bill for!! If you wanna work in hip startups then I guess it's dif…
You must be quite fortunate to have such excellent connections amongst the privileged elite, most people will never get past "the algorithm" if they don't stuff their resumes full of buzzwords to even get past some python script. Many companies these days install tracking software on workstations, as well as for programming challenges during the interview process. IBM and defense contractors are known for the good ol…
>I used to work at Ball and was pushed out for complaining about every single face in every single meeting being white
I doubt that's why you were "pushed out..." Or maybe "complaining" was not done in a constructive manner.
(My uncle thinks he gets "pushed out" of all the jobs he's ever had because of some silly reason like this[1] but it's actually because he has poor work ethic and doesn't get along with others. I used to listen to him talk to dispatch when he was a truck driver living with us...uhhh it was embarrassing to listen to...)
Also, I'm a woman myself, FWIW.
[1] stuff like "my boss promoted my coworker over me because she's pretty." That was the last "reason" he had.
Earlier quoted context omitted.
For what it's worth, my resume to this day is still this style. I'm around 40, been in various forms of IT since end of high school. My resume has never been more than a bullet point list of my skills, and my experience. I've gotten almost every job I've applied for based on that + the interview. The few I haven't gotten, weren't because of the resume (I've always asked why, so I could improve).
If you get every job you ask for maybe you are aiming too low.
Looks like a simpler time. You just say what you did. No need to BS it up to sound like you are gods gift to programming. And once you get the job probably no logging every second of your time.
For what it's worth, my resume to this day is still this style. I'm around 40, been in various forms of IT since end of high school. My resume has never been more than a bullet point list of my skills, and my experience. I've gotten almost every job I've applied for based on that + the interview. The few I haven't gotten, weren't because of the resume (I've always asked why, so I could improve).
How do you get a response?
Earlier quoted context omitted.
DevOps engineer will configure docker\tls\nginx and all that stuff
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.
Earlier quoted context omitted.
I'm baby-sitting Java devs as "senior" atm. They don't know much, but what little they know they're defending with fervor, like "REST", Spring crap, and rubbish pseudo-modularization using "microservices". Worst, taking random architecture astronaut blog posts as dogma, incapable of reflecting whether something makes sense for a given task ("SQL is too old-school and low-level (!)"). Makes you really think about what…
I'm sorry, do you have a specific issue with REST or microservices? Like all things, they have their place and purpose. Simply throwing quotes around them and using the fact that a junior dev recommended them as evidence against them is pretty weak, especially here on HN.
Earlier quoted context omitted.
True. However the inflexibility of the physical media (pen/typewriter+paper) forced people to think and plan before they acted. These days, not so much, and I can see the difference in approach when my kids are writing essays - back in the day we were taught to come up with a little plan, toc, etc before getting down to the details. Now my kids just spit it out without structure, then add bits an pieces here and ther…
It's called agile essay writing.