561–570 of 611 posts
96 years old and still cooler than the current kids. Who else can say they used a computer with two ROUND screens?
Unfortunately he passed away shortly after [1] but your point stands. [1] https://github.com/runvnc/dadsresume/issues/1#issuecomment-1...
96 years old and still cooler than the current kids. Who else can say they used a computer with two ROUND screens?
If Moto 360 smartwatch counts as a computer, I used two.
I am looking at https://www.panelook.com/VLT236-RDP-600-23-6inch-848x848-ROU... right now and thinking about making something cool (the resolution is crap, sadly)
Earlier quoted context omitted.
We probably are close to the same age. My dad was an engineer who also learned to program FORTRAN in the 70's. When I asked him a similar question his reply was (quotes are paraphrased): "It was way too tedious to do. You'd spend hours getting the cards just right. We used to put them in a shoebox and mark them with a pen in case we dropped them on the way to the lab. Then you'd wait until the next day to get your re…
I enjoyed programming in the 90s and early 2000s but I feel it’s turning again into tedious grunt work with scrum, agile, yaml configuration files and needlessly complex systems.
I'm not trying to denigrate you in any way, I myself switched from working at $BIG_BANK to a more lithe type of company and 90% of that bullshit went away.
Agile + Scrum stuff are minimal and now consume ~4.5% of my week instead of ~12.5%, I'm not spending half my "dev" time babysitting and maintaining giant applications no one really understands in full, and instead work on a bunch of little serverless applications, maybe half of which I do actually understand and can explain end to end.
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…
> My dad is 92 and we just put him in a home. Can you stay healthy enough to die of old age in a regular home? “Put him in a home” sounds so ominous and forceful.
Well, joke’s on her, she’s still alive at 70 and I survived my first bout with cancer at 36 already so she was wrong on two counts. Still didn’t put any elderly family in any home though…
Earlier quoted context omitted.
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…
I'm not sure I'd even interview this person; I'd at least have to find reasons to. It definitely doesn't give me anything to ask about. Quotes like "Save a lot of time by automating an email process" are so vague and ambiguous that the bullet point may as well be omitted. Education on the top is a waste of most anybody's time, let it be on the top only if you have no work experience (and if that's the case, yikes). I…
... are you kidding with these two sentences side by side? you just answered your own question, ask about the email process! and how is that outline of what I did even that vague? and everyone says to list accomplishments that benefitted the company instead of responsibilities, which this is a perfect example of.
I'll hopefully never have to write a resume again but if I have to I'll just pay an expert. The way I instinctively read and understand a document by actually reading it and caring about the content first is just too mismatched from the average neurotypical's way of looking at the world for me to empathize.
Earlier quoted context omitted.
Mine is still plain text. Basho at least found that charming.
Mine too - works for programming gigs - also, searchable. https://vazor.com/resume.txt
Earlier quoted context omitted.
> As will some version of /bin/sh I hope not! That's one of the things I pray every day to go away. (Even I don't believe in any gods, and am a Linux-only user for the last 20 years). The Unix shell language is one of the most horrific legacy technologies that are still around. I really wish it dies soon™ and gets replaced finally by something sane!
It won't because it's too close to human interaction.
UIs changed in the past, and still change the whole time.
Why would shell be any different?
Earlier quoted context omitted.
The backdoor into CMU back then was and maybe still is Pitt. Pitt students had the privilege of signing up for any CMU course and it just meant a slightly longer walk to class.
The Cognitive Linguistics degree at CMU in the 90's was an interdisciplinary combination of cognitive science, neurology, computer science and linguistics, and disappeared when the faculty member that created and sponsored it passed away in the mid-1990s. While Pitt is a quality university, I don't think they offer degrees from CMU. Pitt was on my radar and one of the few places I was accepted to, but out of state tu…
That job market seems like so long ago. See job ad, type out a letter with your CV, wait for them to write back, somehow organize a time to meet, more rounds, and so forth. At least it must have been hard to spam out CVs. The guy seems pretty hardcore from my perspective. University training for all those techs. Of course hardware back then cost a lot of money so you wanted people who knew what they were doing. What…
The last time I was hired for a purely software-related position was 1993. They were looking for an IC (they didn't call it that, then) who would quickly transition to tech lead / system architect. The technical part of the interview involved role-playing myself presenting an initial proposal to a potential customer who had provided a brief written requirement. One of the interviewers role played the customer. IIRC the interview schedule was something like 30 mins to read the requirement and think, 15 mins to ask initial questions, an hour (perhaps longer?) to develop the proposal, an hour (?) to present it and face customer questions.
In essence I was being asked to spot ambiguities in the requirement and develop an initial estimate. I passed. I would have failed had I applied for the same job straight out of uni.
