<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>thoraway1010</author><text>In jurassic age companies you can get up to speed quicker, there is less to wrap your head around and the onsite staff tend to use a simpler approach (manual methods etc).&lt;p&gt;If you think you are &amp;quot;up to speed&amp;quot; on a large company a week or so you are usually so incompetent you don&amp;#x27;t know what you don&amp;#x27;t know.</text><parent_chain><item><author>master_yoda_1</author><text>If it takes 6 month to come to speed for an experienced engineer, I would say you are working with dinosaurs, in a jurassic age company.</text></item><item><author>subsubzero</author><text>Haha, it typically takes 6 months to get up to speed at a company as everyone has their own set of unique tools and infrastructure. Also at that cadence you are not vesting any stock(1 year cliff?) so that seems very strange. Having worked with high-vis engineers in the past, alot of them seem to be vanity hires, they really don&amp;#x27;t impact much change and probably stoke the egos of the upper managers&amp;#x2F;execs much like (prof. slughorn from harry potter), collecting &amp;quot;geniuses&amp;quot;.</text></item><item><author>gfiorav</author><text>I&amp;#x27;m always going to cringe at Twitter&amp;#x27;s &amp;quot;star&amp;quot; engineers who spend an average of 7 months in each company. HTH do you even understand the product and contribute in that time frame? One of two things needs to be at play:&lt;p&gt;1. You were brought in to do very specific work (i.e.: migrate something to k8s).&lt;p&gt;2. You were brought in as a token due to your social media following.&lt;p&gt;Seriously, how else?</text></item></parent_chain></comment><story><title>The Wetware Crisis: the Dead Sea effect (2008)</title><url>http://brucefwebster.com/2008/04/11/the-wetware-crisis-the-dead-sea-effect/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>packetlost</author><text>You can be contributing code in a week or less, but if you&amp;#x27;re getting fully up to speed on any moderately large system in under 3 months, you probably should take breaks for meals and sleep more. Or you&amp;#x27;re not getting fully up to speed and are just ignorant. It could be less for a trivial or entirely greenfield system, but then you&amp;#x27;re worrying about other things like requirements&amp;#x2F;constraints&amp;#x2F;etc.</text><parent_chain><item><author>master_yoda_1</author><text>If it takes 6 month to come to speed for an experienced engineer, I would say you are working with dinosaurs, in a jurassic age company.</text></item><item><author>subsubzero</author><text>Haha, it typically takes 6 months to get up to speed at a company as everyone has their own set of unique tools and infrastructure. Also at that cadence you are not vesting any stock(1 year cliff?) so that seems very strange. Having worked with high-vis engineers in the past, alot of them seem to be vanity hires, they really don&amp;#x27;t impact much change and probably stoke the egos of the upper managers&amp;#x2F;execs much like (prof. slughorn from harry potter), collecting &amp;quot;geniuses&amp;quot;.</text></item><item><author>gfiorav</author><text>I&amp;#x27;m always going to cringe at Twitter&amp;#x27;s &amp;quot;star&amp;quot; engineers who spend an average of 7 months in each company. HTH do you even understand the product and contribute in that time frame? One of two things needs to be at play:&lt;p&gt;1. You were brought in to do very specific work (i.e.: migrate something to k8s).&lt;p&gt;2. You were brought in as a token due to your social media following.&lt;p&gt;Seriously, how else?</text></item></parent_chain></comment><story><title>The Wetware Crisis: the Dead Sea effect (2008)</title><url>http://brucefwebster.com/2008/04/11/the-wetware-crisis-the-dead-sea-effect/</url></story>