☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 2 days agoVSCode-style TUI written in Rustcodeberg.orgexternal-linkmessage-square11linkfedilinkarrow-up154arrow-down111
arrow-up143arrow-down1external-linkVSCode-style TUI written in Rustcodeberg.org☆ Yσɠƚԋσʂ ☆@lemmy.ml to Open Source@lemmy.mlEnglish · 2 days agomessage-square11linkfedilink
minus-squareSlimePirate@lemmy.dbzer0.comlinkfedilinkarrow-up3·14 hours agoThe readme is gigantic with weird info like keybinds and project layout, especially the bizarre “what works” status section and the mention of number of unit tests.
minus-squareHolla@feddit.orglinkfedilinkarrow-up7·1 day agoThey’re writing whole paragraphs in their commit messages. What dev would even write that much documentation at all? And then into the git message? https://codeberg.org/vitali87/croft/commits/branch/main?page=2
minus-squareTruePe4rl@lemmy.mllinkfedilinkEnglisharrow-up5·23 hours agoThe fact that there is this section in the README even though all the code has docstrings and you can generate the docs is certainly interesting.
minus-squareyuman@programming.devlinkfedilinkarrow-up5arrow-down3·1 day agoif it ain’t stated front and center that this project wasn’t vibeshat, you can safely assume it is.
how do you tell?
The readme is gigantic with weird info like keybinds and project layout, especially the bizarre “what works” status section and the mention of number of unit tests.
They’re writing whole paragraphs in their commit messages. What dev would even write that much documentation at all? And then into the git message? https://codeberg.org/vitali87/croft/commits/branch/main?page=2
The fact that there is this section in the README even though all the code has docstrings and you can generate the docs is certainly interesting.
if it ain’t stated front and center that this project wasn’t vibeshat, you can safely assume it is.