The purpose of a board is not to give credit to developers. The purpose of a board, especially a Kanban board, is to visualize the workflow.
In this particular case, I see a few possibilities. However, without a full understanding of your workflow, I'm not sure that I can recommend one particular approach.
One approach is to create a "release board"...
Based on the comment that the Review column is for work that the implementer has identified as needing additional technical clarity or product or design review, I would suggest that the best course of action would be to remove the Reviewing column and address the underlying root cause(s).
Since Reviewing comes after Development, if the work was unclear and ...
If some of your items don't need review (although I think that's a bit unusual for a development flow), you can split your Development column in three sub-sections, something like this:
Development ( Doing | Ready for review | Ready for testing)
Once a ticket has completed development, you decide if the ticket goes to ...
And ... let me just kick in one other observation here:
"Toyota Manufactures Cars, Not Software!"
Always keep that in mind.
On the one hand, "project management [methodology ...] is all about finding productive ways to align groups of people in the pursuit of common tasks." However, "the physical manufacture of motor-cars along a ...