Live data from Hacker News

Show HN: Pyscn – Python code quality analyzer for vibe coders

github.com

41–50 of 87 posts

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#41
post #5

This is an interesting idea but you might be better off marketing it as a tool for software engineers, maybe to help with old code bases. Or even for someone stuck cleaning up vibe coded nonsense. Vibe coders don't care about quality and wouldn't understand why any of these things are a problem in the first place.

Vibe coders do care about quality, at least the ones that try to ship and get burned by a mountain of tech debt. People aren't as stupid and one dimensional as you assume.

And where, exactly, did this commenter say that vibe coders are "stupid and one dimensional"? Stop putting words in people's mouths.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#42
post #23

Earlier quoted context omitted.

Yes! tree-sitter supports multiple languages and the core algorithms should transfer easily. I focused on Python first because I saw many people struggling with code quality issues in Python.

Just based on usage, I would assume js/ts would be very valuable as well. I see a lot of the same issues there and agree the core algos seem to apply generally. Very cool project!

Agreed, I do python and ts depending on the use case, a ts version would be cool

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#43
post #24

Earlier quoted context omitted.

Vibe coders do care about quality, at least the ones that try to ship and get burned by a mountain of tech debt. People aren't as stupid and one dimensional as you assume.

Given an entire industry is cropping up to fix the mess these people make, I think less of them care then you think.

Is it an industry, or just a meme job title? Serious question.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#44

Earlier quoted context omitted.

Vibe coders do care about quality, at least the ones that try to ship and get burned by a mountain of tech debt. People aren't as stupid and one dimensional as you assume.

And where, exactly, did this commenter say that vibe coders are "stupid and one dimensional"? Stop putting words in people's mouths.

>> Vibe coders don't care about quality and wouldn't understand why any of these things are a problem in the first place.

He literally bucketed an entire group of people by a weak label and made strong claims about competence and conscientiousness.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#46

What about Pylint? iirc pylint has code duplication check as well. is it the same thing?

Pylint's duplication check is text-based (compares lines), while pyscn uses tree edit distance on ASTs. This means pyscn can catch structural clones even when variable/function names differ.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#47
post #26

this should be a MCP server the agent can use and optimize on I have a MCP server that wraps developer tool CLIs (linting, tests, etc), but this would need a textual report instead of HTML. https://github.com/scosman/hooks_mcp

MCP integration could be a good option. If there's interest, feel free to raise an issue on GitHub.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#48
post #5

This is an interesting idea but you might be better off marketing it as a tool for software engineers, maybe to help with old code bases. Or even for someone stuck cleaning up vibe coded nonsense. Vibe coders don't care about quality and wouldn't understand why any of these things are a problem in the first place.

This kind of weird disdain towards "vibe coders" is hilarious to me.

There was a time when hand soldered boards were not only seen as superior to automated soldering, but machine soldered boards were looked down on. People went gaga over a good hand soldered board and the craft.

People that are using AI to assist them to code today, the "vibe coders", I think would also appreciate tooling that assists in maintaining code quality across their project.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#49

Earlier quoted context omitted.

And where, exactly, did this commenter say that vibe coders are "stupid and one dimensional"? Stop putting words in people's mouths.

>> Vibe coders don't care about quality and wouldn't understand why any of these things are a problem in the first place. He literally bucketed an entire group of people by a weak label and made strong claims about competence and conscientiousness.

That comment sounds pretty benign to me. I also don't know why you're assuming the original commenter is male. The only person in the wrong here is you, and you're wrong twice over.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#50
post #5

This is an interesting idea but you might be better off marketing it as a tool for software engineers, maybe to help with old code bases. Or even for someone stuck cleaning up vibe coded nonsense. Vibe coders don't care about quality and wouldn't understand why any of these things are a problem in the first place.

This kind of weird disdain towards "vibe coders" is hilarious to me. There was a time when hand soldered boards were not only seen as superior to automated soldering, but machine soldered boards were looked down on. People went gaga over a good hand soldered board and the craft. People that are using AI to assist them to code today, the "vibe coders", I think would also appreciate tooling that assists in maintaining…

Whether the board is hand solder or not, the person designing it still has to know what they're doing.

I think a comparison that fits better is probably PCB/circuit design software. Back in the day engineering firms had rooms full of people drafting and doing calculations by hand. Today a single engineer can do more in an hour then 50 engineers in a day could back then.

The critical difference is, you still have to know what you are doing. The tool helps, but you still have to have foundational understanding to take advantage of it.

If someone wants to use AI to learn and improve, that's fine. If they want to use it to improve their workflow or speed them up that's fine too. But those aren't "vibe coders".

People who just want the AI to shit something out they can use with absolutely no concern for how or why it works aren't going to be a group who care to use a tool like this. It goes against the whole idea.

Post reply on HN