Drinkey/keyvault

development summary and retrospective

Opened this issue · 0 comments

Summary

The first commit is Nov 19, and on Dec 7, all planned features completed.

Almost 3 weeks of part-time development to get all planned tasks done, conducted several times refactoring.

Retrospective

  • Unittest is useful, especially for refactoring
  • OOP may not necessary for all projects.

Others

There is always saying that programming language is not important, the important thing is how to solve the problem. But without knowing your tools, how to create the proper solution for your problem?

I have more experience in Python. When I start learning Go several weeks ago, I always try to find the equivalent solution in Go compared to Python. I found I was wrong, they are different.

Plan

  • The client needs to be implemented.
  • And I need to figure out how to sign the certificate signing request via HTTPS. The client certificate does not exist yet...
  • There is value passing across functions and some can be changed to address passing. Need to figure out.
  • Refactor the model with ORM, the current implementation looks ugly.
  • Documentation
  • Orchestration and Deployment