325 karma · joined March 23, 2020
- [codes] showing up instead of references,
- raw search tool output sliding across the screen,
- Gemini continusly answering questions asked two or more messages before but ignoring the most recent one (you need to ask Gemini an unrelated question for it to snap out of this bug for a few minutes),
- weird messages including text irrelevant to any of my chats with Gemini, like baseball,
- confusing its own replies with mine,
- not being able to run its own Python code due to some unsolvable formatting issue,
- timeouts, and more.
There is something satisfying in noticing the same solution applied to problems in different domains, like audio, medicine, and aviation.
My only Apple product is also an iPad, and I mostly use it to make music with Auxy Studio:)
Do you use any fun apps on Android? Currently, my favorite apps are Digitron and Nanoloop. (No affiliation, but Digitron's upgrade was gifted to me.)
I also played with the idea of letting users slide their finger off a knob (tap and slide away from the center). This allows for moving the finger over a longer circumference, hence enabling a great degree of precision. The problems with this approach are that it takes longer to operate such knobs, you need to communicate to the user what the max allowable distance from the knob is, it can interfere with scrolling, and it doesn't work for knobs close to the edge of the screen. (Your idea works well for knobs at the edges.)
And this is just knobs! There are many other components, interactions between them, as well as associated accessibility challenges, haptics, etc. Instead of reinventing the wheel, I was hoping that human factors people had developed relevant guidelines, but perhaps it simply is not a prevalent enough problem.
2. Speaking of knobs, I am writing a toy software synth for smartphones. Are there any design guidelines for mobile UI for audio? Knobs are hard to use and sliders take up a lot of space with only a little more precision. I experimented with curved sliders (inverted parabola or sine), but they are confusing since height doesn't really encode anything and the curvature is there only to make the slider longer. I didn't find any design systems focused on audio components.
Do you come across issues like this too or am I not prompting it correctly?
Are there any very affordable DIY midi control surfaces with a few knobs, pads, keys (two octaves), and BT?
Use case:
Building a personal RAG system as a weekend project.
Tool used:
OpenHands and Trea, both running in Docker.
Cost in $:
$60
Cost frequency:
One-time (over 3 weekends)
Cost includes:
Mostly API usage and infrastructure
Satisfaction:
Low (10%?) — the final system worked much worse than `ripgrep`.
The AI often produced unusable or overcomplicated results.
I ended up spending more time debugging than... vibing.
Usefulness:
AI is helpful for certain programming tasks, and GitHub Copilot can be useful (when it’s not overeager). But in this case, the “vibe coding” approach felt inefficient and frustrating. Might’ve been better with higher-end tools, but hard to say.I find AI very helpful for some programming problems and GH Copilot can be very useful sometimes (especially, when it is not overeager), but this vibe coding business is beyond me.
(I only used OpenHands and Trea in Docker. I haven't tried more premium products due to budget constraints. In hindsight, maybe I should have.)
I wish there were two versions of the UI:
1) the current "God mode" with hundreds of services and nested pages for cloud uber natives that grok all that, and
2) a simplfied UI for simple devs like me. There could be a few types of the simplified UI, depending on what you do (mobile dev, ML researcher, AI engineer, web dev, etc.).
Currently, I spend way too much time scrolling and navigating between different pages to set up or troubleshoot basic things.
I wish I had the time and skill to read the whole 180 pages of your dissertation with full understanding, but I will spend some time with it. I like some of your diagrams already!
Anyway, yes, they come from a service you are using with the subject line "[Kagi Search] There Are Some Untranslated Phrases." I know how to unsubscribe or reroute emails to my spam folder.
Kagi team, folks say you have a great product, but if you don't pay attention to small issues like this one, you are bound to lose some of your goodwill.
Learn more at viridiandynamics.com/apply
The very act of issuing a disclaimer can create a sense of distrust. It suggests that the author anticipates skepticism or potential backlash, raising questions about their motives and the integrity of their work. This is particularly problematic in academic settings, where disclaimers can undermine the authority and rigor of research findings. While acknowledging limitations is crucial for responsible scholarship, the way these limitations are framed can significantly impact how the research is received and interpreted. A carefully worded disclaimer can acknowledge potential weaknesses without undermining the overall strength of the argument, while a poorly constructed one can create unnecessary barriers to engagement and understanding.
For this reason, I created Craft Your Disclaimer, an AI-powered service to help creators craft disclaimers tailored to their goals and audience preferences. You can register for free at: CraftYourDisclaimerOrSomeOtherBS.ai