I have not checked this, but I assume that most excess vitamin D, which is stored in the liver, is excreted by the liver together with cholesterol and other cholesterol derivatives, in the biliary secretion, reaching thus the intestine, and not by the kidneys in urine.
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 :
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.
Have you found that this still saves you time overall? Or do you spent a similar amount of time acting as a code reviewer rather than coding it yourself?
https://youtube.com/shorts/EJmmq0yc08U?si=dnFXr0IgJh18pmp-