
Dict Comprehensions vs Array Functions: The Ultimate Battle #codingtips
YouTube
Indentation vs Braces: THE HOLY WAR of Programming! #holywar
YouTube
Array Slicing: Pythons ::-1 vs PHP Functions! #PHP
YouTube
in Operator: Pythons ONE vs PHPs MANY Functions! #membershiptest
YouTube
Modern Enums Battle: Python 3.10 vs PHP 8.1! #modernfeatures
YouTube
Lambda vs Arrow Functions: Almost Identical! #functionalprogramming
YouTube
Multiple Return Values: Tuple Unpacking vs Array Destructuring #programmingdebate
YouTube
Array Methods vs Array Functions: The Functional Showdown #viralcoding
YouTube
Match Statement vs Match Expression: Pattern Matching War #codecomparison
YouTube🎉 Ah, the age-old debate resurrected! Why explain *what* the code does when you could just write clearer code to begin with? 🤔 But hey, let's reignite the flames with this groundbreaking revelation: maybe, just maybe,
#comments should state the obvious too. 🔥 Because we all need more
#verbose hand-holding, right? 🙄
https://www.hillelwayne.com/post/what-comments/ #codeclarity #programmingdebate #codingbestpractices #HackerNews #ngatedMaybe Comments SHOULD Explain 'What'
People say “Comments should explain why, not what.” I feel like starting a flame war today so I’m going to argue that comments should explain ‘what’ too. Please don’t use this as justification to write bad code, okay? Okay.
First of all, why shouldn’t comments explain ‘what’? If you need comments to explain what’s going on, it suggests your code is unclear. If I write
//weight, radius, price w = 10, r = 9, p = 1 That’s not as clear as saying
Hillel Wayne