You can discuss things unrelated to genuinely proprietary information. But this depends on the company—I worked for several companies whose secret sauce was mor

You can discuss things unrelated to genuinely proprietary information. But this depends on the company—I worked for several companies whose secret sauce was more related to proprietary business information rather than proprietary tech, so they gave close to zero shits if I publicly wrote about it and, at times, republished my posts on their own company blog to make themselves more attractive to devs. I also have a bunch of personal projects about which I can talk. Topics like "what we learned load-balancing a tomcat cluster" contain genuinely useful information, but the company I worked for at the time didn't consider them proprietary because the proprietary stuff was what they ran on the cluster. I'll acknowledge that this won't be the case for everybody. I've been pretty lucky that none of the companies I worked for prevented me from writing about these topics; some were happy to use what I wrote for their own promotional material. (I don't want to dox myself, so I'd rather not share a link to my blog, and "what we learned load-balancing a tomcat cluster" isn't the literal title of a blog post I wrote.)