<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Ted's Rants and Raves by Ted M. Young Comments</title>
	<link>http://tedyoung.blogsome.com</link>
	<description>It's the People and the Process: Pay attention to the People doing the as well as the Process. If the people don't work well together, no process will help.</description>
	<pubDate>Wed, 25 Nov 2009 17:03:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Leonardo</title>
		<link>http://tedyoung.blogsome.com/2009/11/22/how-to-do-your-best-in-a-technical-interview-part-ii-questions/#comment-29</link>
		<pubDate>Sun, 22 Nov 2009 13:06:32 +0000</pubDate>
		<guid>http://tedyoung.blogsome.com/2009/11/22/how-to-do-your-best-in-a-technical-interview-part-ii-questions/#comment-29</guid>
					<description>Awesome question! I never thought of that, but its definitely true... From my past experience, I put several friends on the best places I worked for and none on the ones I didn't like... 

</description>
		<content:encoded><![CDATA[	<p>Awesome question! I never thought of that, but its definitely true&#8230; From my past experience, I put several friends on the best places I worked for and none on the ones I didn&#8217;t like&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Administrator</title>
		<link>http://tedyoung.blogsome.com/2009/11/21/how-to-do-your-best-in-a-technical-interview/#comment-28</link>
		<pubDate>Sat, 21 Nov 2009 21:28:55 +0000</pubDate>
		<guid>http://tedyoung.blogsome.com/2009/11/21/how-to-do-your-best-in-a-technical-interview/#comment-28</guid>
					<description>Hi Lanette,

It's been a while since I've done any Python, so I'm not sure what question I'd ask that's specific to Python. However, my interview questions tend to be &quot;here's some requirements, go implement it&quot;. Whether it's done in Java, Python, or Lisp, the important thing is that you can break the problem down, ask questions, and create a solution that works.

For testers, I'm less interested in their coding skills than their ability to break things. You didn't say how you use Python for testing stuff, so I'd probably come up with some application and ask you to tell me how you'd test it and then automate the test using Python.

As for practicing so that you don't get nervous, all it takes is, well, practice. Just like I used to take simulated job interviews in college, ask friends to indulge you while you stand at a whiteboard while they sit down and watch you demonstrate your scripting ability. If you can make a non-technical person understand what you're doing, then your in great shape.

;ted</description>
		<content:encoded><![CDATA[	<p>Hi Lanette,</p>
	<p>It&#8217;s been a while since I&#8217;ve done any Python, so I&#8217;m not sure what question I&#8217;d ask that&#8217;s specific to Python. However, my interview questions tend to be &#8220;here&#8217;s some requirements, go implement it&#8221;. Whether it&#8217;s done in Java, Python, or Lisp, the important thing is that you can break the problem down, ask questions, and create a solution that works.</p>
	<p>For testers, I&#8217;m less interested in their coding skills than their ability to break things. You didn&#8217;t say how you use Python for testing stuff, so I&#8217;d probably come up with some application and ask you to tell me how you&#8217;d test it and then automate the test using Python.</p>
	<p>As for practicing so that you don&#8217;t get nervous, all it takes is, well, practice. Just like I used to take simulated job interviews in college, ask friends to indulge you while you stand at a whiteboard while they sit down and watch you demonstrate your scripting ability. If you can make a non-technical person understand what you&#8217;re doing, then your in great shape.</p>
	<p>;ted</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lanette (testyredhead)</title>
		<link>http://tedyoung.blogsome.com/2009/11/21/how-to-do-your-best-in-a-technical-interview/#comment-27</link>
		<pubDate>Sat, 21 Nov 2009 15:58:19 +0000</pubDate>
		<guid>http://tedyoung.blogsome.com/2009/11/21/how-to-do-your-best-in-a-technical-interview/#comment-27</guid>
					<description>Cool! I like the ideas here. I was wondering if you could give an example of a question you might ask a tester about Python? I mean, right now I'm writing lots of python scripts for testing stuff, but I've never interviewed on my scripting skills before. How could I practice so I don't get so nervous I choke?</description>
		<content:encoded><![CDATA[	<p>Cool! I like the ideas here. I was wondering if you could give an example of a question you might ask a tester about Python? I mean, right now I&#8217;m writing lots of python scripts for testing stuff, but I&#8217;ve never interviewed on my scripting skills before. How could I practice so I don&#8217;t get so nervous I choke?</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Web developer</title>
		<link>http://tedyoung.blogsome.com/2008/02/27/intellij-idea-tip-change-background-color-for-read-only-files/#comment-25</link>
		<pubDate>Wed, 14 Oct 2009 07:55:35 +0100</pubDate>
		<guid>http://tedyoung.blogsome.com/2008/02/27/intellij-idea-tip-change-background-color-for-read-only-files/#comment-25</guid>
					<description>Humm... interesting,

thas a great tip, didnt no this before, its very useful, keep up the good work :D

Thanks</description>
		<content:encoded><![CDATA[	<p>Humm&#8230; interesting,</p>
	<p>thas a great tip, didnt no this before, its very useful, keep up the good work <img src='http://tedyoung.blogsome.com/wp-images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
	<p>Thanks</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: software development uk</title>
		<link>http://tedyoung.blogsome.com/2007/04/17/the-4000-error-message/#comment-24</link>
		<pubDate>Mon, 17 Aug 2009 08:06:50 +0100</pubDate>
		<guid>http://tedyoung.blogsome.com/2007/04/17/the-4000-error-message/#comment-24</guid>
					<description>Humm... interesting,
Thanks for writing, most people don't bother.</description>
		<content:encoded><![CDATA[	<p>Humm&#8230; interesting,<br />
Thanks for writing, most people don&#8217;t bother.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Shaun Abram</title>
		<link>http://tedyoung.blogsome.com/2008/11/10/silicon-valley-code-camp-2008-feedback/#comment-23</link>
		<pubDate>Mon, 23 Feb 2009 21:58:40 +0000</pubDate>
		<guid>http://tedyoung.blogsome.com/2008/11/10/silicon-valley-code-camp-2008-feedback/#comment-23</guid>
					<description>Hey Ted,
I think a good measure of a talk is how long you think about it afterward. Well, it's been over 3 months and it is still in the back of my head. I have finally got around to trying to improve our test data, but I can't seem to find your slides... Did you post them anywhere? If not, can you? I think they would be really useful, even if they are in a very rough &amp;amp; ready, or even incomplete state. I am sure we can still get some benefit from them...

Thanks, and I hope all is well.

Shaun</description>
		<content:encoded><![CDATA[	<p>Hey Ted,<br />
I think a good measure of a talk is how long you think about it afterward. Well, it&#8217;s been over 3 months and it is still in the back of my head. I have finally got around to trying to improve our test data, but I can&#8217;t seem to find your slides&#8230; Did you post them anywhere? If not, can you? I think they would be really useful, even if they are in a very rough &#038; ready, or even incomplete state. I am sure we can still get some benefit from them&#8230;</p>
	<p>Thanks, and I hope all is well.</p>
	<p>Shaun</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Miguel Munoz</title>
		<link>http://tedyoung.blogsome.com/2008/02/27/intellij-idea-tip-change-background-color-for-read-only-files/#comment-22</link>
		<pubDate>Fri, 20 Feb 2009 02:01:30 +0000</pubDate>
		<guid>http://tedyoung.blogsome.com/2008/02/27/intellij-idea-tip-change-background-color-for-read-only-files/#comment-22</guid>
					<description>I've been doing this for years, and I recommend it. I've found that a light gray background (r=g=b=246) works best for me. 

I also do this in table cell renderers. I set the background to light gray if the cell isn't editable.</description>
		<content:encoded><![CDATA[	<p>I&#8217;ve been doing this for years, and I recommend it. I&#8217;ve found that a light gray background (r=g=b=246) works best for me.</p>
	<p>I also do this in table cell renderers. I set the background to light gray if the cell isn&#8217;t editable.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: William Pietri</title>
		<link>http://tedyoung.blogsome.com/2009/02/01/book-review-the-art-of-lean-software-development-1st-edition/#comment-21</link>
		<pubDate>Thu, 05 Feb 2009 10:23:36 +0000</pubDate>
		<guid>http://tedyoung.blogsome.com/2009/02/01/book-review-the-art-of-lean-software-development-1st-edition/#comment-21</guid>
					<description>Regarding not using source code control, I just met some folks who were using cp as their source code control system, so they are indeed out there.</description>
		<content:encoded><![CDATA[	<p>Regarding not using source code control, I just met some folks who were using cp as their source code control system, so they are indeed out there.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Curt Hibbs</title>
		<link>http://tedyoung.blogsome.com/2009/02/01/book-review-the-art-of-lean-software-development-1st-edition/#comment-20</link>
		<pubDate>Tue, 03 Feb 2009 06:07:13 +0000</pubDate>
		<guid>http://tedyoung.blogsome.com/2009/02/01/book-review-the-art-of-lean-software-development-1st-edition/#comment-20</guid>
					<description>Ok, I should have proof read that before posting. :-(

&quot;developing software with source control&quot; should have been &quot;developing software without source control&quot; -- the complete opposite!
</description>
		<content:encoded><![CDATA[	<p>Ok, I should have proof read that before posting. <img src='http://tedyoung.blogsome.com/wp-images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
	<p>&#8220;developing software with source control&#8221; should have been &#8220;developing software without source control&#8221;&#8212;the complete opposite!</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Curt Hibbs</title>
		<link>http://tedyoung.blogsome.com/2009/02/01/book-review-the-art-of-lean-software-development-1st-edition/#comment-19</link>
		<pubDate>Tue, 03 Feb 2009 06:04:48 +0000</pubDate>
		<guid>http://tedyoung.blogsome.com/2009/02/01/book-review-the-art-of-lean-software-development-1st-edition/#comment-19</guid>
					<description>Hi Ted, I am the primary author of this book.

I am truly sorry that you were mislead by the title into purchasing this book and the expectations that you had. For someone with your background I would have expected precisely your reaction.

Unfortunately, you are not part of the intended audience for this book, which is aimed squarely at the complete novice in bothe Lean and Agile. For people like us who have been steeped in this stuff for years, it can be easy to forget that there is a very large population of software developers who are not only are still practicing &quot;traditional&quot; software development, but don't really know anything about it either.

This book is meant to introduce such developers to the concepts and give some prescriptive guidance on how/where to dig deeper.

As an example, Chapter 3 talks about the importance of using source control and scripted builds. Why include this? Who in the right mind would ever consider developing software with source control or scriupted builds? Well, you'd be surprised... they are still out there!</description>
		<content:encoded><![CDATA[	<p>Hi Ted, I am the primary author of this book.</p>
	<p>I am truly sorry that you were mislead by the title into purchasing this book and the expectations that you had. For someone with your background I would have expected precisely your reaction.</p>
	<p>Unfortunately, you are not part of the intended audience for this book, which is aimed squarely at the complete novice in bothe Lean and Agile. For people like us who have been steeped in this stuff for years, it can be easy to forget that there is a very large population of software developers who are not only are still practicing &#8220;traditional&#8221; software development, but don&#8217;t really know anything about it either.</p>
	<p>This book is meant to introduce such developers to the concepts and give some prescriptive guidance on how/where to dig deeper.</p>
	<p>As an example, Chapter 3 talks about the importance of using source control and scripted builds. Why include this? Who in the right mind would ever consider developing software with source control or scriupted builds? Well, you&#8217;d be surprised&#8230; they are still out there!</p>
]]></content:encoded>
				</item>
</channel>
</rss>
