Yeah I really would not want all my convos synced up like this. I've been working on a personal version of something like this but it keeps all your conversations and notes in a separate Git repo that you control that's totally separate from the project repo - it's entirely designed for personal use:
It's interesting - YouTube does show AI summaries now - here's the one for this video:
This video explores dishwasher detergent, focusing on a new powder formulation. The creator details the science behind effective dishwashing, including pre-wash cycles and water temperature. Independent testing results comparing the new powder to leading pods are revealed.
I've noticed that they all seem to not give away too much so you still have to watch the video to get the conclusion. It makes sense why they do this for creators, but I do agree it would be awesome to just read the conclusion on many of these.
A few years back a friend approached me with an idea to track todos in Google Calendar directly by adding #todo to event titles. If you don't mark them as done they will roll forward to the next day. We ended up shutting it down as a product, but I recently vibe coded it back as a Google Apps Script so it's free to run on your own. It works super well for people who live off of their calendar - https://github.com/slackpad/hashtagtodo-redux.
Claude Code running in a terminal can connect to your IDE so you can review its proposed changes there. I’ve found this to be a nice drop in way to try it out without having to change your core workflow and tools too much. Check out the /ide command for details.
Not the parent but I've totally been doing this, too. I've been using docker compose and Claude seems to understand that fine in terms of scoping everything - it'll run "docker compose logs foo" "docker compose restart bar" etc. I've never tried to isolate it, though I tend to rarely yolo and keep an eye on what it's doing and approve (I also look at the code diffs as it goes). It's allowed to read-only access stuff without asking but everything else I look at.
Really agree with the author's thoughts on maintenance here. I've run into a ton of cases where I would have written a TODO or made a ticket to capture some refactoring and instead just knocked it out right then with Claude. I've also used Claude to quickly try out a refactoring idea and then abandoned it because I didn't like how it came out. It really lowers the activation energy for these kinds of maintenance things.
Letting Claude rest was a great point in the article, too. I easily get manifold value compared to what I pay, so I haven't got it grinding on its own on a bunch of things in parallel and offline. I think it could quickly be an accelerator for burnout and cruft if you aren't careful, so I keep to a supervised-by-human mode.
Yeah - I think early users are going to click on a link too and don’t really care. If you were really advertising or something with traction you’d want a nice domain but I don’t think it would hurt early adoption of little saas tools.
I ended up using one of my more generic domains (https://www.modulecollective.com/) and then launching things as <product>.modulecollective.com. It's a little wordy but it's free and creates kind of a natural place to catalog things. I figure if any of them take off then I can go buy a better name later and move it over, having the old one redirect. That would be a good problem to have :-)
That particular domain was going to be like a Netflix DVD style subscription product for Eurorack modules but I never even ended up trying to build that after buying the domain.
Haven’t tried it yet (I’d love to find something like this too) but I saw a conference talk on https://docs.voxel51.com/ that looked pretty interesting. It is kind of a data frame for images with a GUI for exploring them. They make it pretty easy to rip various models over your images to add tags, and to evaluate the results.
Forrest Mims did a bunch of interesting hand drawings like that back then but I don’t recall the specific book or image you are thinking of. I’m curious to see if you find it - it sounds up my alley too.
Did anybody find any references to the materials on the outside of the Push 3?
I loved the Push 2 but if it got any amount of sunlight on it the rubber outer shell would sweat and become this sticky rubber mess. I don't have a fully protected area to keep the device in and it became so gross it was unpleasant to use and I stopped using it. A lot of people complained but they didn't deal with it very well, and directed you to hope for the best by scrubbing it with orange oil products. I hope they sorted this out because otherwise Push 2 was amazing and this looks like a very nice set of improvements.
https://www.kickstarter.com/projects/electro-smith/daisy-an-... is worth a look as well. They have dev platforms in Eurorack, desktop synth, and guitar pedal form factors that could be used for something like this, though they have enough DSP to actually run the audio processing the module, but it seems like it could be used for something like a hybrid setup as well with VCV rack with some software work.
I saw a variant of this where they used a very similar script but the text came from Apple. They were attempting to add the card to Apple Pay so they could easily use my stolen card number in physical stores.
This is a great read! The code is very clean and easy to follow and the progression of ideas is well thought out. Even if you don't know Go you could learn that along the way without too much trouble. He also just released a companion volume writing a compiler for the Monkey as well.
https://github.com/modulecollective/moe