Jay Harris

Jay Harris


Jay is a .NET developer, a software consultant, and is president of Arana Software (www.aranasoft.com). He has been developing on the web for 15 years, since he abandoned VB3 for JavaScript because he didn’t have to wait for a compile. With a career focus on end-user experience, he is a strong advocate of practices and processes that improve quality through code, ranging from automated testing, continuous integration, and performance analysis, to designing applications from the user’s perspective. Jay is also an active speaker and leader in the developer community, serving as President of Ann Arbor .NET Developers and is co-founder for Lansing Give Camp.


Originally from Rochester, New York, he and his wife, Amy, have lived in Michigan since 2003. They like Michigan, but still consider themselves tourists, and probably always will.

Contact Information:

Articles Authored

  • Anti-Patterns: TED (Test-Eventually Development)

    Last updated: Tuesday, February 19, 2019

    Published in: CODE Magazine: 2011 - January/February

    Software developers are good at writing applications. Testers are good at testing applications. In the software development world where separation of concerns is a never-ending quest, it seems logical to apply the rule to the software development cycle. “Let the developers code; QA can be responsible for making sure it works.” It provides an object-oriented management approach where each team is responsible only for what they are best at, and the two teams interface through one simple property, each: the result of their logic and expertise. The system is of logical design. It appears to be a logical pattern. Or so it seems.