Hi Cory I think in theory many of your points are valid and certainly are in practice for many…
fresnobob
42

Hi Bob — Your story resonates. It actually sounds familiar to many I’ve seen. I work in a .NET shop where many C# developers also do JS. But it’s clearly not their primary interest.

Recently we re-organized to have a dedicated UI development team. I believe this is the future. As you mentioned, there is simply too much to know to expect people to be proficient in rich client-side development, and the middle tier, and data access, and so on.

This structure has really helped up improve our game. And through this pattern we’re helping improve everyone’s practices by embedding with teams and working with them to build modern client-side UIs. We’re also now using a rich starter kit for all new projects so that we get bundling, testing, minification, and so on for “free”. It’s just there by default. I agree that trying to do everything up front is really overwhelming. That’s precisely why I created the new course — to help give people a clear map on how to alleviate the pain by making these decisions once and for all.

You mentioned that the only thing you feel like you gained was the lack of postback. If that’s the case, perhaps your app just wasn’t a great candidate for client-side rendering in the first place? As I mentioned in the article, there are many other benefits that just may not have applied to your app.

But I really appreciate your thoughtful response!

Show your support

Clapping shows how much you appreciated Cory House’s story.