News for hackers. Stuff that matters.

A comment on Please, kill your darlings. Parent comment

Re:Please, kill your darlings by bradlenox on Tuesday March 08, 2016 @11:27AM (#11246251)
I agree. Someone's "darling" code might be a truly innovative or unique way of solving a problem, and providing enough commentary should help avoid the problems the author warns about.
[ Parent | on HN ]
Re:Please, kill your darlings by mhurron on Tuesday March 08, 2016 @11:32AM (#11246291)
It's amazing, their whole complaint is solved by proper software development practices - Comment your code.
[ Parent | on HN ]
Re:Please, kill your darlings by prodigal_erik on Tuesday March 08, 2016 @12:52PM (#11247007)
Code that's clear enough not to need a comment is better than code that has a comment. Comments can be outdated or mistaken and they consume screen real estate.
[ Parent | on HN ]
Re:Please, kill your darlings by mhurron on Tuesday March 08, 2016 @01:09PM (#11247145)
You still need to document intent. No code is self documenting.
[ Parent | on HN ]
Re:Please, kill your darlings by dllthomas on Wednesday March 09, 2016 @11:32AM (#11253892)
In some cases, naming may be sufficient to communicate intent.
[ Parent | on HN ]
Re:Please, kill your darlings by CaptSpify on Tuesday March 08, 2016 @11:36AM (#11246318)
To be fair: What is proper practice, is far from what is common practice
[ Parent | on HN ]
Re:Please, kill your darlings by TTPrograms on Tuesday March 08, 2016 @11:35AM (#11246310)
Not to mention it may be a performance optimization.
[ Parent | on HN ]
Re:Please, kill your darlings by sgt101 on Tuesday March 08, 2016 @11:55AM (#11246505)
Which is a good reason, if that optimization is needed.
[ Parent | on HN ]