I usually think of coding as what programming has become over the years, copy-pasting code without much thought or deep understanding of what it does. This is almost generally true among web coders.
Programming indeed is complex, although the easiest thing to do is writing bad code, we will focus on things that are on us developers reach and not on what is under control of the .NET runtime.
We will focus on what makes good code better, anyone can start by asking non trivial questions about application architecture, algorithms, data structure selection, and so on.
The key to write better applications is that first you have to realize that there is no bug-free code, and always there will be time to run and fix problems on your applications.
Applications
Once you are confident that the application runs properly after debugging and testing, then you can start thinking about performance goals for your application. We will agree here that are enough smart developers working on the .NET runtime so we will focus on what is on our side as developers.
The biggest problem with performance is that usually comes late, and is the hardest problem to fix once it was baked into the design as a misrepresentation of data.
Data
All applications can be defined as algorithms that transform data and data transformations that happen on your applications can be a key aspect of the overall performance of it. The basic representation of data that will be manipulated places strong constraints on performance if it is poorly chosen -XML JSON DB- specially if is detected late into the product cycle, trying to change it then will be expensive.
Top comments (1)
How dare you sir, talking about my code like that!!?? 😄