pull down to refresh

272 sats \ 5 replies \ @SimpleStacker 31 Mar \ parent \ on: Stacker Saloon
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
write
preview
250 sats \ 4 replies \ @BlokchainB 31 Mar
Even getting here is hard. I looked at the repo and was overwhelmed lol like I have no idea where to begin to look for this bug. I saw all the branches (like ek’s lightning branch) and was lost. But thanks for the ChatGPT hint never thought to use it in that way
reply
103 sats \ 1 reply \ @ek 31 Mar
ek’s lightning branch
I don't know what you are talking about lol
We are just bad at deleting old branches. Most of them are probably stale. Github should tell you that though.
reply
30 sats \ 0 replies \ @BlokchainB 31 Mar
Hahaha I’ll show you
reply
131 sats \ 1 reply \ @SimpleStacker 31 Mar
You probably don't need to pay attention to any of the branches. Just focus on understanding master.
It is hard, but worth it! ChatGPT can help a lot. Another hint is to tell ChatGPT that it uses next.js framework. A lot of it is standard coding patterns for that framework so once you get the hang of it, it becomes a lot easier to understand everything.
reply
30 sats \ 0 replies \ @BlokchainB 31 Mar
Okay chatGPT I’m using next.js
reply