lysdexic@programming.dev to Programming@programming.dev • 8 months agoPush Ifs Up And Fors Downexternal-linkmessage-square9 fedilinkarrow-up127
arrow-up127external-linkPush Ifs Up And Fors Downlysdexic@programming.dev to Programming@programming.dev • 8 months agomessage-square9 Commentsfedilink
minus-squarelysdexic@programming.devhexagonhexbear2·8 months ago My advice: use descriptive variable names. The article is really not about naming conventions. linkfedilink
minus-squareonlinepersona@programming.devhexbear7·8 months agoDoesn't matter, it's hard to read an article. If it were hard to read for another reason like bad grammar, I'd comment on that too 🤷 linkfedilink
minus-squareSheldan@programming.devhexbear7·8 months agoShould have still used them. It was harder to read this way. linkfedilink
minus-squarelysdexic@programming.devhexagonhexbear2·8 months ago Should have still used them. It was harder to read this way. The blog author is literally using de-facto standard for placeholder names. https://en.wikipedia.org/wiki/Foobar https://www.techopedia.com/definition/27996/frobnicate The var names used by the author are perfectly fine. They don't cause any issue, nor do they make things hard to read. linkfedilink
minus-squarelad@programming.devhexbear1·8 months agoI even thought that this (hardness) was intended to emphasize the way it's hard to spot problems in real codebase 😅 linkfedilink
The article is really not about naming conventions.
Doesn't matter, it's hard to read an article. If it were hard to read for another reason like bad grammar, I'd comment on that too 🤷
Should have still used them. It was harder to read this way.
The blog author is literally using de-facto standard for placeholder names.
The var names used by the author are perfectly fine. They don't cause any issue, nor do they make things hard to read.
I even thought that this (hardness) was intended to emphasize the way it's hard to spot problems in real codebase 😅