It does not matter how slowly you go, so long as you do not stop.
ASP.NET Web Forms and ASP.NET MVC envision the HTTP request in different ways, although both frameworks share the same runtime environment up until ASP.NET Core 1.0. In ASP.NET Web Forms, each request is directed at displaying a given ASPX page. As a developer, you design a website around a bunch of pages. Each page offers a bunch of clickable elements to trigger an action. No action is clearly identified by name and parameters; all actions, instead, are postbacks the page makes to itself. Put another way, in ASP.NET Web Forms you handle a user’s clicking, modify the state of the page, and render it back.
In ASP.NET MVC, the granularity ...