Making your code more permanent is difficult. In this section, you will learn how to profile your code to generate performance reports. Next, you will learn how to use those reports to help optimize your code.
Worrying about performance too soon will waste your time and give you a minimum return on investment. When you try and guess where the bottlenecks may be, you might be right 50% of the time. The problem is you will also be wrong 50% of the time. Speaking from experience, premature optimization will waste days/weeks/months and at least 50% of that time will be wasted.
If you want a quick website, I recommend that you set-asides time after your MVP has been delivered. It's only after MVP can you can figure out where the worst bottlenecks will be.
The performance conversation is usually an interesting conversation. At the beginning of a project I usually warn a client that they will need to set aside a period of time after the main development work and testing has been done to make their new [...]
In today's article, I'm going to go over how you can implement a global caching solution that can switch between Global, Session and Disabled. On any web project, performance is key. Your website users will go elsewhere if a page takes too long to [...]