I think at least a 100-level knowledge of bookkeeping is beneficial to nearly every developer. Bookkeeping is, arguably, one of the oldest and longest-practiced "data processing" disciplines. It seems arbitrary and somewhat old-fashioned until you grok the reasoning and history behind it (double-entry sourced from summaries of various different "journals" to facilitate separation of duties, closing periods and rolling-up detail entries into totals because human computational power is limited, an equation that balances implicitly when there aren't entry errors, etc.)
Odds are that your work somehow impacts the revenue or expenses of your business and will need to interface with accounting or finance people at some point. I found it increased my perceived credibility when I could speak using terminology from the accounting or finance person's area of expertise.
I also agree with other posters who would argue that everyone should have some basic proficiency in double-entry bookkeeping. That's probably way too optimistic, though.
Odds are that your work somehow impacts the revenue or expenses of your business and will need to interface with accounting or finance people at some point. I found it increased my perceived credibility when I could speak using terminology from the accounting or finance person's area of expertise.
I also agree with other posters who would argue that everyone should have some basic proficiency in double-entry bookkeeping. That's probably way too optimistic, though.