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

Very nice, thanks for creating this!

> The system we want, where the octave is pure and the fifths are pure and everything closes into a neat loop, does not exist and never has. Every tuning system in history is a different choice about where to dump the error.


Maybe a complement. A well designed software ideally makes it easy for developer to contribute and avoid errors. It includes a lot of system / structure and documentation that ensures nothing gets broken or overlooked.

In such a context also a coding agent has it much easier. But establishing that or adding something beyond what's already safely established, here high intelligence models really pay off


I tried this actually and wasn't so happy with the results. First you search / index twice and that will cost. You'll have to wait for the slower of the two as you don't want to reorder after already showing the user.

You'd need some scoring where precise hits get better score than those only found by fuzzy search. With that it's maybe acceptable, but I personally preferred just being able to switch it easily/quickly when needed and by preference.


Fuzzy is usually faster. Grab the fuzzy results then exact match within them, no second index needed


That's a fair point. Personally, the search latency wouldn't bother me unless search is the primary mode of interaction in the application context.


I feel you, I also prefer precise search in most cases.

In a private bookmark extension project, I explictly supported both and made it easy to switch them any time: https://github.com/Fannon/search-bookmarks-history-and-tabs


Or this: https://www.youtube.com/watch?v=0L8ugmv3Qns

The Captain Pikant videos are really well done aestetically


If I needed something like this, my first try would be to take a MIDI / DAW controller like Novation Launchpad Mini Mk3 and write a script for it.

This would be cheaper, much more versatile and customizable I bet. Many MIDI / DAW controllers can be "programmed" via MIDI IN/OUT, e.g. how to light the pads.


While I got me a 16GB Macbook Air, I appreciate that Apple continues to make 8GB devices. This indicates for me also a commitment for not bloating up the OS (like Windows did) too much and caring about memory efficiency.


I don't understand this logic. You can live with 8 GB but there is nothing to "appreciate". It's enough for some stuff but totally short for other stuff.


I'm not surprised if this is true to a wide degree (not fully).

What the people that predicted that AI will change productivity drastically in just a year or two imho underestimate: Just because a technology is capable of this in theory (and I think it is, even today) - it doesn't mean we are willing or able to deploy it to its full potential at scale. There will be a few individuals and very few companies which will do so or come close.

For most of the companies, they're still doing a lot of processes manually that could have been automated with 80s technology. Why should a change in the technology suddenly make everyone change their mindset, culture, way of thinking? This may take 1-2 generations to more fully form. Maybe that's also better: Slower change is less destablizing for society / individuals, I think of it more like a defensive mechanism of the system to keep it stable.



There goes my productivity for the weekend. :-D


I'd be interested in how you setup those repos for non-coding tasks, thanks for sharing!


For non‑coding work we still treat a repo as the source of truth, but it’s mostly Markdown, checklists and assets rather than code.

Think of it as a structured project brain that AI can read, update and score.

For example, for social media management our repo's outline structure that are getting to be is as follows (still WIP):

social-media/ README.md # How this repo works, scoring rules /config platforms.yaml # Accounts content_guidelines.md # Brand voice, do/don’t list /planning 2025-12-calendar.md # Calendar 2025-12-campaign-x402.md # Campaign brief, goals, KPIs /drafts 2025-12-05-x-new-feature.md 2025-12-16-x-new-feature.md /assets images/ video/ copy-snippets.md /published 2025-12-05-x-new-feature.md # Final copy + URLs + timestamp 2025-12-16-x-new-feature.md /reports 2025-01-05-metrics.md # CTR, saves, comments, etc.

Daily tasks are then deterministic checklists inside the repo, e.g. “Create 3 drafts for next Tuesday with images in /assets/images and entries added to 2025-12-calendar.md under campaign X”.


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

Search: