Is ACM membership useful for just typical developers not in research or grad school?
(Reading papers on a regular basis is something that I encourage developers and managers to do; it's a good way to expand your toolkit and get ideas for different ways to solve things. A paper a week -- maybe an hour a week, on average -- and that's like fifty new things you've been exposed to in a year. These add up, and eventually can make a big difference in how you approach problems).
lock free data structures. static analysis. solvers for systems of equations. cache maintenance techniques. concurrency control. etc.
most jobs though don't afford the latitude/scope for you to be looking into details like that in the first place.