Certification has gotten a bad reputation, but if approached correctly, it's invaluable.
Why do we write acceptance tests, and user stories? So we can certify our programs.
Why should we take certification exams, so we can validate our skill sets before moving forward.
Know what you want to do, and know that you can do it.
Don't fall victim to imposter syndrome or the Dunning-Kruger Effect.
How does this apply to me as a developer?
- The first step after knowing the a plan and/or a feature is to verify your assumptions.
- Certify that you are working on the right thing in the right way.
- As a developer, this is the time to advocate for Spikes and Proof of Concepts or “Tracer bullets”
- Certify that your usage of terms is consistent across the company. In the above example, of Spikes, Tracer Bullets and PoCs, they can all be the same, and they can all be different. Certify with your team how you will be doing these things.
- Always certify. Take tests to certify your knowledge, communicate to certify your assumptions, work with small focused goals to certify your plans.