FPtje/FProfiler
1
0
Fork 0
mirror of https://github.com/FPtje/FProfiler.git synced 2025-03-04 03:03:14 -05:00
Code Issues Packages Projects Releases Activity

wil -> will spelling

Browse Source
This commit is contained in:
FPtje 2016-05-01 20:54:37 +02:00
parent 51e2a4c12c
commit 6d52b3ab59
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.MD
View File

@ -58,4 +58,4 @@ What do I mean by macro-optimisation/the big guys you ask? Think of reducing an
That's where the profiler comes in. Always mistrust what you **think** is a big performance hog is, **measure** it. Even the assumptions of people who have optimising code as their profession are often proven wrong by the profiler. Don't be smug and think you can do any better.
When working on performance, the profiler is to be your guide. The profiler is to tell you what to optimise. Do not bother with anything other than the most expensive functions for you wil be wasting your time.
When working on performance, the profiler is to be your guide. The profiler is to tell you what to optimise. Do not bother with anything other than the most expensive functions for you will be wasting your time.