Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My dad's resume and skills from 1980

github.com

Post reply on HN
Print view View original

351–360 of 611 posts

Re: My dad's resume and skills from 1980

#351

Post by lordnacho »

ChrisMarshallNY wrote: post #327
PragmaticPulp wrote: post #165

Earlier quoted context omitted.

> Hire someone right away and let them quit if they want to and hire someone else. It's just business for crying out loud. This is missing the point of interviewing. The goal isn't to find any warm body to fill the chair, the goal is to find someone qualified to do the work who also has a history of doing good work at previous employers. You also don't have unlimited headcount and hiring budget, so it's worth making…

I actually very much agree with this comment. I was a manager for 25 years. A bad "team fit" was not good. I never had a technical failure in my hires, but I did have a couple of "bad cultural fits." These usually weren't toxic people, but people that couldn't handle the responsibilities and pressures (we were a small, high-functioning team, and everyone's visibility was fairly high). But this: > who also has a histo…

I'll second that. I never hired anyone who couldn't do the work. The only times things went badly were times when the person basically didn't want to do the work, due to some personal hangup. No amount of interviewing is going to weed out that guy who can code perfectly fine but deep down is yearning to be a psychologist instead. Like any other job that pays bills, you are vulnerable to paying his bills until they find what they really want.

> In my experience, they just drive out the qualified people that can see projects through, and leave you with ... the ones that are really well-practiced in short, academic exercises.

Yeah beats me how anyone thinks LC is useful, other than for weeding out the most unqualified people, like people who genuinely have never coded. I suppose what it really does is finds you people who are willing to put in the time to study all the hundreds of questions.

Re: My dad's resume and skills from 1980

#352

Post by yieldcrv »

jimhi wrote: post #348
yieldcrv wrote: post #315

Earlier quoted context omitted.

Entertainers still have that capability in many places Offbrand for this site but I’ve seen women audition and work and get paid the same day, this year Is what it is They sign all forms and its W-2 employment some places as well I agree we should reduce friction to that level for more kinds of work, some people are working on that

Can you clarify, are you talking about modeling, standup, acting? What role exactly?

all of the above

the main point is how it is in direct contrast to how other sectors will interview for weeks and months, before any resolution at all, then require negotiating an offer, just to get to a two-week notice at a minimum and then require another 2 weeks to a month to get paid, with deposits taking several more business days (up to 5 actual days) to be available

paid instantly when you realized you might need it, versus paid 4 months from now hoping you planned and forecasted correctly

Re: My dad's resume and skills from 1980

#353

Post by kjs3 »

dspillett wrote: post #99
wyattpeak wrote: post #51

Earlier 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'…

> people will finally accept that Python and JavaScript are no longer young languages > JavaScript is 26 years old, Python is 31 I can't speak for Python, but Javascript has changed¹ massively in recent years, more so (I expect) than Fortran or COBOL every did in their active history. It could be argued that what we have now is a younger language with the same name. > but I'd bet my bottom dollar that they'll at leas…

Yes...Fortran at least has changed a lot since inception. There's been Fortran 90, 95, 2003, 2008 & 2018 standards since to keep up with the various industry fads of the time (You want OO Fortran? Sure thing.). You can get a good overview of Fortran features from inception through the 2008 standard in the paper "The Seven Ages of Fortran" by Michael Metcalf or on the Fortran wiki (https://fortranwiki.org/fortran/show/Standards).

Re: My dad's resume and skills from 1980

#355

Post by kjs3 »

greyhair wrote: post #150
wyattpeak wrote: post #51

Earlier 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'…

Python3 yes, but Python2 will have faded away. Perl! Oh, poor Perl. Python 3, or its children, will be around a long time. As will some version of /bin/sh

Yes, Perl certainly took an odd turn on their 'next gen version of the language' journey, but I'm willing to bet there will be a Perl community running 5.247.2 or some such decades from now, alongside sh, awk & sed.

Re: My dad's resume and skills from 1980

#356

Post by still_grokking »

greyhair wrote: post #150
wyattpeak wrote: post #51

Earlier 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'…

Python3 yes, but Python2 will have faded away. Perl! Oh, poor Perl. Python 3, or its children, will be around a long time. As will some version of /bin/sh

> 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!

Re: My dad's resume and skills from 1980

#357

Post by sgerenser »

mitchdoogle wrote: post #334
hnlmorg wrote: post #280

Earlier quoted context omitted.

Universities are always several years behind the curve. At college in the 90s they were still teaching token ring networking despite Ethernet already being common place. The same college told me that programmers didn’t design any of the code they write; they only transcribe code from flow charts. Just yesterday I was talking to a grad about DevOps. He said the field sounded boring from what he was taught at uni. Then…

It's highly dependent on school. The Ivies, including "public Ivies" will teach you proper comp sci. A lot of other big schools will do you well also. When it comes to smaller regional universities or junior colleges and community colleges, then it's hit or miss. Your intro CS course may be great if you manage to get an instructor who knows it well themselves and wants their students to know it, or you may get someon…

I went to RIT in the early 2000s. I remember the CS and CE departments were quite good (although the prevalent Sun workstations were already getting outdated). Somehow I ended up taking 1 elective from the "Management Information Systems" department and the instructor kept mixing up search engines and web browsers. I think I dropped the class shortly thereafter.

Re: My dad's resume and skills from 1980

#358

Post by dsr_ »

lake_vincent wrote: post #341
dsr_ wrote: post #231

Earlier quoted context omitted.

No, I'm strongly implying that many recruiters will just change resumes with minimal regard for the truth. Note the difference between FOOlang and FOOLAND, among other things...

Woah, that is way more insidious than I was expecting. I get what you mean now, and that just seems really stupid on the recruiter's part. Doesn't it come out during the interview process if there's BS on the resume? But I'm guessing that's your point, right? Because the hiring manager should notice, and the interview process should screen for it, so this must be a symptom of much larger scale dysfunction in the tech…

In the best case scenario, the recruiter called up twenty prospects and said "Quick question -- have you worked with FOOLAND?"

"You mean FOOlang? Yeah, a little."

"And what jobs did you have when you did that?"

"Uh, I learned a little about FOOlang in the job I had from 2010-2012, and then it came up again in the job in 2015."

"Thanks! I think I'll have something for you tomorrow."

And then the recruiter edits "Skills" to include six years of the still-misheard FOOLAND.

Everything else is worse.

Re: My dad's resume and skills from 1980

#359

Post by nsxwolf »

scruple wrote: post #276
nsxwolf wrote: post #268

Earlier quoted context omitted.

There's so much suspicion in this industry. Is it so in other industries? We see a 20 year work history, and we assume you must be lying so we LeetCode you in front of a couple recent college grads. And now we're going to go after end user complaints as well? I guess its good I work on the back end, I can always blame poor user experience on the front end and "UX" people.

I'm suspicious of people that need to dress up their 20 years of experience with business speak, yes. It is the business speak specifically that makes me suspicious.

Everyone does this because everyone thinks they need to. So you're suspicious of everyone, but the only thing you can legitimately suspect is that they're the kind of person that does what needs to be done.
Post reply on HN