[HN Gopher] Naming Things Is Hard
       ___________________________________________________________________
        
       Naming Things Is Hard
        
       Author : Liriel
       Score  : 4 points
       Date   : 2022-08-11 06:33 UTC (1 days ago)
        
 (HTM) web link (www.fastruby.io)
 (TXT) w3m dump (www.fastruby.io)
        
       | shay_ker wrote:
       | This is more than just naming things. It's also that Ruby allows
       | you to monkeypatch _any_ method, even if it's a Kernel method or
       | already defined by a library or framework (like Rails).
       | 
       | It's extremely powerful, which is great! But I want a linter that
       | tells me, "Hey - you're monkeypatching that. I'm going to fail
       | this build unless you explicitly indicate you know what you're
       | doing".
       | 
       | I don't know of a convincing linter that has a complete solution
       | to this. Feel free to chime in if you know of one! I'm guessing
       | this is possible in Rubinius, but not sure about the standard
       | Ruby VM.
        
       | chmaynard wrote:
       | Or as paraphrased by Jeff Atwood:
       | 
       | There are two hard things in computer science: cache
       | invalidation, naming things, and off-by-one errors.
        
       | tempxyz wrote:
       | First heard it from a CS professor that it was the hardest
       | problem in computer science.
        
       ___________________________________________________________________
       (page generated 2022-08-12 23:01 UTC)