tag:blogger.com,1999:blog-7229412.post113082503910945832..comments2023-10-02T07:19:19.258-05:00Comments on Geek Goes Meow: The Near-Future of ITShellyhttp://www.blogger.com/profile/01779259600485125169noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7229412.post-1135872764509051782005-12-29T10:12:00.000-06:002005-12-29T10:12:00.000-06:00Interesting observations. I followed your link ov...Interesting observations. I followed your link over from a comment you made on Digg about hot tech skills in '06.<BR/><BR/>I do take issue with #1 and #3 on your list, however, and I think this is more than just a semantic point. Since many new application development efforts begun today and in the future are for web based applications (due to reduced deployment/support costs, universal accessibility, etc.), I'm not sure I understand the distinction you make between "application development" (number 1) and "web programming" (number 3). If by application development you mean fat client/desktop-side executable programs, then I understand and support the claim that the field is dead or at least dying. However, many companies still make the business decision to build software in-house (vs. procure a COTS application), and many of those development efforts are in building web applications. So web programmers are getting hired to build those applications and, as you stated, this is a high growth area.<BR/><BR/>So does "application development" mean fat client development?cdthompso1https://www.blogger.com/profile/12173947765374849608noreply@blogger.com