HN user

ekzy

359 karma

Programmers know the benefits of everything and the tradeoffs of nothing

t dot h at sent dot com

Posts8
Comments142
View on HN
GPT-5.6 13 days ago

Just my two cents. I'm on the Plus plan, I ask gpt-5.6 sol / high to analyze a vibe-coded codebase (~50k LoC) and write a plan to make it production ready. It wasn't a great prompt, I just wanted to test it quickly. It ran for ~15min and consumed 95% of my 5h quota (I thought it was gonna crash). The output is excellent but just a heads up that it consumes a lot of quota!

Ok after re reading I think you have issues with long running spans, I think you should break down your spans in smaller chunks. But a trace can take many hours or days, and be analysed even when it’s not finished

I’ve implemented OTEL for background jobs, so async jobs that get picked up from the DB where I store the trace context in the DB and pass it along to multiple async jobs. For some jobs that fail and retry with a backoff strategy, they can take many hours and we can see the traces fine in grafana. Each job create its own span but they are all within the same trace.

Works well for us, I’m not sure I understand the issue you’re facing?

Oh I see what you mean that would be a neat feature. Assuming you can get timestamps though it should be trivial to work around the issue?

Do you know when we can expect an update on the realtime API? It’s still in beta and there are many issues (e.g voice randomly cutting off, VAD issues, especially with mulaw etc…) which makes it impossible to use in production, but there’s not much communication from OpenAI. It’s difficult to know what to bet on. Pushing for stt->llm->tts makes you wonder if we should carry on building with the realtime API.

Why Clojure? 1 year ago

Call it “stalled” if you like, it’s stable and it’s pure joy. I can just get stuff done with Clojure. And things that may seem inactive, like that lib that you need that hasn’t had a commit in 8 years, turns out that it just works and doesn’t need to change. This is commonplace in Clojure.

Spec is still alpha and I’m not sure it will evolve more or if it’ll be something completely different. At least they’re not pushing you down the wrong path. Use/look at Malli instead of spec.

Every V4 UUID 2 years ago

Nice. I’ve added a few favourites just to keep track of them, you never know!

It would be great if there was an API because I’m working on an UI that needs UUID autocomplete. Thank you!

Could you also pick up the audio announcements? Could be weird for the app to request microphone permission though, but I think lots of lines have them and should be doable to transcribe them locally on the phone. I think your approach is better and simpler, but as I was reading the edge cases (like someone changing train and going back in the other direction), the audio could maybe help getting from 90% accuracy to 98%. Sounds a bit more involved to implement though.

Honest question, what’s wrong with docker desktop? Looking at all the alternatives suggested it’s not clear to me why any other tools are better? I’m not using k8s locally, just docker compose. To connect to our remote k8s cluster, I use IntelliJ k8s extension (I just need to do some basic dev tasks, I’m not administrating the cluster)

Try Clojure 2 years ago

Then… don’t? No ones is forcing you to try it or even to comment with your close-minded opinion. What does this comment bring to the conversation?

Yes. A relevant quote from Alan Kay in his talk “the power of simplicity”:

one of the things that's worked the best the last three, or four hundred years, is you get simplicity by finding a slightly more sophisticated building block to build your theories out of. its when you go for a simple building block that anybody understand through common sense, that is when you start screwing yourself right and left, because it just might not be able to ramify through the degrees of freedom and scaling you have to go through, and it's this inability to fix the building blocks that is one of the largest problems that computing has today in large organizations. people just won't do it

https://youtu.be/NdSD07U5uBs

I made an app some years ago that let you order custom song books with chords (physical books), to play the guitar / sing along at campfires etc. I integrated the app with Spotify, a printing API, stripe, and ordered a few books for myself (basically you could import some Spotify playlists or just add some songs), compile it into a book and then place your order and get it delivered at home… all automated. I thought I could turn this into a nice SaaS, until I was told this is illegal as the lyrics and tabs/chords are protected by copyright. I couldn’t find more motivation after this major roadblock so I gave up. It’s still up and running, but only I have access to the printing feature. The name which I thought was clever was actually kinda confusing to people (lyrink.com as in lyrics + ink) and always autocorrected to “lyrics”. I worked on this printing feature for many months. There’s some really interesting programming challenges with trying to fit dynamic content from the internet, with chords and lyrics (where the chords have to be placed correctly near the lyrics) etc. into a nicely formatted physical book (without using a monospaced font)

agreed, and maybe ask to login to save logo or unlock more features, but I agree that you should let user play around a bit without needing to sign up!

In my experience, it isn't black or white. I've used tailwind along with components, e.g.

.button-primary { @apply rounded-full focus:ring focus:ring-orange-500 ring-offset-4 outline-none px-6 py-3 etc...

and it gives you the best of both worlds. You refactor common css code into components and still have the amazing flexibility of utility classes.