4 ms·

As what some would call an old person (~50), I love this. There is so much knowledge in old workers. Not all is relevant, sure, but there is so much that is tim

As what some would call an old person (~50), I love this. There is so much knowledge in old workers. Not all is relevant, sure, but there is so much that is timeless stuff that every young Engineer will learn, sooner or later, though varying degrees of suffering. If we could put away arrogance (from both young and old) we could do so much to advance the field.

amatecha 5y ago
Oh yeah, I absolutely love talking with the oldest possible people I work with. I'm not being sarcastic or anything. The older colleagues always have unbelievably awesome insight and interesting stories, and really wise advice. In a purely selfish way I'm always disappointed when someone retires because I know what kind of knowledge and wisdom is walking out the door. I always hope to be this type of person for those around me, sharing knowledge/experience to those who are up-and-coming in the career/industry. :)
gorbachev 5y ago
The thing that gets me is the cookie cutter interviewing approach a lot of places do. They ask about specifics, but that's not what is the really valuable stuff. As an example I've worked with so, so many web frameworks over the years, even created one or two of my own (small, limited functionality things). Most of them nobody uses any more, because newer frameworks are just better. But I bet the majority of recruiters see "Web Framework X, 1995" in my resume and think...wow, how outdated is this guy...what they don't seem to realize is that with some exceptions and advancements in technology, they all do the same things, even now. The issues you run into are mostly the same or so similar it's easy the spot the pattern, if you've got the experience I have. This is the same for any problem area for any experienced developer. That is very, very hard to convey in most interviews. What I do not have is skills to develop an implementation of a randomly selected algorithm in 20 minutes on the spot, because the last time I even saw it mentioned was 35 years ago, and even then I probably used a well tested library for it. Ask me about why you'd want to use that algorithm, or why I'd choose it over another one...that I could answer.
- zarkov99 5y ago
  Hang in there. I had to go through the Leetcode ordeal as well and it gets easier. It feels awful at first, but if you stick to it, read through the solutions, make sure you understand them, after 100 problems or so it all starts to come back and it becomes much easier. Its probably not the interview methodology I would use but I can see how efficient it is from the interviewer's POV.
  - snaidamast 5y ago
    I took a look at this LeetCode stuff on the web site. I reviewed a few of the sample, possible tests and found them utterly ridiculous. I have never seen a need in my entire career to program anything like these samples were expecting applicants to program.

amatecha 5y ago

Oh yeah, I absolutely love talking with the oldest possible people I work with. I'm not being sarcastic or anything. The older colleagues always have unbelievably awesome insight and interesting stories, and really wise advice. In a purely selfish way I'm always disappointed when someone retires because I know what kind of knowledge and wisdom is walking out the door. I always hope to be this type of person for those around me, sharing knowledge/experience to those who are up-and-coming in the career/industry. :)

gorbachev 5y ago

The thing that gets me is the cookie cutter interviewing approach a lot of places do. They ask about specifics, but that's not what is the really valuable stuff. As an example I've worked with so, so many web frameworks over the years, even created one or two of my own (small, limited functionality things). Most of them nobody uses any more, because newer frameworks are just better. But I bet the majority of recruiters see "Web Framework X, 1995" in my resume and think...wow, how outdated is this guy...what they don't seem to realize is that with some exceptions and advancements in technology, they all do the same things, even now. The issues you run into are mostly the same or so similar it's easy the spot the pattern, if you've got the experience I have. This is the same for any problem area for any experienced developer. That is very, very hard to convey in most interviews. What I do not have is skills to develop an implementation of a randomly selected algorithm in 20 minutes on the spot, because the last time I even saw it mentioned was 35 years ago, and even then I probably used a well tested library for it. Ask me about why you'd want to use that algorithm, or why I'd choose it over another one...that I could answer.

zarkov99 5y ago
Hang in there. I had to go through the Leetcode ordeal as well and it gets easier. It feels awful at first, but if you stick to it, read through the solutions, make sure you understand them, after 100 problems or so it all starts to come back and it becomes much easier. Its probably not the interview methodology I would use but I can see how efficient it is from the interviewer's POV.
- snaidamast 5y ago
  I took a look at this LeetCode stuff on the web site. I reviewed a few of the sample, possible tests and found them utterly ridiculous. I have never seen a need in my entire career to program anything like these samples were expecting applicants to program.