Earlier quoted context omitted.
Uh, isn't that rather much the point? Once a young person learns all this stuff from experience, they've become an old person.
But you can gain experience without necessarily becoming old at the same time. They're correlated, but not causal.
Why You Should Hire an Old Programmer
31–40 of 192 posts
Re: Why You Should Hire an Old Programmer
#32How do older programmers deal with coding interviews from companies like facebook / google? i feel like those advantage people who just finished their algorithms class, or have time to practice specifically for it.
Don't want to generalize but as far as I have seen; they don't. As a 6th point in his list could be; connections. I (42 y/o) know people; I can get programmers to follow me if I move company which is a plus. But I also know investors, potential clients, C*O's and hiring managers. People recommend you or know you via their network.
It's at best a 'neutral' because when you inevitably leave again you'll take all those people with you potentially leaving the company floundering.
Re: Why You Should Hire an Old Programmer
#33I would _never_ hire this candidate, based on seeing this. So - the author says that he has "developed some good communication skills". Great! Moving on, let's look at his linkedin page. Quotes from past jobs: "even after our idiot (now ex) CEO canceled the platform.", "wonky JavaEE stuff.". So, as a hiring manager, from this post + linkedin, I now know that this guy: 1) can reach large audiences, 2) trashes past job…
Re: Why You Should Hire an Old Programmer
#34I would _never_ hire this candidate, based on seeing this. So - the author says that he has "developed some good communication skills". Great! Moving on, let's look at his linkedin page. Quotes from past jobs: "even after our idiot (now ex) CEO canceled the platform.", "wonky JavaEE stuff.". So, as a hiring manager, from this post + linkedin, I now know that this guy: 1) can reach large audiences, 2) trashes past job…
Re: Why You Should Hire an Old Programmer
#35When talking with young programmers I too often think "well, you are doing that wrong, been there, done that". They don't want to listen. A couple of months later they notice that the gray beard ones were right. From a company perspective, that's just too late, as the money loss is not recoverable. There is nothing wrong with being a young one with no experience. There is so much wrong when a company has only a bunch…
But obviously that's a generalisation. Just like your comment is.
Re: Why You Should Hire an Old Programmer
#36Re: Why You Should Hire an Old Programmer
#37Earlier quoted context omitted.
(1) You don't make legal cases against people involved in a hiring rejection, you make a case against a company. (2) If you are making hiring decisions the appearance of random blog posts should not and will not give you any legal basis not to hire. Legality is encoded in the law, not in blogposts, especially not in blogposts by random passers by. If you were using this as a reason not to hire the person writing the…
> (1) You don't make legal cases against people involved in a hiring rejection, you make a case against a company. Entirely true. In my defense, I'm not a lawyer. Technically also in my defense: the United States has a bad habit of calling corporations people. > (2) If you are making hiring decisions the appearance of random blog posts should not and will not give you any legal basis not to hire. Legality is encoded…
HR policies are what takes care of that, if an individual is able to make the company engage in illegal behavior you have bigger problems in the oversight department. Hiring comes with a bunch of rules, this person should not be able to transcend those rules by their lonesome.
Re: Why You Should Hire an Old Programmer
#38I would _never_ hire this candidate, based on seeing this. So - the author says that he has "developed some good communication skills". Great! Moving on, let's look at his linkedin page. Quotes from past jobs: "even after our idiot (now ex) CEO canceled the platform.", "wonky JavaEE stuff.". So, as a hiring manager, from this post + linkedin, I now know that this guy: 1) can reach large audiences, 2) trashes past job…
This is indeed basic psychology [1]: talking bad about other people reflects poorly on _you_, not just the people you're talking about. https://en.wikipedia.org/wiki/Emotional_contagion
Re: Why You Should Hire an Old Programmer
#39Earlier quoted context omitted.
Don't want to generalize but as far as I have seen; they don't. As a 6th point in his list could be; connections. I (42 y/o) know people; I can get programmers to follow me if I move company which is a plus. But I also know investors, potential clients, C*O's and hiring managers. People recommend you or know you via their network.
> I can get programmers to follow me if I move company which is a plus. It's at best a 'neutral' because when you inevitably leave again you'll take all those people with you potentially leaving the company floundering.
And unlike a lot of people it seems, I don't really enjoy moving to another company or taking people if they enjoy what they do; it would be that they would ask me first if I have something.
Re: Why You Should Hire an Old Programmer
#40I would _never_ hire this candidate, based on seeing this. So - the author says that he has "developed some good communication skills". Great! Moving on, let's look at his linkedin page. Quotes from past jobs: "even after our idiot (now ex) CEO canceled the platform.", "wonky JavaEE stuff.". So, as a hiring manager, from this post + linkedin, I now know that this guy: 1) can reach large audiences, 2) trashes past job…
> I don't think it's so bad. Sometimes, you work with idiots.
Just because a person thinks coworkers are idiots doesn't mean the person should pipe up about it. It's one of those communication skills that a person with a ton of experience is expected to learn.