Now that you have an ASP.NET application up and running, the next step is to understand the MVC pattern, which stands for Model-View-Controller, and forms the core of the ASP.NET MVC framework.
In his book, A Philosophy of Software Design, John Ousterhout argues against the common practice of breaking large classes into smaller ones.
In this article, we will look at how to get started with your first ASP.NET Core application. We will install the .NET framework, then use one of the generators to quickly get our application up and running in the browser. The whole process shouldn’t take more than ten minutes.
Here is a list of questions on ASP.NET that you might get asked in an interview. I originally wrote this 5000-word article for InterviewBit. Hope it helps for your next interview.
When programming, it’s easy to get by with a superficial understanding of many things. You can easily fool yourself by thinking that you are programming when you are blindly copy+pasting Stack Overflow answers.
Your choice of a programming language shapes so much of who you are as a software developer.
Software development is difficult. Especially if you are working on a 25-year old enterprise software that has gone through multiple platforms, technologies, and has seen multiple generations of developers. All of which makes it really hard to understand and difficult to develop.
The role of software testing is to provide information about the quality of a product. In his book Perfect Software and Other Illusions About Testing, Gerald Weinberg, who is one of my favourite writers, lists a few reasons why developers, testers, and managers avoid testing the product that they are ultimately responsible for.
John Ousterhout, in his book ‘A Philosophy of Software Design’ talks about the problem with having too many classes.