Re:Response to “Literate programming considered harmful”
by Chris2048 on Wednesday August 31, 2016 @10:15AM
(#12398433)
> I'm not going to summon up simple scarecrow arguments, but for software that makes money, I do not want your clever pattern with comments that saves a microsecond behind a 60 millisecond latency api
Is that not a strawman argument?
Re:Response to “Literate programming considered harmful”
by 3pt14159 on Wednesday August 31, 2016 @10:23AM
(#12398491)
You are right, that isn't worded the way I intended (not the least because I misremembered the name). I meant to say code examples. For example:
# double the counts.
counts.map! { |count| count *= 2 }
Is the type of strawman I intended to avoid.
And I'm not saying this because I've always had this view, I used to be too clever. I wrote a automatic caching and automatic windowing API client library. The thing was impossible for anyone else to alter because the mental model was too complex. Now I try to keep complexity only where it is needed and I try to keep the complexity quarantined from the interface as much as possible.
Huge projects like Rails can be clever while still making my life easier because they have an army of smart people finding the edge cases, but for most stuff that isn't the case.