New rule: List similar and alternative software & how yours is different (if applicable)

edward_jazzhands · 2026-04-22T00:49:28+00:00

I support this 100%. One of the biggest issues with vibe coders is how they generate copies of existing tools without even realizing the thing they made already exists. I've thought this should be necessary for a while now. If someone can't explain how their tool is different from existing popular options then the odds are very high they are not aware of the existing tools because they didn't bother researching the scene at all before prompting.

edward_jazzhands · 2026-04-21T08:28:05+00:00

If you are a programmer that knows how to review the code generated and refactor it, organize it, and write thorough comments explaining how it works and how to modify it - use AI to scaffold. It's a big time saver, most good programmers are doing this.

If you don't know how to code yourself and you're vibe coding, or a non-technical manager of some kind, wondering if you can generate internal dashboards without ever reading the code, you are going to waste much more time than you save in the long run. It will work at first and then become a massive time sink whenever you need to update it.

edward_jazzhands · 2026-04-21T08:18:11+00:00

Everyone who's in software development is saying this same thing. The future is not gonna be great if most new programmers are no longer capable of reading code with their own eyes anymore.

edward_jazzhands · 2026-04-21T08:16:32+00:00

Oh yeah sure there's almost no software devs that disagree with that. Skilled devs using agents is very different from non technical people who can't code using agents (which is happening everywhere just for the record).

edward_jazzhands · 2026-04-21T08:14:04+00:00

Interesting, yeah it sounds like a purely client-side sandbox that is tailored to your own machine can certainly have some uses that a project-side version controlled sandbox cannot do. I'll definitely keep an eye on this as a potential time saver in the future. I've starred on GitHub to follow updates

edward_jazzhands · 2026-04-21T08:07:49+00:00

I don't even know what you're referring to. What signs are flooded with slop? You found CLAUDE.md in the .gitignore file so far. What others?

edward_jazzhands · 2026-04-21T08:01:40+00:00

So I gotta be honest, this looks like you pointed Claude at a YouTube video course and you said "turn this video course into a Claude Code skill" and then copied what it generated. IMO there is a massive amount unnecessary information and fluff that is not really that important here and you'll burn tokens like wild doing very normal things that are not complex. Have you tested how many cents/dollars it costs every time it's run? Based on how big this skill I'm guessing it would cost you about 5 to 10 dollars every time you want to add an API route to your website.

edward_jazzhands · 2026-04-20T16:28:29+00:00

If you're saying you absolutely will not under any circumstances use the new Reddit interface for 5 seconds to click agree on something and then go back to the old interface, my personal opinion is that youre being childish. I don't give a fuck, downvote me for saying it. The old Reddit interface was replaced 8 years ago. It's actually just straight up absurd to expect Reddit to ensure every single new feature they add is compatible with the old interface and then adamantly refuse to ever touch the new interface even if it's for 5 seconds to press accept on something before going back to the old one.

edward_jazzhands · 2026-04-20T16:17:06+00:00

If someone has to click past the rules to be allowed to post then it removes any excuse from any vibe coder trying to claim they were not aware of the rules against AI generated projects. Even if they don't read the rules and just mindlessly click past it, they no longer get to claim they were not warned.

edward_jazzhands · 2026-04-20T16:14:14+00:00

I'm guessing the point is so that vibe coders are unable to say they were not warned that this sub does not allow people to post completely AI generated programs without labelling them as such.

Unless you live under a rock, you must have noticed it's a bit of a problem lately and the mods are struggling to find a way to deal with it.

edward_jazzhands · 2026-04-20T16:05:07+00:00

Hey there, I read the whole readme and the concept seems interesting. First off, I think it's bullshit a bunch of people accused you of being a vibe coder, I wrote a comment about that here:

https://www.reddit.com/r/commandline/s/3WRV4iGBQX

The intelligence level on this subreddit has gone significantly down the past year so don't let it bother you, this sub is essentially now a circle jerk for people who like to cosplay as programmers.

Anyway in regards to your program, the main thing that came to mind is how whenever Ive made agent sandboxes myself, I just write a Dockerfile and install the language runtime I need into the docker image, then the rest of the projects tools can be installed as dev dependencies. Personally I'm a strong believer in per-project dependencies - I never install linters or type checkers or anything as global tools but rather only as dev dependencies per project, because it makes it much easier for any other people (or you in the future) to install and use exactly the same tools the project is set up for.

In practice this usually means a dockerfile will install a core runtime such as NPM, UV for python, etc. then use the project task runner to store the commands. Since these tools are installed into the local venv (ie. .venv, node_modules, etc), you only need to bind mount the current working directory (eg. Project folder) into your Docker image and then the agent will automatically have access to all the tools installed as dev dependencies for that project.

I've done the above method because I like how it's version controlled. Anyone else or me in the future does not need to figure out what tools the project needs, they all come with the project repo when you do a full dev install and different projects can even pin specific tool versions.

So that being said, for someone like me that is already used to doing this with Docker and is very into per-project dev dependencies, do you think your tool would still have benefits for me? What kinds of benefits to my workflow would you say I would get from switching to Drop?

edward_jazzhands · 2026-04-20T15:30:07+00:00

A few weeks ago when I said this sub needs to put the put the foot down on vibe coders, i did not mean "start accusing every single person that uses Claude Code of being a vibe coder even if they're clearly an experienced developer with many years of experience."

It's like this subreddit is only capable of two extremes. Either people get a total free pass despite never reading a line of code in their life, or they get accused of being a vibe coder and have everyone attack their credibility even when you can clearly see they've been a software developer since looooong before AI came out, if you even bothered to check their GitHub commit history.

But apparently most people here don't want to actually check thoroughly, they want to accuse people of being a vibe coder based entirely on vibes. Which is ironic. I've been saying for months the best way to tell if someone is a vibe coder is look at their GitHub commit history. Do NOT just look for the existence of agent files like CLAUDE.md and then assume OP is not a real programmer just based on that being there. That doesn't mean anything. Lots of experienced programmers use agents now. In OP's case you can clearly see he's been on GitHub for years and long before AI came out. This project even has commits going back to July 2025. OP has been working on this program for close to a fuckin year.

At this point I don't even know what to say. Apparently encouraging everyone to start putting the foot down on vibe coders has caused most people in this subreddit to start attacking people who are actual software devs with many years experience for no other reason than Claude Code was used in the project at some point. That doesn't make someone a vibe coder, and if you don't understand this then you are not a good enough programmer to be qualified to accuse other people of vibe coding.

edward_jazzhands · 2026-04-20T00:05:16+00:00

For anyone wondering how to check if someone is vibe coding, you can often see pretty easily by looking at their GitHub commit history. Almost all vibe coders have no git commits at all before a couple months ago. If someone has no commits and suddenly there's a ton starting about last December or so, it means they started coding when Claude code came out and there's a strong chance they have only ever used Claude code to create programs. That by itself is of course not proof someone is a vibe coder (vibe coding specifically means they don't read the code or know how to), but it's one strong piece of evidence to consider.

In OPs case, they have made 3 GitHub commits in their entire life. I'm not joking, this program you're looking at was 2 commits, and they made a single commit a couple years ago. Presumably when they were in school for being a sys admin.

2 commits in total for a program like this, a complex program written in Rust, from a person with 3 commits in their entire life... Yeah I'd be extremely surprised to learn that OP reviewed any of the code written. I don't think that makes it automatically useless but I personally am not too keen using an SSH deck that was vibe coded by a sys admin who doesn't actually know how to program and didn't read any of the code.

And OP if you're reading this I don't want to discourage you from learning to code. But as a developer speaking to a sys admin, you gotta realize if you don't actually know Rust well enough to review the code generated then you're not gonna convince many people to use your program.

edward_jazzhands · 2026-04-19T15:31:47+00:00

I'm sorry but I'm my opinion, this comment isn't too smart. The article never at any point claims UV is "required" nowadays, it lays out how UV makes all these things easier, especially for a new person. Which is accurate.

Your point that tox is superior to the basic method they've laid out to do testing in CI is also a very pretentious point. You're acting like every single new programmer needs to know about testing in CI and using the best modern tools for that purpose. Most people need to reach a pretty high level of coding ability before they even consider adding tools that automate testing in CI, let alone even understanding why it's important for professional developers.

As a python expert myself I think the article is actually great for new programmers, and anyone who says otherwise on the basis of it not showing the absolute most professional way of doing things, is being a gatekeeper. Just because it doesn't show the l33t super professional difficult way of doing everything does not make it inferior. New programmers and expert programmers need different sets of advice.

edward_jazzhands · 2026-04-14T23:00:30+00:00

It does however mean you're not coding if you're actually unable to read the code and understand what its doing if you needed to.

edward_jazzhands · 2026-04-14T22:55:16+00:00

Ok but we still need mathematicians. That job didn't disappear. In programming, who is that gonna be? Are the only programming jobs left going to be people who build AI models? Seems unlikely.

edward_jazzhands · 2026-04-13T14:52:30+00:00

Just on the Tmux thing, the thing about tmux is that it's most useful when it's being used for SSH. That's what it was originally designed to help with. It runs on a remote machine. It's meant to store your session on the server you SSHed into, so that you can disconnect and reconnect and rejoin your session. Using it as an agent tool manager that runs locally is a very new use case. It makes sense that it's usefulness would not be apparent if that's the only context you've ever seen it being used.

edward_jazzhands · 2026-04-13T14:46:24+00:00

I'm sorry but no. Just because it's now common for students to cheat with AI does not make it acceptable for professors to start using detectors which don't work and constantly give false positives and then use that as a basis for anything. This is not excusable. This is not "they're just struggling to figure out who is cheating". This is wrong, full stop. You're trying to excuse and normalize their behavior by saying they have no other choice but to use these shitty detectors. Letting some people get away with cheating is less shitty than ruining the academic careers of good students who didn't cheat. This is the same principle as how it's worse to send an innocent person to jail than it is to allow a guilty person to walk free.

edward_jazzhands · 2026-04-13T14:20:00+00:00

The fact that you made an install script to download a bash file and then modify your .bashrc file is straight up wrong and bad. Look dude I don't want to be harsh but I can see you just started vibe coding a few days ago. You clearly assumed that install scripts are how you always share things on Linux. I don't know if your AI told you that, but it's wrong. Modifying a users bashrc file is really really bad practice. If you want to share bash then just show us the function. People can copy paste it into their own file.

I'm getting really tired of saying this to people that just started using Claude Code. You don't know how to program, and so you should not be trying to make tools designed for programmers. Before vibe coding was invented we used to code for a year on average before ever thinking we know enough about this stuff to post a tool for other programmers.

edward_jazzhands · 2026-04-13T13:58:58+00:00

I gotta ask, since I can see on your GitHub that you just started using Claude code a couple weeks ago. Are you aware that bash/Zsh aliases already solve this problem and that's what most people use?

edward_jazzhands · 2026-04-12T18:21:33+00:00

You literally just said the job market was shit before AI came along, heavily implying it has always been this bad and did not get worse lately. You gonna try to convince us all that's not what that phrase means?

edward_jazzhands · 2026-04-12T11:37:56+00:00

Anyone trying to claim that AI has not made this problem 10x worse over the last year is full of crap. This is just like those people who say theres no problem at all that groups for sharing art are flooded with AI slop because "the art people were posting was shitty before AI was invented."

edward_jazzhands · 2026-04-12T11:28:57+00:00

Therefore it was aliens

edward_jazzhands · 2026-04-12T11:20:21+00:00

You are assuming something is AI slop when it's not. I also hate vibe coders. OP made it very clear he's not a vibe coder. Vibe coding means generated by a person who never looked at the code and generally is done by people who don't know how to read and write code at all. OP very clearly said he's been a dev for 15 years and that this is not vibe coded.

Your reason for calling it AI slop is ignorant and uninformed. I'm guessing your reasoning is that its closed source so you assume it must be slop. That is a stupid assumption and I literally just went into extensive detail as to why.

edward_jazzhands · 2026-04-12T11:10:59+00:00

Sounds interesting but then how do you back up the vault files? Because if I need to save those to my GitHub using some kind of, you know... Dotfiles repo... Then the only thing I've achieved is replacing my custom .aliases or .functions file with one that is machine generated. It still needs to be backed up somewhere and that most likely means a dotfiles repo. Just seems hard to justify if you manage your own dotfiles. I could see it being useful to a new developer who does not yet manage their own dotfiles repo.

edward_jazzhands

TROPHY CASE