Information Overload: The Amount of Disparate Technologies

I’ve been thinking quite a bit lately about the state of the current software development world compared to how it was when I first turned professional over 10 years ago, and it’s a staggering difference to say the least. I cut my programming teeth on VB6, VC++, and classic ASP. CSS and HTML were still in their infancy (blink tag anyone?), and almost all corporate software was done using a 2 tier model, or thin client wrappers around legacy mainframe apps (COBOL/AS400 anyone?). I was lucky in some regards in that .Net came out during the first year of my professional career, so that I could learn it from the ground up. We’re on version 4.0 now, and the amount of class libraries that ship in the System.* and Microsoft.* namespaces has more than doubled since the early betas. Learning the entire 4.0 BCL from scratch would be daunting to say the least. During the early betas of .Net, there were plenty of times where I wondered what the hell I had gotten myself into.

Now enter the big bad web, which unless you swear up and down by C++/STL/ATL/COM (code dinosaur in other words) you absolutely must write applications for. A cursory list of the technologies we as web developers have to know intrinsically:

  1. HTML (duh, and now with HTML5, the game has really changed)
  2. CSS (CSS3 is also a game changer)
  3. JavaScript
  4. The DOM
  5. jQuery
  6. AJAX
  7. JSON
  8. REST/SOAP
  9. MVC (not required, but very useful)
  10. XML
  11. XSLT
  12. XSD/DTD
  13. HTTP/TCP/IP
  14. DNS/DHCP
  15. Ad nauseam…(feel free to add to this list)

Combine the above with the fact that each of the big 4 browsers (IE, Firefox, Chrome, and Opera…yes I left Safari off this list because on the LAN it is very rarely used) have their own individual quirks as to how they implement the standards, and also how individual dynamic web languages generate code, and it gets pretty maddening. Don’t even get me started on the nastiest language of all, SQL (though data wrapping generation tools are getting quite sophisticated, specifically LINQ and the Entity Framework in .Net, as well as ActiveRecord in Ruby…it’s quite possible to write entire applications now without writing a single line of SQL, though all developers need to understand the underlying SQL that gets generated).

Then we get into the language/platform agnostic parts of software engineering. Learning new languages, performing object oriented analysis and design, reusing code, eliminating cross cutting concerns (dependency injection), configuring servers both physically and logically, database design (which thousands of books are devoted to), production debugging, unit testing, integration testing, functional testing. I could go on, and on, and on…the point is that it’s pretty overwhelming when you take a step back and look at all the different moving parts that make a useable application, well…useable. Sometimes I take for granted what I’ve learned after over a decade in this industry and have to remind myself that (while I’m still by far not an expert) I was once completely new. But I also wonder what it would be like to get into this industry now, given that the web has changed EVERYTHING about what we do for a living, and hell…how we live outside of our careers in general. Remember life before Facebook? Before Wi-Fi? Before smartphones? Before email?

When I was at Columbia University, I’d often walk by Rodin’s “The Thinker” and could feel exactly what it was created to represent: The struggle with dilemmas, and also the frustration of trying to understand and make sense of it all. In the end, what I think makes a software developer successful is the ability to adapt, not fight change, and the drive to constantly improve ourselves and learn new tools. The programming landscape is constantly evolving, and hell I fight it from time to time (e.g. I am a complete CSS idiot, and have been fighting that for a while now…mainly because it’s such a quirky spec and implemented very poorly across different browsers)…the biggest change in my entire career was basically forgetting VB6, learning C# and Java, and never looking back. I wonder what the next big change will be (by big, I mean something like The Web, or moving from different languages)? If I had to guess, it’s going to be something in the mobile space and how we access information there, and if I had a preference, it would be moving away from RDBMS systems and utilizing cloud solutions without having to worry about what the underlying persistence layer for data is, e.g. more platform agnosticism. As a developer, I just like to create without being bogged down with the underlying implementation details. I used to love the details, but just want to produce things that “just work” at this point. Frameworks are moving towards this more and more, and I welcome it. so here’s to hoping for more high level development tools that allow us to create more, and drive that next level of innovation.

No comments yet