<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div><blockquote type="cite"><font class="Apple-style-span" color="#000000">[Snip]</font></blockquote><blockquote type="cite">So, I appreciate knowing about such opportunities, even though there's no<br></blockquote><blockquote type="cite">way I'd apply for this particular gig at this particular time, because I<br></blockquote><blockquote type="cite">agree with Aahz that it would be rude to waste people's time that way.</blockquote>[Snip]<br><br>There are some [things] you can learn while doing a job, that's the job<br>of an engineer. </div></blockquote><br></div><div>+1 I would argue that it rude to immediately dismiss a software engineer solely because he/she hasn't encountered a particular subclass of programming problems. Software Engineers that are worth their salt are capable of applying their programming expertise to various types of problems. And in a market like today's: developers are going to exercise this flexibility even more so. That aside: I can site plenty of examples of software engineers that have worked in a variety of different problem domains throughout their career. In fact, I started writing software in the consumer electronics industry, then moved on to server-side mobile service development, and after a brief stint in writing code for a company specializing in geocoding and mapping services, my current gig involves building software for recruiting and employee performance management.</div><div><br></div><div>But, don't take my word for it. Do read: <a href="http://www.joelonsoftware.com/articles/fog0000000073.html">http://www.joelonsoftware.com/articles/fog0000000073.html</a>.</div><div><br></div><div>Ryan</div></body></html>