Never edit a method, always rewrite it?

Re:Never edit a method, always rewrite it? by GreaterFool on Monday December 04, 2017 @05:59AM (#15843012)

Saw the headline, first though "I'll bet this is about dynamically typed languages", and lo and behold

> At a recent RubyConf...

EDIT: just wanted to add that when I code in dynamically typed languages I'm inclined to do the same thing. Without rigidity provided by a strong type system it's too easy to mess things up. That's why I prefer strongly typed languages so I can benefit from the structure they enforce.

[ Parent | on HN ]

Re:Never edit a method, always rewrite it? by jtlisi on Monday December 04, 2017 @06:57AM (#15843237)

Dave Cheney is well known in the go community, and works at Heptio. I don't think dynamic typing has much to do with this article.

[ Parent | on HN ]

Re:Never edit a method, always rewrite it? by GreaterFool on Monday December 04, 2017 @07:30AM (#15843351)

The author says Chad Fowler proposed this idea at RubyConf

[ Parent | on HN ]

Re:Never edit a method, always rewrite it? by mcphage on Monday December 04, 2017 @08:42AM (#15843688)

Yes, but the author of this article, which is discussing the idea, was written by Dave Cheney.

[ Parent | on HN ]

Re:Never edit a method, always rewrite it? by alexland on Monday December 04, 2017 @02:37PM (#15846747)

Don't confuse static/dynamic typing and weak/strong typing. A language can be both dynamically and strongly typed (Python, for example). The thing you like about a "strongly typed language" is the static typing, meaning a variable's type can't change once it's been created.

[ Parent | on HN ]