timrichard

And is then finished in a trouser press…

> you'll just pee out the extra Vit D.

It’s fat soluble, rather than water soluble

One interesting thing to note is that many people use more force than necessary with their fretting hand. This was certainly true of me. Some hold the guitar neck with some sort of death-grip.

One useful exercise is to fret a note as you normally do, and play it. Then keep picking or plucking that note with gradually less pressure applied by your fretting fingers. At some point, the note will choke and not sound out any more. Then, a little more pressure can be applied to make it sound out again. That minimal level of force is going to be the ideal amount for stamina and to prevent injury. There’s nothing to be gained by pressing harder, in fact you can bend notes slightly sharp by pressing really hard. In many forms of instrument practice, hand tension is often the enemy (especially for faster soloing).

The faucet seems a bit drastic. I got a 1L (about 32oz?) spray bottle of Isopropyl alcohol, and use a small spray amount onto a microfiber cloth to clean iPhone and iPad screens. It’s really cheap and seems to last a long time, as only a small amount is needed.

It will degrade the oleophobic coating of the screens quicker, but I figured that would wear off over time anyway. So far it’s been really effective at wiping off all greasy fingermarks in seconds. I like the window/glass type microfiber cloth for this.

When I started using systemd timers, I really liked the systemd-analyze calendar facility, to calculate n trigger times for a given calendar expression.

For example, show the next five trigger times for the end of the last day when the month has 31 days :

systemd-analyze calendar --iterations=5 '*-*-31 23:59:59'

Yes, I think so. Often it doesn’t take much more than a glance for simpler edits.

I think you’re absolutely right and I’ve come to the same conclusion and workflow.

I work on one file at a time in Ask mode, not Composer/Agent. Review every change, and insist on revisions for anything that seems off. Stay in control of the process, and write manually whenever it would be quicker. I won’t accept code I don’t understand, so when exploring new domains I’ll go back with as many questions as necessary to get into the details.

I think Cursor started off this way as a productivity tool for developers, but a lot of Composer/Agent features were added along the way as it became very popular with Vibe Coders. There are inherent risks with non-coders copypasting a load of code they don’t understand, so I see this use case as okay for disposable software, or perhaps UI concept prototypes. But for things that matter and need to be maintained, I think your approach is spot on.

I have been adding .env files to .cursorignore so far.

I can see from that thread that the approach hasn’t been perfect, but it seems that the last two releases have tried to address that :

“0.46.x : .cursorignore now blocks files from being added in chat or sent up for tab completions, in addition to ignoring them from indexing.”

A button with a dice icon.

I should do a lot more with Alfred, but apart from using it as a launcher my most used feature is the clipboard search. After invoking it by typing 'clip' into the box, I get an incremental search on all clipboard contents it has tracked, and can re-copy any of those items to the current clipboard by pressing enter. Very useful and efficient when it's part of your workflow.

I've been using Jetbrains IDEs for quite some time. I currently use IntelliJ and Cursor together. Cursor is everything I hoped Jetbains AI would be. The TypeScript support in VSCode and derivatives (like Cursor) is great, unlike Jetbrains. As I already have a license, I switch to IntelliJ for the fantastic Git and DB plugins, as well as the great refactoring and find/replace features. Local History and diffing in Jetbrains is also far superior, so sometimes I use history labels as snapshots in between significant changes from Cursor.

If you're transitioning from ChatGPT pastes to an IDE integration, I would recommend a trial of Cursor. They have acquired SuperMaven, and the autocomplete feature is mostly appropriate and useful. I think the chat-diff-review-apply workflow really tightens and accelerates the feedback loop, as well as the ability to submit an error from the terminal to the chat session with a single click. People say good things about the Compose and Agent features, but I haven't so far been drawn to them to explore.