At the risk of stating the obvious, I would like everyone to know that https://www.shellcheck.net/ exists. Unless you are a bash wizard: if your bash script doesn't pass shellcheck, it is very likely to have bugs.
- Posts
- 12
- Comments
- 1609
- Joined
- 2 yr. ago
- Posts
- 12
- Comments
- 1609
- Joined
- 2 yr. ago
Offroad @lemmy.ml It's not sexy but it is (was) mine
Inventing Reality @lemmy.ml Just Bezos Things
ThinkPad @lemmy.ml While we're sharing setups...
TrailViews @piefed.social Desert Sunrise
pics @lemmy.world Desert Sunrise
Photography @lemmy.ml Desert Sunrise
pics @lemmy.world Moonrise at sunset
Photography @lemmy.ml Moonrise at sunset
pics @lemmy.world Winter Dawn
Photography @lemmy.ml Winter Dawn
pics @lemmy.world Late spring in Georgia
Photography @lemmy.ml Late spring in Georgia
I'd like to add my perspective.
I'm not very anti-AI, I use a locally run model to help me write code (especially boring stuff).
For me it's mostly about "is it worth the time to package this thing in Nixpkgs, add it to my config, and get used to how it works?"
And for vibecoded projects, even if they work now, the answer is "probably not"; more specifically it's "let's look if it's alive in a year, if I'm still interested".
As such, I really appreciate when people add a disclaimer so that I don't have to go look at the code only to be disappointed - I also appreciated it back in the day when someone said "this is my first real project" or something, for similar reasons.
And secondly it's a question of trust. If the author doesn't disclose such basic things about the way the project has been developed, and in fact avoids answering when asked directly, what other potential problems could there be semi-hidden in the codebase?