News

Q&A with Chris Klug: Web Development in 2018

Expert Web developer Chris Klug helps makes sense of today's complicated Web dev ecosystem and the tools and technologies that are emerging at a dizzying pace.

Being a Web developer is challenging. The Web dev world changes at a pace that would make most people dizzy. And if you are working in the Microsoft space and using Visual Studio, for example, the release cadence of the IDE is way too slow to keep up. You have to go outside your comfort zone and locate other tools that can help you -- tools that will do what you want, but will still work with your existing tools.

At the upcoming Visual Studio Live! conference at Microsoft headquarters in Redmond, Wash., Aug. 13-17, expert Web developer Chris Klug will present a full-day workshop to help attendees deal with that and many other issues. Specifically, Klug will detail:

  • How Web development has changed a lot in the last few years.
  • The available tools that can make life a lot easier.
  • Different technologies available to Web developers.

We caught up with Chris recently to get his thoughts on the most significant technology change in the past few years, his favorite Web dev tech, the importance of being polyglot and more.

Of course, a lot has changed in Web development over the past few years, but what do you think has been the most significant technology change or release that has affected developers, either back-end or front-end (or both)?
I think the biggest change has been the introduction of Node and npm. It opened up a whole world of things that we could do. Whether you are building full end-to-end application in JavaScript, or just running Webpack or Gulp for your builds, Node is the reason it can be done. Not to mention that we finally found a common place to store all of our client-side resources. We don't need to run around to a bunch of different locations and download scripts, or try to hack it in to a package manager like NuGet that wasn't great for that kind of stuff. Having that said, I think on the server side, ASP.NET MVC and Core has made a huge difference. I know it isn't new, but when it came out, it really changed our way of embracing the Web for what it is. Working with it instead of trying to abstract it away.

What have become your favorite Microsoft and non-Microsoft Web technologies for Web development?
That kind of ties in with the previous question. Node, npm and ASP.NET Core are my favorite things to be honest. And Visual Studio Code! It is so nice to get out of the heavy Visual Studio when doing Web. Not that I don't like Visual Studio, it's awesome, but it is getting quite heavy.

Do you develop on a .NET stack, LAMP stack, or both? Do developers need to be cross-platform now?
I'm .NET only to be honest, but being cross-platform has some huge advantages I think.

"The more polyglot you are, the more likely you are to pull in knowledge and influences from different platforms in your project to get the best solution."

Chris Klug, Senior Software Developer, Tretton37

The more polyglot you are, the more likely you are to pull in knowledge and influences from different platforms in your project to get the best solution. Different platforms have a lot of different interesting, and often opinionated ways of doing things, which can be very interesting to look at and pull influences from.

Do you have any favorite secret tools or plugins you can recommend that readers might not know about?
Actually I run my environment very clean. As I do a lot of presenting around the world, I want to have as little magic as possible so it doesn't confuse the attendees, or have them focus on "the wrong thing."

What is the one thing all Web developers should do in 2018?
Challenge themselves to try new things, such as couple of new frameworks and/or a new editor. Trying different things, and seeing other things than what we are used to is a great way to grow.

What is the one thing all Web developers SHOULDN'T do in 2018?
jQuery ... nah, just kidding! Kind of.... But to be honest, the most important thing to not do, is to not stagnate and shy away from new things.

What else do you want to share about changes in Web development ahead of your full-day workshop at Visual Studio Live! Redmond at Microsoft HQ in August?
I just want to say that anyone who is considering to attend the workshop should come well rested and with an open mind, because there will be a lot of stuff to cover in just one day.

About the Author

Becky Nagel serves as vice president of AI for 1105 Media specializing in developing media, events and training for companies around AI and generative AI technology. She also regularly writes and reports on AI news, and is the founding editor of PureAI.com. She's the author of "ChatGPT Prompt 101 Guide for Business Users" and other popular AI resources with a real-world business perspective. She regularly speaks, writes and develops content around AI, generative AI and other business tech. Find her on X/Twitter @beckynagel.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube