Hacker Newsnew | past | comments | ask | show | jobs | submit | steipete's commentslogin

Marketing for what? I didn't even link to what I'm building because I wanna ship it when it's ready.


(OP) You know if I link to a half-finished project, people would take it apart as many don't understand the nuance between crap and simply not done yet. But if you follow me on twitter it'll take you a few minutes to figure out. I'm two months in, even with AI, shipping good stuff takes time.


Having scrolled through several pages of your complaining about idiots on HN or discussing a yet another AI tool, I guess this is it: https://sweetistics.com/ ? Something you couldn't link in the article for some reason?

I've scrolled bit more. I think in the past 50-100 tweets you only wrote thee talking about this, one of them proudly showing a mistake (invalid tweets containing the same text): https://x.com/steipete/status/1978229441802162548

So, I have to follow you on twitter and sift through garbage indistinguishable from all such "look how great is codex" and "this is my shamanic ritual that works I promise" to maybe see something you work on.

No thank you. I will make my judgement from the long-form article you posted.

And, as I said: depending on actual functionality, after burning $1000 a month on tokens you may actually have a fully functioning app in React + Typescript with little human supervision. I might do the same for anything Twitter-related because I couldn't be arsed to work with Twitter or Twitter APIs.


(OP) 1/3rd of the code is tests.

There's an Expo app, two Tauri apps, a cli, a chrome extension. The admin part to help debug and test features is EXTREMELY detailed and around 40k LOC alone.

To give some perspective to that number.


Yeah, I read the post. Telling me that there's a chrome extension and some apps tells me nothing. Saying that the code is 1/3 tests is...something, but it's not exceptional, by any means.

I've got an code base I've been writing from scratch with LLMs, its of equivalent LOC and testing ratio, and my experiences trusting the models couldn't be more different. They routinely emit hot garbage.


OP: If you give the llm examples like https://react.dev/learn/you-might-not-need-an-effect, it does a farily good job at refactoring useEffecs.

And yes refactoring sometimes re-introduces these, so it's not a perfect solution.


The irony here is that I did!

Having looked at the code a bit more, all I can say is that it's a lot of code to do little.

There's also a lot of naive error throwing going on.

And he seems to debug using logger stmts.

They're not scalable projects, you couldn't write enterprise software the way those projects are written. You would end up with such a volume of code.


(OP) the current projec is closed source. If you look at my cli tools, that's pure slop, all I care is that it works, so reviewing that code for sure will show some weird stuff. Does it matter? It's a tool to fetch logs form a server. I run it locally. As long as is does that reliably, idk about the code.


What does your current project do? Do you make money with it?


tbh in the time where everyone uses AI to write articles, some typos and mistakes like that are helpful to show that it's human made.


(OP) I use atlas for database migrations, it works quite well with agents and has plenty guardrails around it.


Been using that for a while, first Chinese model that works REALLY well!

Also fascinating how they solved the issue that Claude expects a 200+k token model while GLM 4.5 has 128k.


For that workflow, you might be happier with https://vibetunnel.sh.


Bind to localhost (default) and share securely via Tailscale.


I either have to trust that's all it's doing or read a bunch of code to verify it:

https://github.com/amantus-ai/vibetunnel/tree/main/VibeTunne...

And this is a solved problem. It doesn't need a new vibe aware implementation.

But thanks for downvoting and flagging my comment. That really improves public perception.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: