Been on testing for years without problems. Super reasonable choice for a personal machine if you need recent software versions.
Always use a separate partition for /home, have backups in place and your golden.
I’m no AWK expert but I know just enough to tell when it’s the right tool for a particular job. Most pipelines consisting of `grep`, `sed` and `cut` commands can be replaced with a single AWK command. In this case:
stat / | awk '/Birth:/ { print $2; }'
For the line containing the `Birth:` regex, print the second field (by default, fields are delimited by spaces). Other lines that don’t match the regex are ignored.
stat command gets the detail of when the OS was installed on the machine. uptime doesn't give that. I wanted to say that I have been using the same development machine at work for 4.5 years. "running" was not the right word for it, obviously.
You can also use apt-pinning to set priority for which release to use.
A long time ago I ran stable, and pinned testing at low priority.
Across the decades I've slowly upgraded my stance. Now my machines run Debian Unstable, with testing and experimental pinned at very low priorities. Unstable does sometimes have unsatisfiable dependencies, so it's good to have some other options. And sometimes I just want what's coming for a specific package or kernel, and experimental will often be there.
This way, you can also have a rolling distro.
https://wiki.debian.org/DebianTesting