I author internal software rather than something public, but I think this method still would apply thinking back on SaaS apps I've built.
I use Github generated release notes based on Pull Request bodies and this is more than sufficient for my dev team.
I think have a small app in my different internal web application called `releases` (a Django app) that has a simple model called Release. I hand write the release notes, copy and paste the version number, and select date for each release (sometimes I'll batch add them if I get behind).
But I had write them with my audience in mind (business system users - who care about specific bugs or features; i leave out any internal things that wouldn't be of interest).
At the footer, or a small indicator in side bar, I display the version number that was created through our automated release process (Github Release triggers a release and the tag that is the version number gets set as an env var in my Docker image). Clicking that takes the user to a /release-notes/ page that has a descending order list of the notes that I hand author in the Django admin.
Pretty low tech but I find I like to be able to hand author the notes with the user's in mind.
You can save some memory by moving to Polars from Pandas but watch out for a subtle difference in the quantile's different default interpolation methods.
Claude, can you please explain this for someone with a high school level understanding of science?
I'll break this down into simpler terms!
You might have seen viral videos or heard about what happens when you put two grapes in a microwave - they create impressive sparks and even plasma (which is like a super-hot, glowing gas, similar to what's in those plasma ball toys).
The key points of this paper are:
First, some background:
- When two grapes are placed close together in a microwave, they act like a special kind of antenna or lens for microwave energy
- This creates an incredibly intense concentration of energy between the grapes (they call this a "hotspot")
What's new in this research:
- The scientists used tiny diamonds that contain special defects called nitrogen-vacancy centers (think of these like extremely sensitive sensors)
- They placed these special diamonds between two grapes in a controlled setup
- Using these diamond sensors, they could measure how strong the magnetic field was between the grapes
- They found that the magnetic field between the grapes was twice as strong as it would be normally
Why this matters:
- Previous research only looked at the electric fields between the grapes
- This study confirms that grapes can also concentrate magnetic fields
- This could be useful for quantum computing and other advanced technologies that need precise control of magnetic fields
Think of it like this: If you put two magnifying glasses next to each other, they can concentrate light into a very bright spot. The grapes are doing something similar, but with microwaves instead of light. The scientists used special diamonds as a tool to measure just how concentrated this "microwave spot" becomes.
---
I don't even try reading stuff like this on my own anymore. Maybe I'm just dumber than most, but I find Claude's explanation so much more accessible.
"With nearly 30 years of data showing significant progress, it’s clear that farmers in the EAA have done more to improve water quality in South Florida than any other private group in state history."
+1 for Trustworthy, it’s a really fantastic product. The app is well designed, constantly improving and the founders really seem to understand the problem they are solving.
thanks for sharing Trustworthy - I'll check it out.
if you're willing to share: do you worry about their security or do you feel that they're at least as secure as what you could do yourself or other services might do?
I've worked on plenty of large projects and haven't run into places were I've "lost control". Just the opposite, I have found it to be very extensible.
I'm curious if there are cases I haven't hit that you have, though.
I use Github generated release notes based on Pull Request bodies and this is more than sufficient for my dev team.
I think have a small app in my different internal web application called `releases` (a Django app) that has a simple model called Release. I hand write the release notes, copy and paste the version number, and select date for each release (sometimes I'll batch add them if I get behind).
But I had write them with my audience in mind (business system users - who care about specific bugs or features; i leave out any internal things that wouldn't be of interest).
At the footer, or a small indicator in side bar, I display the version number that was created through our automated release process (Github Release triggers a release and the tag that is the version number gets set as an env var in my Docker image). Clicking that takes the user to a /release-notes/ page that has a descending order list of the notes that I hand author in the Django admin.
Pretty low tech but I find I like to be able to hand author the notes with the user's in mind.