freenode/#shirakumo - IRC Chatlog
Search
12:44:18
selwyn
i have a kind of dual attitude in that while i believe that it is important to prove stuff, one thing i don't like is having to implement an algorithm in code (unless it's a pedagogical exercise)
12:45:11
selwyn
that's when i say 'this algo has been around for years, why hasn't someone solved the problem of implementing it in the best/sanest way so i can just use it'
14:03:26
|3b|
ACTION thinks both doing proofs and implementing algos are important, if you want to be able to do more of them in the future
14:04:42
|3b|
but there usually isn't a need for a "better" proof of something, unlike implementations of algorithms, where there are lots of ways to measure "better"
14:06:56
|3b|
but also, time is limited, so it is reasonable to specialize in one or the other, or something completely different, particularly if you seem to be better at (or even just more interested in) one of them
14:20:31
Shinmera
I love the design aspects of programming -- meaning everything except the proof that it's working.
14:35:38
selwyn
people do try to construct alternative 'elementary' proofs using as few assumptions/areas as possible, it's quite popular in number theory
14:36:01
selwyn
i wouldn't say there's a 'need' for it though, it's motivated by an aesthetic sensibility
16:20:55
|3b|
right, but an ugly proof doesn't stop you from using the results to prove something else, but an implementation of an algo using too much ram might prevent it from being useful
16:22:00
|3b|
(or too much CPU, and the 2 can frequently be traded for eachother, so you can't say either "minimal ram" or "minimal CPU" implementation is always better)
17:10:56
selwyn
i respect those who design algorithms that are efficient from the pov of making best use of the cpu cache and keeping memory down and being fast
17:11:54
|3b|
yeah, optimization at that level can be a fun puzzle, just usually too far down the project stack for me to get to :/