As a daily user of this app, it's really great. There's also an adjust serving size feature which updates the ingredients amounts dynamically once you've made the recipe:

After figuring out how to make the coordinates work, it's so satisfying to use a live-updating drag and drop that previews where the dropped content will go.

We already stopped using Hershey's, but last camping trip we used 2 of these instead of using graham crackers and chocolate, it was an upgrade in every way. Pre-layered for ease of assembly in the dark, double the chocolate (top and bottom). Never buying graham crackers again for s'mores.

Or if you stopped reading at "regular expression", Gemini can probably just do it directly too!

And before you go and try do that change manually, you can use a regular expression find and replace and captured groups to do it in one fell swoop.

More details: www.jetbrains.com/help/idea/tu...

Annoyed with merge conflicts when updating versions in libs.versions.toml?

If you add a "#libraryName" above each version entry, you can avoid the merge conflicts caused by adjacent lines being updated independently since each simple version bump will have an unchanged line in-between another.

Is it over-engineered? Probably, but it helped me build a seamless handoff for concurrently editing state where the only direct point of communication between the two pieces of UI is a disk-backed DataStore.

Let's start with the most straightforward approach: we observe the disk, use it to set the slider's current value, and when the user moves the slider, we update what's stored on disk.

Seems great! We have a single source of truth for the state following unidirectional data flow. But...