<story><title>Engineers suck at finding the right jobs</title><url>http://matt.aimonetti.net/posts/2012/11/14/engineers-suck-at-finding-right-jobs/</url></story><parent_chain></parent_chain><comment><author>ChuckMcM</author><text>It is an interesting screed. I was thinking when I wrote up the comment about how VP&apos;s might feel about leaving a position that there is an interesting dividing line which doesn&apos;t get talked about a lot, Matt touches on it but didn&apos;t really call it out, its this, &quot;What are you trying to get done?&quot;&lt;p&gt;Early in my career Steve Bourne gave me useful advice, he said the difference between junior engineers and senior engineers was that senior engineers had an agenda. More specifically they had an execution goal (like write a new file system, or create a product that solves problem &apos;X&apos;) and they worked toward it.&lt;p&gt;This is a both a hugely motivating and hugely scary thing, its motivating because you don&apos;t have to ask &quot;what do I do now?&quot; the direction just falls out of where you are vs where you are trying to go. It is scary because you can find you&apos;re goal isn&apos;t compatible with any of the company&apos;s goals. When you discover that what you want to do can&apos;t be done at the company you are working at, you either have to change goals or leave. But its not a &apos;feel bad about it&apos; leaving it is &apos;hmm, this isn&apos;t going to work out here so lets go somewhere that it could&apos;.&lt;p&gt;The alternative to having an agenda is &quot;Goofing off and waiting for someone to give you a task.&quot; There are a lot of engineers who operate in that mode, do their assigned tasks at an acceptable quality level and without too much schedule slip. They are great to have around because people with agendas and use them to move the agenda forward, but they don&apos;t make for very good &apos;senior&apos; people because they really don&apos;t care what they work on, its not their main focus.&lt;p&gt;It is important to note that you can&apos;t &quot;fail&quot; if you&apos;re just goofing off, as one of my kids put it, &quot;It isn&apos;t procrastination if you don&apos;t have anything you need to do.&quot; You can however rationalize your low work output by the fact that your management really hasn&apos;t given you all that much to do, so whose fault is that? Whereas if you have an agenda, a goal, a destination, you can fail to make it to that destination. &quot;You said you were going to build a game that could crush Farmville, you failed.&quot; Reading the blog post from Speck about Glitch shutting down, &quot;we failed to develop an audience.&quot; They had a goal, they didn&apos;t get there.&lt;p&gt;Matt&apos;s advice that if you don&apos;t know what you want, you can&apos;t choose reasonably is solid. Start by deciding what you want to do, and pick something that will take a while as early goal achievement has its own problems.</text></comment>
<story><title>Engineers suck at finding the right jobs</title><url>http://matt.aimonetti.net/posts/2012/11/14/engineers-suck-at-finding-right-jobs/</url></story><parent_chain></parent_chain><comment><author>tinco</author><text>So, it is a noble thing Matt is doing here, but my skepticism always kicks in when a post like that does not include a self evaluation.&lt;p&gt;I am sure you could fish up some great job opportunities for anyone who writes you a nice e-mail. But is your own job the job you want from your career?&lt;p&gt;I mean, being tech lead on a big company is nice and all. But the company is just a coupon distributor, I&apos;m not saying that I work for the sexiest startup in the world, but I&apos;m just saying that &apos;up&apos; is not always the most satisfactory trajectory for a career.&lt;p&gt;I don&apos;t think I&apos;d be happy for long at a company like LivingSocial, unless you guys are hiding something behind there that makes it a very nice place to work at?</text></comment>