PokeVideoPlayer v23.9-app.js-020924_
0143ab93_videojs8_1563605_YT_2d24ba15 licensed under gpl3-or-later
ImmersiveAmbientModecolor: #bf9688 (color 2)
Video Format : (720p) openh264 ( https://github.com/cisco/openh264) mp4a.40.2 | 44100Hz
Audio Format: 140 ( High )
PokeEncryptID: d2b74ab5384588111b30dc2d2419ff0c520be7e554025e7385576490cbf7ae4744b964e59e929eb4aa74edfe36129fa1
Proxy : eu-proxy.poketube.fun - refresh the page to change the proxy location
Date : 1732505624121 - unknown on Apple WebKit
Mystery text : ZXg1ZUduVTFaRVkgaSAgbG92ICB1IGV1LXByb3h5LnBva2V0dWJlLmZ1bg==
143 : true
990,124 Views • Nov 20, 2024 • Click to toggle off description
piratesoftware.live/
Join the community here:
discord.gg/piratesoftware
#Shorts #Twitch #PirateSoftware
Views : 990,124
Genre: Entertainment
License: Standard YouTube License
Uploaded At Nov 20, 2024 ^^
warning: returnyoutubedislikes may not be accurate, this is just an estiment ehe :3
Rating : 4.981 (359/76,369 LTDR)
99.53% of the users lieked the video!!
0.47% of the users dislieked the video!!
User score: 99.30- Masterpiece Video
RYD date created : 2024-11-25T03:31:44.82549Z
See in json
940 Comments
Top Comments of this video!! :3
Breaking news: programmer writes unreadable code; Refuses to comment.
11K |
“# TODO: Fix this”
2.7K |
I've definitely seen a third type: the exhausted exasperated coder comment. "Do not change this. It works. No-one knows why, but if you change it nothing works any more. DO NOT TOUCH."
3.8K |
Saw the title and thought he was talking about YouTube comments
1.4K |
There're 2 types of comments:
2. The bad ones
1. The good ones
0. The nonexistant ones.
518 |
I was always told by my professors in college "comment your code like you know the next engineer to look at it is a serial killer and knows where you live" 😂
1K |
There is another.
// DO NOT TOUCH
101 |
“This sets unbreaking to 1”
“This tree is an aspen. We know that it’s an aspen because of the way it is”
30 |
WHY is always good, but WHAT has its place; I can appreciate WHAT comments that mark the borders between components.
339 |
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.
569 |
it's like the settings in the BIOS
>enable TPM
>click on it to get explanation
>this setting enables or disables TPM
OH WOW THANK YOU THIS TOTALLY EXPLAINS IT
39 |
Context is in great demand but poor supply
54 |
I can read code just fine, but I can’t read my coworkers minds.
17 |
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.
21 |
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!”
55 |
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.
187 |
This should be taught in all beginner programming classes and courses.
Comments aren't for translating individual lines or sections of code. They're for providing context.
1 |
"We don't know why this works. A priest has been called."
5 |
"This was part of a failed feature, but removing or otherwise altering it in any way shatters the entire program. I don't know why. I've tried fixing it, but the only solution was to leave this as if it was still interacting with the scrapped feature."
8 |
@CheeseTako
4 days ago
"I don't remember what this does, but deleting it breaks everything"
8K |