3 ms·
Learn to use a performance profiler and then a debugger/disassembler/whatever fit you needs. The profiler tells you where the slowdown happens, the rest then le
by nolok 3y ago
Learn to use a performance profiler and then a debugger/disassembler/whatever fit you needs. The profiler tells you where the slowdown happens, the rest then let you figure out what actually happens.
By learn to use I mean really do, it's like refactoring tools, it's sort of boring and tiring to learn those, you end skipping large parts because "yeah I already know / it's obvious", then you need one day for an emergency / something right now and feel like you're fighting against it.
For those three (and some others), the key to being very good at it is learning all the small tricks and details, when you don't need it, so the day you do it lets you skip 90% of the work.
As an overall point, I'm sure many people have various different experiences, but for myself while being in high school I needed to parse "replay" files for some games to extract and process information and allow players to post their replays to get stats on web forums, and it helped me to learn a great deal about how to properly reverse engineer and figure out stuff, things that I have no idea how I would have learned otherwise.
- beezlewax 3y agoExcuse my ignorance... but what refactoring tools do you speak of? I'm accustomed to the basic ones in VS code but I have a feeling I'm missing something greater judging by your comment
- jonathanlydall 3y agoThere are probably multiple refactoring tools which would fit the description by the parent. Personally I have experience with JetBrains ReSharper for (full) Visual Studio, it has loads of functionality which makes it very fast for me to navigate and refactor even very large C# projects. JetBrains has different products for many different languages and I expect they offer similar capabilities in each. Learning all the features at once is impractical, but if you learn a new one every now and again, after a few months or years you become incredibly proficient. I had a similar experience with conversation macros back in the day when I was a GM for WoW. You don’t make too many at once as you’ll never remember them all, instead you make them kind of as you need them, which tends to be situations like “this is the third time today I’m writing this long explanation”.