<story><title>Older job seekers get fewer offers on LinkedIn but a younger profile photo helps</title><url>https://www.psychnewsdaily.com/older-job-seekers-on-linkedin-get-fewer-job-offers-but-younger-profile-photo-helps/</url></story><parent_chain><item><author>seattle_spring</author><text>As an engineer with more than 15 years professional experience, my definition of &amp;quot;junior shit&amp;quot; would be thinking you can hand-roll a foundation or framework better than something that already exists.</text></item><item><author>austincheney</author><text>The most consistent pattern I have observed as an older developer with some years on a resume is absolute utter astonishment when I don&amp;#x27;t want to waste time on a bunch of confused newb shit like sickly bloated frameworks with a million dependencies.  Its weird to hear people acknowledge that I have just so much experience on paper and yet be so amazingly dumbfounded surprised that I would be focused on less junior things.&lt;p&gt;I haven&amp;#x27;t yet found the proper words to converse through that, but a team of similarly older developers sharing similar concerns adds tremendous value.</text></item></parent_chain><comment><author>OldHand2018</author><text>If the existing framework is so great, why does it keep getting replaced with a new framework?  Why aren’t we all still on Angular?&lt;p&gt;And if we all keep hiring only the best candidates, why would we think that they &lt;i&gt;can’t&lt;/i&gt; write a better framework?  &lt;i&gt;somebody&lt;/i&gt; is writing a better framework.</text></comment>
<story><title>Older job seekers get fewer offers on LinkedIn but a younger profile photo helps</title><url>https://www.psychnewsdaily.com/older-job-seekers-on-linkedin-get-fewer-job-offers-but-younger-profile-photo-helps/</url></story><parent_chain><item><author>seattle_spring</author><text>As an engineer with more than 15 years professional experience, my definition of &amp;quot;junior shit&amp;quot; would be thinking you can hand-roll a foundation or framework better than something that already exists.</text></item><item><author>austincheney</author><text>The most consistent pattern I have observed as an older developer with some years on a resume is absolute utter astonishment when I don&amp;#x27;t want to waste time on a bunch of confused newb shit like sickly bloated frameworks with a million dependencies.  Its weird to hear people acknowledge that I have just so much experience on paper and yet be so amazingly dumbfounded surprised that I would be focused on less junior things.&lt;p&gt;I haven&amp;#x27;t yet found the proper words to converse through that, but a team of similarly older developers sharing similar concerns adds tremendous value.</text></item></parent_chain><comment><author>LAC-Tech</author><text>Backend framework? Fair enough. Frontend framework? I&amp;#x27;m really not so sure anymore.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    user does something -&amp;gt; change state -&amp;gt; modify DOM
&lt;/code&gt;&lt;/pre&gt;
This isn&amp;#x27;t exactly rocket science.</text></comment>