[chuck32]

Sorry, this is really bad advice IMO.

"1year or more out there are entirly new stacks, new libraries, new versions, new ways of building things etc."

You think there are any dev teams which change their entire stack every year? As for new libraries, thats what documentation is for, nobody gets hired because they have a the newest & hottest libraries APIs memorized.

Being a good developer has very little to do with knowing all of the trendiest new tools. A sound understanding of software engineering practices and methodologies is far more important.

[spcelzrd]

In addition to having a sound understanding of software engineering practices, a good developer will be able to learn new tools, languages, and libraries.

Being adaptable is a must. There's no reason to place a lot of value on a person who has already learned a particular library when you know they will eventually have to learn something else. Value the engineer underneath the layer of buzzwords.

[jevgeni]

You are right. I think fundamental knowledge is important in this case, where it allows you to cut throught the fluff of buzzwords and see what the actual content is.

[jevgeni]

Well, this is bad advice only in a certain context. If an organization has reached a more mature period of your products life cycle, you are not concerned that much with new hot things that come out. If you need to generate product ideas and prototypes, or the all too familiar "productive prototype", then you are of course interested in stuff that will help you bring out new features cheaper and quicker.