Need some cases against sticking with WebForms and in favor of a more modern tech stack
I recently was transferred from the database/ETL development team to help out the web development team (I have several years of ASP.NET and C# experience). They still use ASP.NET WebForms with Telerik's RAD Controls and the manager is adamant that this is better and faster because you don't need to write the Javascript yourself.
I have found their coding style to be very reminiscent of 2003-2005 era coding: Most logic in code behind, layer upon layer upon layer of chaining methods, etc. basically the "Smart UI" antipattern. The VP of software didn't seem to be aware that they were still using WebForms as he was a bit shocked when we discussed it during the meeting where he told me I was being reassigned to their team.
Since there's no way that I can tell to run both ASP.NET Web forms and something more modern like Razor Pages in the same app (if there was then I'd just suggest we do a portion in the new style to show it can be done better), I'd like to at least start making some bullet points for why future applications should be done using a more modern approach instead of sticking with the WebForms approach. I know the biggest hurdle to get over will be the learning curve (although Razor Pages looks easier than WebForms to me, and I used WebForms for a couple of years myself) and the fact the Telerik UI controls let you do a lot of client-side logic without writing it yourself so the idea is that it's faster to get things written by using the controls.
What other talking points should I be writing down to make when the time comes? I'd likely need to involve the VP as I'm sure the manager won't listen to me alone as she is rather set in her ways.
0 comments:
Post a Comment