Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
odite509073dNever understood this. Surely you know what you're making, right?
Ranchu448973dAh yes, my variables are mostly retarded jumbles of letters until IntelliJ is done with my crap and renames them.
vintprox83573dExplaining something when I lose convincing note, I guess.
iamai111473dComments, they are easy to forget in the afterthought.
Code testing, at times, there are just too many scenarios that it's difficult the capture them all.
M1sf3t465173das far as what should be simple tasks go? Structure trumps naming any day of the week.
Do I want to make this all one component or do I want to break it down more. Should it have a direct route or just toggled from another. Do i need slots or can I get away with just passing props. Or maybe just context. Or should I put it in a store so that changes to it's state will remain if they move to another part of the app. May not be necessary now but what about in the future? The debate is never ending.
rutee071150673dGiving a shit.