pull down to refresh
77 sats \ 14 replies \ @ek 30 Mar \ parent \ on: Stacker Saloon
Start with understanding the problem the ticket is describing
Understanding is one thing fixing it is whole other skill set I am still developing. Like I have no clue where this issue exists in the code base. Plus it’s marked as a ui/UX bug but how do I know it’s not a back end issue?
reply
reply
Now I understand the bug the sat counter per zap is missing. It should be before replies but it’s missing on this comment for some odd reason
reply
reply
yep i noticed pinned comments don't show the amount of zaps, and doesn't even let me zap by clicking the lightning bolt as usual. This should probably be changed.
And @BlokchainB, my suggestion for where to start in the code is to look for the logic of pinned comments (search
pinned or pin in Github)... that's where I would start, anyway.reply
Oh @BlokchainB, one tip from one journeyman dev to another! Probably 95% of the time "coding" is not writing code but reading it.
Read the code and follow the logic to understand what's going on. AI tools like ChatGPT can really help here! Copy and paste the code in and ask it to explain to you. Sometimes it gets stuff wrong though, so you gotta keep a critical thinking cap on. But it does a pretty good job most of the time and speeds up your understanding by a lot.
Sometimes to fix a bug it's 99% reading code then changing one line to fix the bug haha
Ahh okay
reply
😆😆😆😆
reply