3 ms·
I sit with an FP expert (he might deny it, but he is). What I find, is that he takes a lot longer to get to the solution that I hack out in a day in Python3 (wi
by ggm 8y ago
I sit with an FP expert (he might deny it, but he is). What I find, is that he takes a lot longer to get to the solution that I hack out in a day in Python3 (with his assistance most of the time) but his solution has three interesting properties.
1) its usually founded on a very good understanding of the problem, and the abstractions inherent in the problem. If he can re-use the abstractions he has used before he does, to great effect in speed-to-solution
2) it is very usually correct. it is remarkably bug free because the Haskell typing removes a huge amount of ambiguity about the problem going in
3) he has absolutely no problem explaining what it does 3 months or more later.
I value these behaviours immensely. My own Python is usually buggy, often re-produces techniques I did a week ago, badly, and I can't explain why I used that lambda/map function.
- 2wrist 8y agoIt is really cool when you can find people like this. He sounds class!
- ggm 8y agoHe is!
- gugagore 8y agoI'm very curious about what kinds of problems these are. Any chance you can give us an idea?
- ggm 8y agoTypically processing data from logs, analyses of SQL state changes in the absence of good knowledge of the prior states. Some stuff which is aggregation over disparate inputs where a DSL can be useful. A lot of the time radix trees and other prefix/length matching logic is being used. Sometimes we're cross correlating different sources against disparate common keys. Some stuff connecting type: value record structures into JSON. We work a lot on ill-formed requests to refine data previously worked on with new questions. We work a lot on small distributed systems exploring eventual consistency and event sourcing. We work with quite large logfiles collected asynchronously, with poor clock alignment. So data buffering and sorting is not uncommon.