<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: hr</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/hr.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2013-08-13T12:51:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>What is a good onboarding process for a new employee at a startup?</title><link href="https://simonwillison.net/2013/Aug/13/what-is-a-good/#atom-tag" rel="alternate"/><published>2013-08-13T12:51:00+00:00</published><updated>2013-08-13T12:51:00+00:00</updated><id>https://simonwillison.net/2013/Aug/13/what-is-a-good/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/What-is-a-good-onboarding-process-for-a-new-employee-at-a-startup/answer/Simon-Willison"&gt;What is a good onboarding process for a new employee at a startup?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Have them deploy the site on their first day. This ensures they know how to...&lt;/p&gt;

&lt;ol&gt;&lt;li&gt;Set up a working development environment&lt;/li&gt;&lt;li&gt;Check code out of your repository&lt;/li&gt;&lt;li&gt;Navigate the code base&lt;/li&gt;&lt;li&gt;Make code changes&lt;/li&gt;&lt;li&gt;Run tests&lt;/li&gt;&lt;li&gt;Pass a code review (or at least get some peer review)&lt;/li&gt;&lt;li&gt;QA their change beyond just the automated tests&lt;/li&gt;&lt;li&gt;Deploy their change to production&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;If they do all of this on day one, they'll come in on day two ready to start building and shipping production code.

&lt;p&gt;This also means your team need to have a development/deployment environment that can be set up in less than a day, albeit with a little guidance. This is a very good thing.&lt;/p&gt;

&lt;p&gt;If your infrastructure is good enough you can even do this with non-technical employees as well - let them edit the "about" page on your site to add themselves through the GitHub web editor and hit a "deploy" button in Jenkins or similar to deploy the site!&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/code-review"&gt;code-review&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/startups"&gt;startups&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hr"&gt;hr&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="code-review"/><category term="startups"/><category term="quora"/><category term="hr"/></entry><entry><title>What are the coolest benefits/perks offered by startups?</title><link href="https://simonwillison.net/2011/Dec/25/what-are-the-coolest/#atom-tag" rel="alternate"/><published>2011-12-25T09:56:00+00:00</published><updated>2011-12-25T09:56:00+00:00</updated><id>https://simonwillison.net/2011/Dec/25/what-are-the-coolest/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="https://www.quora.com/What-are-the-coolest-benefits-perks-offered-by-startups/answer/Simon-Willison"&gt;What are the coolest benefits/perks offered by startups?&lt;/a&gt; on Quora&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I heard that Songkick give all of their employees a monthly gig budget to encourage them to go to live music (since that's what the site is all about), which I think is a neat and appropriate perk.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/startups"&gt;startups&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quora"&gt;quora&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hr"&gt;hr&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="startups"/><category term="quora"/><category term="hr"/></entry></feed>