|
|
|
|
|
|
by uxp
5539 days ago
|
|
|
> See if you can find some bottleneck in one of your Python/Ruby/Perl apps that's chewing a lot of CPU time. I found that hard to do as a starting developer who didn't know what was actually a bottleneck in my code, but I did have a particular library/gem that I wrote myself that did a few things I constantly needed (think of authentication in a web app, it's almost always included). So I rewrite it in C. It didn't really make it faster, or better, but I learned a bunch of C. |
|
|
That's what a profiler is for! Even experienced developers use them, it's the only reasonable way to find bottlenecks.
> It didn't really make it faster, or better, but I learned a bunch of C.
That works too! :)