3 ms·
What I find is you have people that gain 10 years of experience in 10 years and people that get 1 year of experience repeated 10 times. The field changes, it's
by cogman10 4y ago
What I find is you have people that gain 10 years of experience in 10 years and people that get 1 year of experience repeated 10 times.
The field changes, it's changed significantly since I started 10 years ago. Yet there's a fairly large contingent of devs that aren't keeping up. I've interviewed old devs that are at the top of their game and old devs that are no better than the interns we have. I've worked with the same.
- postalrat 4y agoWhat are you basing your judgements on?
- tester756 4y agoIn my opinion: They lack foundational software engineering knowledge/opinions Use their IDEs as if they saw it for the first time Lack of experience when it comes to architecture
- btschaegg 4y agoIt becomes even worse if you run into people who operate on cutting edge knowledge from decades ago and insist on it. I've seen people organize their data in a cache-pessimal way in order to squeeze out a couple of CPU cycles, for example. It becomes really tiring when you constantly have to whip up a benchmark just to settle debates on things that have been common knowledge for basically forever now.
- tester756 4y agoHaha, I've experienced that. You can argue everything with "because of performance reasons" because it requires way more effort to actually check it.
- neonsunset 4y agoOr sometimes it's the opposite and you get shoved "Premature optimization..." quote up your change request during every code review and fighting person's bad habits requires you writing benchmark or referencing 5 articles with examples for every little thing. It's maddening.
- deleted 4y ago[deleted]
- sevagh 4y agoYou found this, really? You're not just repeating a very common and widespread phrase that's been found by other people and in use for decades? ([1] [2]) [1]: https://news.ycombinator.com/item?id=4627373 https://news.ycombinator.com/item?id=4627373 [2]: https://ask.metafilter.com/62762/What-is-the-source-of-this-quote-about-experience https://ask.metafilter.com/62762/What-is-the-source-of-this-...
- cercatrova 4y agoThis is a weird way of twisting their words. They didn't "find" the phrase themselves, as in coming up with the words, rather they found that in their experience, some programmers behave according to said phrase. You are parsing the word "find" in the incorrect way in this situation.
- wrnr 4y agoI've heart this being repeated a lot so it is likely not something you came up with yourself. I always become suspicious when a software engineer has been working on a problem +10 years. The type that spend their time upgrading angularJS to angular or something like that.
- Beltalowda 4y agoThere are certainly older devs who only know $thing and can be kind of myopic, but this works the other way too: there are also young devs who only know $thing and are rather myopic. Another thing I've seen is people complaining about "old geezer not keeping up" is used to shut down conversation about whether $new_fad is really the best choice, and $old_thing may actually be better. Not saying that was your intent, but I've seen it used like this many times. Not all that many years ago someone saying "no thanks, I'll stick with SQL instead of no-SQL" and even "no thanks, I'll stick with Java because I think the static typing is better" could be seen as "not keeping up".
- cogman10 4y ago> There are certainly older devs who only know $thing and can be kind of myopic, but this works the other way too: there are also young devs who only know $thing and are rather myopic. This is why I tried not to classify this as a young v old thing. I don't think it's the case that old devs can't keep up. I think it's the case that some devs don't keep up regardless of age. For young devs, it's hard to know if that's the case or if it's simply inexperience. For old devs, it's far more glaring when all their experience is with VB6. I think that's where a lot of the ageism in software hiring practices comes from. > Not all that many years ago someone saying "no thanks, I'll stick with SQL instead of no-SQL" and even "no thanks, I'll stick with Java because I think the static typing is better" could be seen as "not keeping up". Perhaps some saw it that way. I never did. I would say that if you were completely unfamiliar with no-SQL, you likely weren't keeping up. Just like if you aren't aware of k8s or docker today, you aren't keeping up. Whether or not you chose to use those techs is entirely different from simply outright rejecting them without evaluation.