<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Fragile</title>
	<atom:link href="http://fragile.org.uk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://fragile.org.uk</link>
	<description>People and computers, mostly.....</description>
	<lastBuildDate>Fri, 18 Nov 2011 10:38:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Worried about candidates googling during a phone screen? You&#8217;re doing it wrong. by neilj</title>
		<link>http://fragile.org.uk/2011/11/worried-about-candidates-googling-during-a-phone-screen-youre-doing-it-wrong/comment-page-1/#comment-1087</link>
		<dc:creator>neilj</dc:creator>
		<pubDate>Fri, 18 Nov 2011 10:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=726#comment-1087</guid>
		<description>@John Huner
Agreed, though I can see value in providing a candidate with a task where there is insufficient information to solve straight away and expecting the candidate to puzzle through asking clarifying questions where needed, since this give an idea of problem solving process. However you&#039;d still need a pure programming task to augment it.</description>
		<content:encoded><![CDATA[<p>@John Huner<br />
Agreed, though I can see value in providing a candidate with a task where there is insufficient information to solve straight away and expecting the candidate to puzzle through asking clarifying questions where needed, since this give an idea of problem solving process. However you&#8217;d still need a pure programming task to augment it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Worried about candidates googling during a phone screen? You&#8217;re doing it wrong. by John Huner</title>
		<link>http://fragile.org.uk/2011/11/worried-about-candidates-googling-during-a-phone-screen-youre-doing-it-wrong/comment-page-1/#comment-1086</link>
		<dc:creator>John Huner</dc:creator>
		<pubDate>Fri, 18 Nov 2011 10:25:20 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=726#comment-1086</guid>
		<description>Also, the premise even seems a bit crazy.  Developers use Google in their job (probably everyday).  So using Google to answer questions seems fine to me.  Yes, you want to know that they understand things, but if they don&#039;t understand they are not going to be able to quickly Google and extract the sensible information for a good reply.</description>
		<content:encoded><![CDATA[<p>Also, the premise even seems a bit crazy.  Developers use Google in their job (probably everyday).  So using Google to answer questions seems fine to me.  Yes, you want to know that they understand things, but if they don&#8217;t understand they are not going to be able to quickly Google and extract the sensible information for a good reply.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reasons I love working in software by Management Improvement Carnival #145 &#187; Curious Cat Management Improvement Blog</title>
		<link>http://fragile.org.uk/2011/09/reasons-i-love-working-in-software/comment-page-1/#comment-1078</link>
		<dc:creator>Management Improvement Carnival #145 &#187; Curious Cat Management Improvement Blog</dc:creator>
		<pubDate>Mon, 10 Oct 2011 12:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=717#comment-1078</guid>
		<description>[...] Reasons I love working in software &#8211; &#8220;1) I get to work with people who really love what they do. 2) I get to work with people who are insanely open to change.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Reasons I love working in software &#8211; &#8220;1) I get to work with people who really love what they do. 2) I get to work with people who are insanely open to change.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Work At Your Company? by Eddie Van Helsing</title>
		<link>http://fragile.org.uk/2011/05/why-work-at-your-company/comment-page-1/#comment-990</link>
		<dc:creator>Eddie Van Helsing</dc:creator>
		<pubDate>Mon, 23 May 2011 23:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=704#comment-990</guid>
		<description>@neilj I read my post to my cats. I took their purring as approval.</description>
		<content:encoded><![CDATA[<p>@neilj I read my post to my cats. I took their purring as approval.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Work At Your Company? by neilj</title>
		<link>http://fragile.org.uk/2011/05/why-work-at-your-company/comment-page-1/#comment-989</link>
		<dc:creator>neilj</dc:creator>
		<pubDate>Mon, 23 May 2011 22:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=704#comment-989</guid>
		<description>Thanks for the feedback,  I particularly liked the idea of focusing job specs on the energy and excitement of specific projects. Not to mention to the massive win of open sourcing an appropriate project. 

Some specific responses

@Tet 
&quot;Anyone in a position to publish information about the company to prospective employees is rarely in a position to see the real company culture.&quot;
This is really great point. I think that below a certain size, probably the size at which individuals can still influence the entirety of a companies culture, it is still possible, but at larger companies it&#039;s a matter of expressing a group or department&#039;s sub culture. 

@Amazed 
Perhaps I should clarify, paying people anything other than a fair and equitable salary is completely counter productive. That said, as a London based tech company, we will never be able to compete with the rates available contracting from an investment bank. So it&#039;s a matter of preference. If money is the sole driver at the expense of job satisfaction then a curated job board makes no sense since the value of the company can be neatly expressed as a number. If, on the other hand interesting work in a challenging, open and engineering driven environment is a key selling point then some level of curation makes good sense. 

@ Eddie Van Helsing
Perhaps some sort of  XKCD inspired &lt;a href=&quot;http://xkcd.com/481/&quot; rel=&quot;nofollow&quot;&gt; &#039;read back your comments out loud before you post&#039;&lt;/a&gt; might have helped here? We do agree on one point though and that&#039;s the use of the term &#039;resource&#039; to describe people, in fact I wrote a &lt;a href=&quot;http://fragile.org.uk/2011/04/teams-are-not-our-most-valuable-resource-a-response/&quot; rel=&quot;nofollow&quot;&gt;post on this very subject&lt;/a&gt; just a few weeks ago.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback,  I particularly liked the idea of focusing job specs on the energy and excitement of specific projects. Not to mention to the massive win of open sourcing an appropriate project. </p>
<p>Some specific responses</p>
<p>@Tet<br />
&#8220;Anyone in a position to publish information about the company to prospective employees is rarely in a position to see the real company culture.&#8221;<br />
This is really great point. I think that below a certain size, probably the size at which individuals can still influence the entirety of a companies culture, it is still possible, but at larger companies it&#8217;s a matter of expressing a group or department&#8217;s sub culture. </p>
<p>@Amazed<br />
Perhaps I should clarify, paying people anything other than a fair and equitable salary is completely counter productive. That said, as a London based tech company, we will never be able to compete with the rates available contracting from an investment bank. So it&#8217;s a matter of preference. If money is the sole driver at the expense of job satisfaction then a curated job board makes no sense since the value of the company can be neatly expressed as a number. If, on the other hand interesting work in a challenging, open and engineering driven environment is a key selling point then some level of curation makes good sense. </p>
<p>@ Eddie Van Helsing<br />
Perhaps some sort of  XKCD inspired <a href="http://xkcd.com/481/" rel="nofollow"> &#8216;read back your comments out loud before you post&#8217;</a> might have helped here? We do agree on one point though and that&#8217;s the use of the term &#8216;resource&#8217; to describe people, in fact I wrote a <a href="http://fragile.org.uk/2011/04/teams-are-not-our-most-valuable-resource-a-response/" rel="nofollow">post on this very subject</a> just a few weeks ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Work At Your Company? by Eddie Van Helsing</title>
		<link>http://fragile.org.uk/2011/05/why-work-at-your-company/comment-page-1/#comment-984</link>
		<dc:creator>Eddie Van Helsing</dc:creator>
		<pubDate>Mon, 23 May 2011 10:43:02 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=704#comment-984</guid>
		<description>Why work at your company? Simple: I have to earn a living &lt;em&gt;somehow&lt;/em&gt;, and crime only pays &lt;em&gt;well&lt;/em&gt; if you&#039;re a banker or a politician. As for developer-&gt;employer trust, let me clear that up for you: &lt;strong&gt;I don&#039;t trust you. I will &lt;em&gt;never&lt;/em&gt; trust you.&lt;/strong&gt; Is that better? 

Look here. I&#039;ve been in the software development trade and I think I know how this works by now. If you hire me, you&#039;re going to try to get as much out of me as you can. If you can get me to work 50 hours a week instead of 40, you will. If you can get an occasional Saturday out of me, you will. If you can get me to accept a mediocre salary, you will. As far as you&#039;re concerned, I&#039;m not a man, but a resource. Men command respect. Resources get exploited.

You&#039;re going to use me up if you can, and then throw me aside to make room for another sucker who will work for a shittier salary than you offered &lt;em&gt;me&lt;/em&gt; because he&#039;s younger and isn&#039;t cynical enough to realize that he&#039;s being led to slaughter.

So don&#039;t ask about trust. Don&#039;t you fucking &lt;em&gt;dare&lt;/em&gt;. You haven&#039;t earned the right to expect trust out of me, or out of any other developer. We&#039;re mercenaries by necessity, because loyalty to an employer is a sucker&#039;s game.</description>
		<content:encoded><![CDATA[<p>Why work at your company? Simple: I have to earn a living <em>somehow</em>, and crime only pays <em>well</em> if you&#8217;re a banker or a politician. As for developer-&gt;employer trust, let me clear that up for you: <strong>I don&#8217;t trust you. I will <em>never</em> trust you.</strong> Is that better? </p>
<p>Look here. I&#8217;ve been in the software development trade and I think I know how this works by now. If you hire me, you&#8217;re going to try to get as much out of me as you can. If you can get me to work 50 hours a week instead of 40, you will. If you can get an occasional Saturday out of me, you will. If you can get me to accept a mediocre salary, you will. As far as you&#8217;re concerned, I&#8217;m not a man, but a resource. Men command respect. Resources get exploited.</p>
<p>You&#8217;re going to use me up if you can, and then throw me aside to make room for another sucker who will work for a shittier salary than you offered <em>me</em> because he&#8217;s younger and isn&#8217;t cynical enough to realize that he&#8217;s being led to slaughter.</p>
<p>So don&#8217;t ask about trust. Don&#8217;t you fucking <em>dare</em>. You haven&#8217;t earned the right to expect trust out of me, or out of any other developer. We&#8217;re mercenaries by necessity, because loyalty to an employer is a sucker&#8217;s game.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Work At Your Company? by Kissaki</title>
		<link>http://fragile.org.uk/2011/05/why-work-at-your-company/comment-page-1/#comment-983</link>
		<dc:creator>Kissaki</dc:creator>
		<pubDate>Mon, 23 May 2011 10:32:39 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=704#comment-983</guid>
		<description>Personally, in the job interview I like to ask about typical projects, the tools and languages being used, the workplace in general (team-rooms? big room with separated spaces?). I kind of miss that on many/all companies websites, so when I search for a job and visit a companys website I can already see what the workplace looks like and what tools they use. I can understand maybe that is not something the company wants to make publicly visible to each and everyone, but well, that is my point of view as a job searcher.

And boy, I hate PR-babbling that tells you nothing.

I also really like the idea a commentator pointed out. Community and Open Source.
A company blog that gives insights and general advises gives you so much information, as an applier.
One that really stands out is the blog of Assembla. I am following their blog for some time now, because they post great blog posts about distributed development and much more. That way I not only came to get to know that company and, even more importantly, follow them, I get to know how they work and that they really know what they’re doing. If you can get people to follow your company for informative blog posts you made it. That is THE way to go IMO.</description>
		<content:encoded><![CDATA[<p>Personally, in the job interview I like to ask about typical projects, the tools and languages being used, the workplace in general (team-rooms? big room with separated spaces?). I kind of miss that on many/all companies websites, so when I search for a job and visit a companys website I can already see what the workplace looks like and what tools they use. I can understand maybe that is not something the company wants to make publicly visible to each and everyone, but well, that is my point of view as a job searcher.</p>
<p>And boy, I hate PR-babbling that tells you nothing.</p>
<p>I also really like the idea a commentator pointed out. Community and Open Source.<br />
A company blog that gives insights and general advises gives you so much information, as an applier.<br />
One that really stands out is the blog of Assembla. I am following their blog for some time now, because they post great blog posts about distributed development and much more. That way I not only came to get to know that company and, even more importantly, follow them, I get to know how they work and that they really know what they’re doing. If you can get people to follow your company for informative blog posts you made it. That is THE way to go IMO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Work At Your Company? by Tet</title>
		<link>http://fragile.org.uk/2011/05/why-work-at-your-company/comment-page-1/#comment-981</link>
		<dc:creator>Tet</dc:creator>
		<pubDate>Mon, 23 May 2011 07:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=704#comment-981</guid>
		<description>Simple answer: you can&#039;t. The primary reason being that you don&#039;t know what your company&#039;s culture and values are. You might think you know what they are. But that&#039;s not necessarily the same. My present employer excluded, I can&#039;t remember the last time I worked for a company that didn&#039;t claim &quot;our staff are our most important asset&quot;. I also can&#039;t remember it being true at any of them. Yet as far as management are concerned, the company exists to keep the staff happy. Anyone in a position to publish information about the company to prospective employees is rarely in a position to see the real company culture. They&#039;ll see what they&#039;d like it to be, not how it really is. It probably doesn&#039;t have to be like that. But decades of experience show that it invariably is.</description>
		<content:encoded><![CDATA[<p>Simple answer: you can&#8217;t. The primary reason being that you don&#8217;t know what your company&#8217;s culture and values are. You might think you know what they are. But that&#8217;s not necessarily the same. My present employer excluded, I can&#8217;t remember the last time I worked for a company that didn&#8217;t claim &#8220;our staff are our most important asset&#8221;. I also can&#8217;t remember it being true at any of them. Yet as far as management are concerned, the company exists to keep the staff happy. Anyone in a position to publish information about the company to prospective employees is rarely in a position to see the real company culture. They&#8217;ll see what they&#8217;d like it to be, not how it really is. It probably doesn&#8217;t have to be like that. But decades of experience show that it invariably is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Work At Your Company? by Eugene Crosser</title>
		<link>http://fragile.org.uk/2011/05/why-work-at-your-company/comment-page-1/#comment-980</link>
		<dc:creator>Eugene Crosser</dc:creator>
		<pubDate>Mon, 23 May 2011 06:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=704#comment-980</guid>
		<description>If your company has some some useful code that you can open source, by all means do it, and spread the word. Developers will notice that you are doing cool things, and are good enough to share them.</description>
		<content:encoded><![CDATA[<p>If your company has some some useful code that you can open source, by all means do it, and spread the word. Developers will notice that you are doing cool things, and are good enough to share them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Work At Your Company? by A.G.McDowell</title>
		<link>http://fragile.org.uk/2011/05/why-work-at-your-company/comment-page-1/#comment-979</link>
		<dc:creator>A.G.McDowell</dc:creator>
		<pubDate>Mon, 23 May 2011 05:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://fragile.org.uk/?p=704#comment-979</guid>
		<description>If a company is big enough to acquire a general reputation, it is probably big enough that the difference between individual workgroups within the company is larger than the difference between that company - averaged out - and others. Assuming that you are recruiting to fill a particular slot, it is up to you to convince good candidates that they want to fill that particular slot in that particular workgroup, to work for that particular boss and in that particular environment.</description>
		<content:encoded><![CDATA[<p>If a company is big enough to acquire a general reputation, it is probably big enough that the difference between individual workgroups within the company is larger than the difference between that company &#8211; averaged out &#8211; and others. Assuming that you are recruiting to fill a particular slot, it is up to you to convince good candidates that they want to fill that particular slot in that particular workgroup, to work for that particular boss and in that particular environment.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

