lysdexic@programming.dev to Programming@programming.devEnglish · 1 year agoPush Ifs Up And Fors Downmatklad.github.ioexternal-linkmessage-square18fedilinkarrow-up138arrow-down15cross-posted to: rust@zorg.socialhackernews@lemmy.smeargle.fanshackernews@derp.foo
arrow-up133arrow-down1external-linkPush Ifs Up And Fors Downmatklad.github.iolysdexic@programming.dev to Programming@programming.devEnglish · 1 year agomessage-square18fedilinkcross-posted to: rust@zorg.socialhackernews@lemmy.smeargle.fanshackernews@derp.foo
minus-squarelysdexic@programming.devOPlinkfedilinkEnglisharrow-up0arrow-down2·1 year ago My advice: use descriptive variable names. The article is really not about naming conventions.
minus-squareSheldan@programming.devlinkfedilinkarrow-up2·1 year agoShould have still used them. It was harder to read this way.
minus-squarelysdexic@programming.devOPlinkfedilinkEnglisharrow-up1·1 year 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.
minus-squareonlinepersona@programming.devlinkfedilinkEnglisharrow-up0arrow-down2·1 year 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 🤷
The article is really not about naming conventions.
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.
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 🤷