For people using AI coding in fucking VSCode — is there any way to prevent it from occasionally corrupting open files? I’m usually diligent about staging and committing to Git often, but sometimes it catches us off guard and good work gets lost. Sonnet 4 is the model in use.
#asknostr
Gustavo
limachaves@iris.to
npub1c09t...tecr
NEED. TO. STOP. EATING. POISON.
https://www.independent.co.uk/news/health/lung-cancer-ultra-processed-foods-study-b2798914.html
Dear @Jumble, please have sex with Iris and be as fast as it. Iris, you might want to leverage Jumble's awesomeness as well.
It's so funny how AI models like to take shortcuts, in order to spend less tokens (guess that is a pre-prompt of providers), from time to time. Just more arguing requirements put on the developers' side, sigh. Onward.
Keep these coming, love to see it.
Tokamak+fusion+reactor+turns+mercury+into+gold+
New Atlas
Tokamak fusion reactor turns mercury into gold
The dream of the ancient alchemists may come true as Marathon Fusion announces that its tokamak fusion reactor technology can turn common mercury i...
GitHub catching up to mkstack and derivatives.


GitHub
Build software better, together
GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.
SOS is my homie
View quoted note →
It's sad to see close friends playing the Luddites' take on AI (and don't even get me started on the posture towards Bitty). I guess history needs to rhyme, there is no way around it. We help when there is an opening.
Now that I'm more comfortable with Emac's "occur" command, I can't think how I went without using it for so long. Game changer.
Vibe, vibe, vibe.
