Optimizing a Nonexistent Performance Problem
As a career game developer who's generally looked upon with at least some degree of respect by my peers, I am required to admit: i forgot i just turned off the CPU for 10ms at the end of my Debug.Log profiler function and just spent 2 days optimizing non-existent perf problems // eject the output in one unit print(res); System.Threading.Thread.Sleep(10);
A career game developer admits that they accidentally disabled the CPU for 10 milliseconds at the end of a Debug.Log profiler function, then spent two days optimizing performance problems that did not exist. The joke is aimed at programmers who overanalyze profiling data and optimize phantom bottlenecks caused by their own debugging code. EN: A career game developer admits that they accidentally disabled the CPU for 10 milliseconds at the end of a Debug.Log profiler function, then spent two days optimizing performance problems that did not exist. The joke is aimed at programmers who overanalyze profiling data and optimize phantom bottlenecks caused by their own debugging code.
computer code / компьютерный кодcode editor window / окно редактора кодаdebugging output / отладочный выводprofiler function / функция профилировщикаCPU / процессорperformance graph / график производительностиblack background / чёрный фонgreen comment text / зелёный текст комментарияwhite monospaced text / белый моноширинный текстrounded rectangle / скруглённый прямоугольник
- @gentoomemes / 2508 2023-02-16
- Type
- image
- Size
- 668×800 · 73.1 KiB
- Mood
- self-deprecating, absurd
- Language
- en
- Added