Are you passionate about software development?  Do you love to share your knowledge with others?  Do you like working in a vibrant, fun culture working on the latest and greatest technologies with other smart and passionate people?  If so, I think I may have your dream job right here.

We're looking for another guidisan to help craft guidance using best practices for .NET development.  The word guidisan ('gId-&-z&n) comes from a blending of "guidance" and "artisan," which really speaks to the heart of the matter.  We're looking for software artisans who have the experience, know-how, and gumption to explore strange new technologies, to seek out new applications and new user scenarios, to boldly go where other developers only dream of going in order to provide deep, technical guidance for their colleagues and peers.

What do guidisans do? 

• Help gather, specify, and document application vision, scope, and requirements.
• Take application requirements and create an application design that meets the requirements and follows best known practices for both Microsoft .NET and Infragistics products.
• Implement applications following requirements, best practices, and design specifications.
• Create supplemental content such as articles, white papers, screencasts, podcasts, etc. that help elucidate example code and applications.
• Research emerging technologies and create prototypes based on emerging technologies.
• Contribute to joint design sessions as well as coding and design discussions.

What do I need to qualify?

• Bachelor’s Degree.
• 4+ years of full-time, professional experience designing and developing business applications.
• 2+ years designing and developing.NET applications (UI development in particular).
• Be able to create vision, scope, and requirements documents based on usage scenarios.
• Demonstrated experience with object-oriented design; familiarity with behavior-driven design, domain-driven design, and test-driven development a plus.
• Demonstrated knowledge of best practices for .NET application development.
• Accept and provide constructive criticism in group situations.
• Follow design and coding guidelines.
• Clearly communicate technical concepts in writing and speaking.

If you think this is your dream job, contact me.  Tell me why it's your dream job and why you think you'd be the next great guidisan.

I just ran across what appears to be a nasty bug in Firefox today.  Without explaining why I'm doing it, suffice it to say that I just wanted to call a script in a parent frame (from an IFrame) that ultimately results in an XMLHttpRequest.  It works in IE 6 and 7, but in FF 1.5, it just doesn't.  In fact, the result of the request seemed to be the result of the previous request that was executed, and to make it more interesting, the responseXML returned null while the text showed the results of the previous call.

Oddly enough, no errors were thrown--it acts like a regular call with an error free response; it just doesn't actually seem to perform the request and in the meantime loses its XML document.

Anyways, I was starting to despair when I ran across this blog post.  It seems I'm not the only one who's bumped into this one (or some variation), yet I must say it was hard to find that blog entry based on my searching.  So I want to raise its visibility with this post. 

For me, the solution was simply to use window.top.setTimeout(myfun, 50).  That appears to give FF the context it needs to properly execute the request.  But of course, that breaks it for IE, so you gotta do a check for Firefox (e.g., if (navigator.userAgent.indexOf('Firefox') != -1)) do the timeout if so; otherwise, make the call directly.

Phwew!  Thanks to those who've gone before me!