2
points
distalx
Joined 491 karma
- distalxFriendly reminder: There is no ghost in the machine. It is a system executing code, not a being having thoughts. Let’s admire the tool without projecting a personality onto it.
- What tools or process do you use to optimize your prompts?
- This looks great! I'm not a guitar enthusiast myself, but the design and color tone look very slick.
Congratulations on the launch after a year of work, and I wish you all the best with it!
Just out of curiosity, how much time did it take you to get app store approval from Apple and Google in 2025?
- It does feel like planned obsolescence when companies like Apple limit software support for older hardware, Ubuntu run smoothly on much older devices. They could certainly do better by extending support and focusing on sustainability.
- Exactly, token per dollar rates are useful, but without knowing the typical input output token distribution for each model on this specific task, the numbers alone don’t give a full picture of cost.
- I bought into that idea a month or two ago, that more control and detailed instructions would deliver a clean result. That just led me down a rabbit hole of endless prompt re-runs and optimization loops. Many time I thought I had the final, perfect prompt, the next iteration slightly worsened the output. And sometimes the output was the same.
The last 20-30% of precision is brutal. The time and tokens we burn trying to perfect a prompt is simply not an optimal use of engineering hours. The problem is simple: Companies prioritize profit over the optimal solution, and the initial sales pitch was about replacement then it changed now its all about speed. I'm not making a case against AI or LLMs; I'm saying the current workflow, a path of least resistance means we are inevitably progressing toward more technical debt and cleanup at our hands.
- Vibe Coding is accelerating the death of documentation and architectural clarity. Companies are measuring success by tokens generated and time-to-prototype, ignoring the massive, hidden cost of cleanup/maintenance.
The real skill is now cleanup, not generation.
- If you don't mind, could you share the link to your Reddit post? I'd love to read more about your findings.
- I feel like this post might be a bit clickbaity. It presents a strong statement without much context, analysis or evidence.
- Probably valid sunk cost fallacy, but it makes me wonder what will happen to the applications and systems being built on top of LLMs? If we face limitations or setbacks, will these innovations survive, or could we see a backlash against all thinking machines, reminiscent of Isaac Asimov's cautionary tales?
- Spot on. The burden and complexity of that cryptographic signing on the client is exactly what OAuth2 was created to avoid. Thanks for making that connection.
- This is fantastic, the leaderboard is really nice! It reminds me of Paper Planes.
- On the B2B2C section, my mind immediately went to OAuth. For a developer like Bob giving his end users access to a service, wouldn't a standard OAuth flow where his users grant permission to his app would be the more conventional and secure solution?
It feels like that model handles key management, delegation, and revocation in a well-established way.
What am I missing here that makes this a better fit?
- On their Reddit post [0], the creator mentioned that it took them '600 prompts'!! I’d love to see how they managed to organize their prompts! This is actually impressively well done. I think what is holding it together is a good music and documentary-style background voice-over. There are so many uncanny stills in the video, but the well placed music makes you overlook that.
[0](https://www.reddit.com/r/aivideo/comments/1lvtxbg/kira_i_use...)
- Could you share more about your process and how they specifically help you with your internal frontends? Any details would be great! Thanks!
- 3 points
- Any hints on what kind of tools you're creating for the inevitable mess?
- 6 points