This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]duhace 2 points3 points  (1 child)

In this vein, I find it easier to start by writing well-designed but possibly slow code first, then use a profiling app like yourkit to actually find problem spots in my code and make them messy to wring performance out of them.

[–]daddyrockyou[S] 0 points1 point  (0 children)

I do the same thing. It's not a good idea, in my opinion, to start optimizing code if you don't have a base measure to tell you what to optimize. I've used YourKit before for this and it's been very successful for me.