Open ten tabs in Chrome. Maybe even twelve!

I don't think you need 32GB of RAM. 16GB should be enough, and 8 will still do for light tasks (though modern apps and websites are starting to push that, which is terrible). Your OS uses any RAM you don't use to cache files, which speeds up your system, reduces power consumption, and could save you some SSD wear by caching the writes.

If you haven't already, you can mount a tmpfs over your browsers' cache directories (a bunch of them in ~/.cache or ~/. config). It used to really speed up browsing back in the HDD days. I doubt it's still necessary, but hey you've got plenty of RAM, right?

If you really don't do anything but browsing, you could boot your entire OS into RAM and have a 0 SSD latency browsing experience.

You could also use the RAM to run a bunch of VMs or containers. I used to run a separate Pihole VM, for example; virtual machines are nice and isolated, so you don't risk ruining your /etc directory with a billion different configured services. The big downside of running such stuff on your machine is that you quickly end up with a whole bunch of duplicates (I have like four versions of postgres running on a server somewhere because I'm lazy) but if you have RAM to spare, that doesn't matter.

One container that may be worth looking at is Waydroid (or Anbox if you're on X11) to run Android apps on your desktop. I find that a bunch of different services have web interfaces thst just don't work as well as their apps, and running those can be nice. How much of a difference this makes will depend on the services you use, of course.

Lastly: don't underestimate the advantages of plenty of RAM when programming. It'll depend on what language you use, but many compilers will generate a million tiny files that will all be written to disk and read back. SSDs are fast, but random reads are still nowhere close to RAM speed. Your OS will hide most of this overhead, but I definitely felt the difference going from 16GB to 32GB because of file system caching alone.