PokeVideoPlayer v23.9-app.js-020924_
0143ab93_videojs8_1563605 licensed under gpl3-or-later
Views : 515,013
Genre: Entertainment
Uploaded At Nov 20, 2024 ^^
warning: returnyoutubedislikes may not be accurate, this is just an estiment ehe :3
Rating : 4.986 (154/44,142 LTDR)
99.65% of the users lieked the video!!
0.35% of the users dislieked the video!!
User score: 99.48- Masterpiece Video
RYD date created : 2024-11-22T23:22:19.748413Z
See in json
Top Comments of this video!! :3
In my work, I like to think of it like this: any comments or details left must be able to clearly explain a given thing to someone who knows little about what they're looking at.
I do this with my emails, my invoices, and my client interactions... usually helps to prevent a lot of questions or mess-ups down the line.
470 |
I appreciate the drive in recent years to write code that uses thoughtful naming that strives to be self documenting. I certainly don’t miss variables in longish methods named “x”.
But I do think we should write more of these sorts of comments to explain what we were thinking when we wrote code.
154 |
I try to live by this quite a good bit. When I tell people at work about how I might do things or what different safety rules are I try to tell them WHY I/we do that/have it as a rule. Becuase most of the time people seem to be more receptive to things when they know the reason behind it, not just “hey (don’t) do that thing!”
37 |
I would augment this by noting that a lot of the reason people write those bad comments is to remind themselves of how the programming language works cause they’re juggling too much of the system in their brain. Plotting down some design context as part of your ‘why’ is often more helpful. In the video, I’d refer to enchant too, something as follows:
Unbreakable is an item enchant property that prevents this item from disappearing when used if set. 1 is the default value.
Then you can in theory extend and/or move this to code documentation later if you have to cause ya did enough of the work when it hurt your brain the most.
14 |
@slotharmstronk1348
2 days ago
Breaking news: programmer writes unreadable code; Refuses to comment.
6.3K |