About John Fuex

John Fuex has been working in software development professionally for over 15 years in Austin, Texas.  Although he still keeps his hands dirty in code as much as possible, he has spent much of the last decade managing a software development organization that included product development, consulting, testing and technical writing.

Specializing in Microsoft development and database platforms, he has created countless web, desktop and client-server applications. John’s current tool of choice is ASP.NET which he has worked with since it was introduced as what is now wistfully known as ASP classic. Despite a preference for C# and advanced skills with MS SQL Server, he remains an unabashed apologist of maligned and misunderstood technologies including MS Access and Visual Basic.

In his current role managing a development team, he enjoys most the opportunity to mentor other programmers and encourage them to reach the pinnacle of their potential. In many ways he finds it more rewarding to build a programmer than a program.

John holds an aging and hopelessly expired MCSD certification that he plans to update “one of these days,” an MCTS in SQL Server 2008,  is a Certified Document Imaging Archi-tech (CDIA), and has a BS in Information Technology degree from the University of Massachusetts where he graduated summa cum laude.

He has published two study guides for the MCSD Visual Basic certification exams and several articles in trade journals specializing in technology for litigators.

LinkedIn Profile
Stack Overflow Profile

If you’d like to comment privately about anything on this blog, or volunteer to write an article, you can contact John at the following address:
ContactInfo

2 Responses

  1. [...] platform: choosing the target language, mainly between VB.NET and C#. Today I found a great post by John Fuex on that subject, not inciting the war between both trenches but instead describing the process he [...]

  2. [...] John Fuex describing the process he and his company went through to solve the C# versus .NET dilemma when migrating [...]

Leave a Reply