When we discuss code profiling with a team of developers, they often say, "We don't have time to profile our code: that's why we have performance testers," or, "If your application or system runs very slowly, the developers and performance testers may suggest the infra team to simply add another server to the server farm."
Developers usually look at code profiling as additional work and as a challenging process. Everyone in the project enters the phase of performance and memory profiling only when something is seriously a problem with performance in production. Due to a lack of knowledge and experience on how to profile and how various profilers work with different profiling types, many of us will fail to identify and address performance problems. As 70 to 80 percent of performance problems are due to inefficient code, it is recommended to use code profiling tools to measure and analyze the performance degradations at the early stages of development. This will help developers and performance engineers to find and fix the performance issues early which can make a big difference overall, especially if all the developers are testing and profiling the code as soon as they write.