But whatever, the experience is bad: I have to wait for the Music application startup time, then click the context menu and select "Quit Apple Music". It feels like being forced to watch a product ad. Opening Apple Music is never what I want. Imagine if pressing shift opened TextEdit by default, that would be silly. Or doing CMD-v where you can't paste would automatically pop up some random app.

I feel like no machine response is a correct UX pattern in this case. The absence of sound playback would indicate to me that I need to do something else to play sound.

Whatever is the last thing that was paused should play IMHO. If nothing was paused, it should do nothing. Else, you open a pandora's box of possibly wrong choices that the user then has to close.

So combined with the issues claude has been experiencing in the last couple of weeks (see https://news.ycombinator.com/item?id=47660925) - codex has become a better option. Claude has been unable to complete simple tasks and got lost in 5+ minutes of exploration too many times and I just called quits.

https://github.com/antoineMoPa/moonreview

The intended use is to run `moonreview` instead of `git status` / `git diff` or `magit`, but you can add comments and they get auto resolved. You can also stage hunks if you are happy with them.

Probably other tools exist or will appear in this space (I saw at least another one in the comments on this post), but i think there is something fundamentally too slow and dumb with current corporate code reviews. People are reviewing other people's slop and most of the comments are probably fed back into an agent. So why not have the whole process be done upfront by the original developper. Another cool thing I saw people do is to attach claude to github PR comments, which I think is great and love to work with this, but it's even better if we can also have this locally to catch sloppy code before it even reaches github.

- Working later because of addictive loops.

- Wasting time and money building stuff nobody will ever use.

- Abusive screen time.

- Loss of deep understanding of a code base and over-reliance on the AI, with reduced incident or bug response time.

- Producing a lot of sloppy code, too much to be owned or reviewed.

- Mental fatigue.

https://news.ycombinator.com/newsguidelines.html

My favorite output so far is that I asked it what life was and in a random stroke of genius, it answered plainly: "It is.".

It's able to answer simple questions where the answer is in the question with up to 75% accuracy. Example success: 'The car was red. Q: What was red? ' |> 'the car' - Example failure: 'The stars twinkled at night. Q: What twinkled at night? ' |> 'the night'.

So nothing crazy, but I'm learning and having fun. My current corpus is ~17mb of stories, generated encyclopedia content, json examples, etc. JSON content is new from this weekend and the model is pretty bad at it so far, but I'm curious to see if I can get it somewhere interesting in the next few weeks.

https://github.com/antoineMoPa/rust-text-experiments

Comments URL: https://news.ycombinator.com/item?id=46615068

Points: 1

# Comments: 0

> Developers are not Idiots

I'm often distracted and AIs are idiots, so a stricter language can keep both me and AIs from doing extra dumb stuff.

Comments URL: https://news.ycombinator.com/item?id=45074640

Points: 4

# Comments: 0