logoalt Hacker News

dofmlast Sunday at 2:34 PM3 repliesview on HN

If you characterise questions as bad faith so you don’t have to answer, sure.

Since this is my thread, and since I am an exasperated freelancer who has made most of his post-dot-com career from writing exactly the kind of quite small, simple, unambitious, often internal things for smaller customers that nobody would confuse with anything cool, who is trying to understand how AI is going to make his life any better when it’s so opaque, fast moving, poorly documented and full of unverifiable claims battling unverifiable claims, let me assure you that the following question is not being asked in bad faith:

What did you ship?


Replies

stavroslast Sunday at 2:57 PM

I've shipped small, simple, unambitious internal things for our company that saved people lots of time, and I've shipped them in minutes rather than the a day or two they used to take.

I've just shipped a migration from our old auth service to the new one in a week, a migration that we've put off for three years because it would take the team months to finish.

I've shipped small side-projects that I'm the primary (and usually only) user of, but they now take me two days rather than weeks of effort and learning (e.g. https://www.writelucid.cc, https://pine.town, https://stavrobot.stavros.io, https://github.com/skorokithakis/dracula).

I've made changes in OSS apps that I just wouldn't have made otherwise (https://github.com/futo-org/android-keyboard/pulls/skorokith...), and even some closed-source ones (https://www.stavros.io/posts/adding-a-feature-to-a-closed-so...).

I've shipped hardware projects that would have taken me months of learning in a few days (https://www.stavros.io/posts/i-made-a-voice-note-taker/).

How's that?

show 3 replies
galangalalgollast Sunday at 3:14 PM

I don't use it to ship whole products. I have it do some tasks.

I have it code dsp techniques in journal articles I hand it. I have it create the unit tests, pipelines documentation. Then I manually verify the test cases aren't wrong and run the tests. If they pass it does what I wanted and I start looking at the code quality. It varies from being better than I could have done it to being objectively bad. I fix it if it needs fixing, then I'm done.

I have also pointed it at issues in our backlog and it usually finds the subtle logic errors underlying the behavior in the issue.

I haven't started and entire product from zero and shipped it. Mostly because I haven't started a new product since it was capable of that. But also because it has a scale beyond which I don't find it as useful. I have used it for an entire repo, but in the crates.io or npm scale of repo, not boost scale.

ncphillipsyesterday at 10:41 AM

I work at a 6 year old startup. Essentially every feature and bug fix we’ve shipped in the last year has had LLMs involved. Every project plan involved AI, either for writing or for codebase research. For code review we get AI to do the first pass.