The overriding thing is to "take care of each other". If they want more updates, send more updates. If they want less updates, send less updates. How do you know what they prefer? Ask them.
Then comes the adage 'under promise over deliver'.
If you send out an update saying you're working on cool X module/technology/idea to solve a problem, and then it turns out you couldn't, it's a bummer across the table.
Even if it succeeds, you don't get much credit for it because everyone 'pitched in' with their ideas/tweaks at the beginning, so now the entire team feels like you were just the implementer of the team's design/strategy.
Call me a lone-wolf cowboy if you will, but it's a plain truth that no amount of 'team-players' can deny.
And if companies do not want to work with such under-communicators, no big deal. Not everyone meshes with everyone else. There's plenty of other candidates in the sea, and plenty of other companies in the sea.
Communicating about communicating is underrated.