I think strengths are more difficult to define than weaknesses, because they are very context dependent. “Speed” may be useful in certain situations, but in many cases “speed” can be harmful in more ways than just overlooking details. You miss out on opportunities to learn, to ask for help, to become better at thinking critically as a software engineer.

What the idea of “strengths being weaknesses” reflects is how much we identify with our present state of ability. It seems like we get it backwards. We ask our jobs to fit us as people, rather than how we as individuals can become best for the job.