<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;CkMCQ3szfip7ImA9WhRRFkg.&quot;"><id>tag:blogger.com,1999:blog-2486195259155082212</id><updated>2011-11-30T02:54:22.586-08:00</updated><category term="c#" /><category term="quality assurance" /><category term="regex" /><category term="design patterns" /><category term="java" /><category term="qa" /><category term="software" /><category term="software engineering" /><category term="code quality" /><category term="programming" /><category term="code complete" /><category term="patterns and practices" /><category term="regexp" /><category term="code" /><category term="testing" /><category term="regular expression" /><category term="methodologies" /><category term="shunting-yard" /><category term="testing tools" /><category term="browsers" /><category term="web testing" /><category term="calculator" /><title>Nathandelane, Father, Programmer, High Priest</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blog.nathandelane.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://blog.nathandelane.com/" /><author><name>Nathan Lane</name><uri>http://www.blogger.com/profile/11094451213403897606</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/-kaavpMZMkw4/TYEC7Z1IW0I/AAAAAAAAAIQ/1qwwA6Iy_Fo/s220/Me-2010.png" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>7</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/NathandelaneFatherProgrammerHighPriest" /><feedburner:info uri="nathandelanefatherprogrammerhighpriest" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly></feedburner:browserFriendly><entry gd:etag="W/&quot;AkQCQHY8fSp7ImA9WhZTGEw.&quot;"><id>tag:blogger.com,1999:blog-2486195259155082212.post-4883239581006481519</id><published>2011-03-16T11:31:00.000-07:00</published><updated>2011-03-22T11:26:01.875-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-22T11:26:01.875-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="code complete" /><category scheme="http://www.blogger.com/atom/ns#" term="code quality" /><category scheme="http://www.blogger.com/atom/ns#" term="software" /><category scheme="http://www.blogger.com/atom/ns#" term="quality assurance" /><category scheme="http://www.blogger.com/atom/ns#" term="software engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="design patterns" /><category scheme="http://www.blogger.com/atom/ns#" term="methodologies" /><title>How to Write Software Right</title><summary>I have been working on, testing, developing, breaking, engineering, architecting, designing, and creating software for over twenty years. Seven and a half of them have been professional years. I have been in school, participating in Computer Science related activities for seven of my twenty years. I have ready thousands of books, essays, tutorials, forums, blog posts, and reports on various </summary><link rel="replies" type="application/atom+xml" href="http://blog.nathandelane.com/feeds/4883239581006481519/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.nathandelane.com/2011/03/how-to-write-software-right.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/4883239581006481519?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/4883239581006481519?v=2" /><link rel="alternate" type="text/html" href="http://blog.nathandelane.com/2011/03/how-to-write-software-right.html" title="How to Write Software Right" /><author><name>Nathan Lane</name><uri>http://www.blogger.com/profile/11094451213403897606</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/-kaavpMZMkw4/TYEC7Z1IW0I/AAAAAAAAAIQ/1qwwA6Iy_Fo/s220/Me-2010.png" /></author><thr:total>2</thr:total></entry><entry gd:etag="W/&quot;DEUEQ3c8fip7ImA9Wx5bFkg.&quot;"><id>tag:blogger.com,1999:blog-2486195259155082212.post-7596262239083880620</id><published>2010-10-21T11:06:00.000-07:00</published><updated>2010-11-01T17:03:22.976-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-11-01T17:03:22.976-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="code complete" /><category scheme="http://www.blogger.com/atom/ns#" term="code quality" /><category scheme="http://www.blogger.com/atom/ns#" term="patterns and practices" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><category scheme="http://www.blogger.com/atom/ns#" term="programming" /><title>Patterns and Practices: Scope and Type Inference Through Syntactic Sugar</title><summary>Code CompleteOnce again I'm referring to Code Complete. Code Complete taught me a lot of things and coding style is one of those that I hold important to this day. Let me preface this by stating that Code Complete was built around C++ and later C# coding, still I believe that utilizing coding style that is indicative of scope and usage makes programs more maintainable. I also believe that more </summary><link rel="replies" type="application/atom+xml" href="http://blog.nathandelane.com/feeds/7596262239083880620/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.nathandelane.com/2010/10/patterns-and-practices-scope-and-type.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/7596262239083880620?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/7596262239083880620?v=2" /><link rel="alternate" type="text/html" href="http://blog.nathandelane.com/2010/10/patterns-and-practices-scope-and-type.html" title="Patterns and Practices: Scope and Type Inference Through Syntactic Sugar" /><author><name>Nathan Lane</name><uri>http://www.blogger.com/profile/11094451213403897606</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/-kaavpMZMkw4/TYEC7Z1IW0I/AAAAAAAAAIQ/1qwwA6Iy_Fo/s220/Me-2010.png" /></author><thr:total>0</thr:total></entry><entry gd:etag="W/&quot;CEQCRX48eCp7ImA9WxBbEkk.&quot;"><id>tag:blogger.com,1999:blog-2486195259155082212.post-1179529822250385966</id><published>2010-02-11T13:09:00.000-08:00</published><updated>2010-03-10T09:32:44.070-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-10T09:32:44.070-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="patterns and practices" /><category scheme="http://www.blogger.com/atom/ns#" term="programming" /><title>Patterns and Practices: Valid Reasons to Create a Routine</title><summary>Code CompleteSeveral months ago I finished reading Steve McConnell's Code Complete 2nd Edition. I learned a lot from it and took notes. Some of what the book contained were methodologies that I already knew and used on a daily basis. Other parts of the book opened my eyes to a higher road in programming. My goal in reading the book was to become a better programmer, a better program designer or </summary><link rel="replies" type="application/atom+xml" href="http://blog.nathandelane.com/feeds/1179529822250385966/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.nathandelane.com/2010/02/patterns-and-practices-valid-reasons-to.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/1179529822250385966?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/1179529822250385966?v=2" /><link rel="alternate" type="text/html" href="http://blog.nathandelane.com/2010/02/patterns-and-practices-valid-reasons-to.html" title="Patterns and Practices: Valid Reasons to Create a Routine" /><author><name>Nathan Lane</name><uri>http://www.blogger.com/profile/11094451213403897606</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/-kaavpMZMkw4/TYEC7Z1IW0I/AAAAAAAAAIQ/1qwwA6Iy_Fo/s220/Me-2010.png" /></author><thr:total>0</thr:total></entry><entry gd:etag="W/&quot;CEAHSXw7eip7ImA9WxBWFko.&quot;"><id>tag:blogger.com,1999:blog-2486195259155082212.post-1393704279581516544</id><published>2010-02-08T13:01:00.000-08:00</published><updated>2010-02-08T15:45:38.202-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-08T15:45:38.202-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="qa" /><category scheme="http://www.blogger.com/atom/ns#" term="testing tools" /><category scheme="http://www.blogger.com/atom/ns#" term="quality assurance" /><category scheme="http://www.blogger.com/atom/ns#" term="browsers" /><category scheme="http://www.blogger.com/atom/ns#" term="testing" /><category scheme="http://www.blogger.com/atom/ns#" term="web testing" /><title>Web Testing Tools</title><summary>For six years now I have served my time as an IT professional in the Quality Assurance sector. Over that period of time I have tested a wide variety of systems from desktop applications to video games, and from web sites to embedded wifi networked systems. All of these systems required a different means to test them effectively. In each system the same mindset (detail-oriented) was employed, but </summary><link rel="replies" type="application/atom+xml" href="http://blog.nathandelane.com/feeds/1393704279581516544/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.nathandelane.com/2010/02/web-testing-tools.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/1393704279581516544?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/1393704279581516544?v=2" /><link rel="alternate" type="text/html" href="http://blog.nathandelane.com/2010/02/web-testing-tools.html" title="Web Testing Tools" /><author><name>Nathan Lane</name><uri>http://www.blogger.com/profile/11094451213403897606</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/-kaavpMZMkw4/TYEC7Z1IW0I/AAAAAAAAAIQ/1qwwA6Iy_Fo/s220/Me-2010.png" /></author><thr:total>1</thr:total></entry><entry gd:etag="W/&quot;DkcNRHY-fyp7ImA9WxBWFE0.&quot;"><id>tag:blogger.com,1999:blog-2486195259155082212.post-4375539576854563037</id><published>2009-12-03T10:47:00.000-08:00</published><updated>2010-02-05T13:08:15.857-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-05T13:08:15.857-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="code quality" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><category scheme="http://www.blogger.com/atom/ns#" term="programming" /><title>Code Quality</title><summary>As I program more and more the quantity of files, classes, enumerations, structs, and fields increases dramatically. With that increase comes the ever increasing possibility of defects. When I am programming I try to follow a set of guidelines known as a programming style guide. Style guides help us to be consistent in whatever we're doing. It is probably more common for style guides to be used </summary><link rel="replies" type="application/atom+xml" href="http://blog.nathandelane.com/feeds/4375539576854563037/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.nathandelane.com/2009/12/code-quality.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/4375539576854563037?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/4375539576854563037?v=2" /><link rel="alternate" type="text/html" href="http://blog.nathandelane.com/2009/12/code-quality.html" title="Code Quality" /><author><name>Nathan Lane</name><uri>http://www.blogger.com/profile/11094451213403897606</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/-kaavpMZMkw4/TYEC7Z1IW0I/AAAAAAAAAIQ/1qwwA6Iy_Fo/s220/Me-2010.png" /></author><thr:total>0</thr:total></entry><entry gd:etag="W/&quot;D04CSH0zcSp7ImA9WxNWFEg.&quot;"><id>tag:blogger.com,1999:blog-2486195259155082212.post-4811521385600610540</id><published>2009-10-13T09:16:00.000-07:00</published><updated>2009-10-13T10:46:09.389-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-13T10:46:09.389-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="programming" /><category scheme="http://www.blogger.com/atom/ns#" term="calculator" /><category scheme="http://www.blogger.com/atom/ns#" term="c#" /><category scheme="http://www.blogger.com/atom/ns#" term="methodologies" /><title>Two or Three Ways to Do Things</title><summary>As I continually program throughout my career and daily life, I come across the problem often that there are simply too many ways to program a system. The other problem is that there really isn't much of a correct way to program any specific system. It seems that the means to an end often involves trends. To clarify, I have been trying to program a decent text-based calculator for some time now. </summary><link rel="replies" type="application/atom+xml" href="http://blog.nathandelane.com/feeds/4811521385600610540/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.nathandelane.com/2009/10/two-or-three-ways-to-do-things.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/4811521385600610540?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/4811521385600610540?v=2" /><link rel="alternate" type="text/html" href="http://blog.nathandelane.com/2009/10/two-or-three-ways-to-do-things.html" title="Two or Three Ways to Do Things" /><author><name>Nathan Lane</name><uri>http://www.blogger.com/profile/11094451213403897606</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/-kaavpMZMkw4/TYEC7Z1IW0I/AAAAAAAAAIQ/1qwwA6Iy_Fo/s220/Me-2010.png" /></author><thr:total>0</thr:total></entry><entry gd:etag="W/&quot;D04MQHY_fyp7ImA9WxNQFkk.&quot;"><id>tag:blogger.com,1999:blog-2486195259155082212.post-1177877683727188937</id><published>2009-09-22T10:54:00.000-07:00</published><updated>2009-09-22T11:59:41.847-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-22T11:59:41.847-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="regexp" /><category scheme="http://www.blogger.com/atom/ns#" term="regular expression" /><category scheme="http://www.blogger.com/atom/ns#" term="shunting-yard" /><category scheme="http://www.blogger.com/atom/ns#" term="regex" /><category scheme="http://www.blogger.com/atom/ns#" term="calculator" /><category scheme="http://www.blogger.com/atom/ns#" term="c#" /><title>The Programmer's Calculator</title><summary>A while back I determined that I wanted an easy to use text-mode calculator that could perform all of the calculations I required in my job as a web programmer. Often these are simple arithmetic. As I set out to write my first calculator that was more than a simple GUI with buttons to click, I began asking questions about the best method to use in the process. I already knew about postfix </summary><link rel="replies" type="application/atom+xml" href="http://blog.nathandelane.com/feeds/1177877683727188937/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.nathandelane.com/2009/09/programmers-calculator.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/1177877683727188937?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2486195259155082212/posts/default/1177877683727188937?v=2" /><link rel="alternate" type="text/html" href="http://blog.nathandelane.com/2009/09/programmers-calculator.html" title="The Programmer's Calculator" /><author><name>Nathan Lane</name><uri>http://www.blogger.com/profile/11094451213403897606</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://1.bp.blogspot.com/-kaavpMZMkw4/TYEC7Z1IW0I/AAAAAAAAAIQ/1qwwA6Iy_Fo/s220/Me-2010.png" /></author><thr:total>0</thr:total></entry></feed>

