ysaie

31 / ⚧ / code, music, art, games

──────────────────────────────
🌸 many-shaped creature
✨ too many projects
🚀 cannot be stopped
🌙 stayed up too late
:eggbug: eggbug enjoyer
──────────────────────────────
header image: chapter 8 complete from celeste
avatar: made using this character builder


📩 email
contact@echowritescode.dev

joewintergreen
@joewintergreen

is how some unreal engineers never provide tooltips for variables and functions exposed to blueprint

do you know how easy it is to do? you literally comment it. that's it. the editor uses the comment as the tooltip

so many people never do this


ysaie
@ysaie

this, and also blueprint comments!! you can literally just write down what the code you wrote does!!


You must log in to comment.

in reply to @joewintergreen's post:

I wish more programmers thought of these comments as what they really are: intra-team communication. If there's no comment for a variable and it's name and context don't make it plainly obvious what it does (and any nuances around its use that you'd need to have seen the code to know about), then you are creating potentially dozens of future redundant slack conversations from different team members who hit the same missing stair and don't know wtf the thing does, and the lost flow that comes with that. Even for team members who are comfortable tracking down the variable and its usage in the C++ code to read and learn what it does, it's frequently a hassle to find that because native land is this opaque wall within the editor. Writing the description should be considered part of the work of writing the code itself, the code should not be considered done until then.