= 27d567bc2d48d9f40e9ccc20ea370b15)
thomblake comments on Brute-force Music Composition - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (32)
Often if I'm trying to work out an algorithm to solve a problem that is possibly solvable by brute force, I'll start by writing a quick brute-force algorithm to perform the task. Then I'll leave it running in the background while I'm working on a better algorithm - that way, my time to implement the 'more efficient' algorithm is never more than the time it would have taken to brute force it.
But now that I think of it, I don't think I've actually used this solution since the days when computers were a lot slower.
So presumably you now just use the brute-force algorithm and forget about it?
Also, these must be one-off problems you're solving, right?
I like this... And if there is no more efficient algorithm you can find, then your brute-force has already gotten a head start.