Observations about Raphael A.

  Observation created over 5 years ago

Documentation is vital for a software company. That is true for all aspects of our app but particularly user management. Lessonly cannot exist without learners, so the action of making it clear and easy to get users into Lessonly is important. Even though I know all of that creating documentation can be seen as the least fun aspect of software. It is more fun to build new stuff than to write in painstaking detail about the stuff you just built.

With all of that being said, it only makes what Raphael did more impressive. We recently wrapped up the development of SCIM for OneLogin. We were left with the documentation piece. I tried my best to get it started but we reached a point where we had to set the JSON user schema and I was lost. Raphael (who got involved late to the project) was able to familiarize himself with the code base and write some killer documentation (found here: https://docs.google.com/document/d/1zaEPLM1wtiDHBth9owIG29R2c-3oYWq04jPtxvH-5P0/edit#)

This is the definition of a team player. Hopping onto a project and helping out any way you can no matter what. Raphael has always been game for these sort of things but I was reminded again by this.

  Observation created almost 6 years ago

https://lessonly.slack.com/archives/G8Q5B0EVA/p1560261306012400

That slack thread tells the entire story...

1) See a problem
2) MEASURE the problem in a quantitative way so that you know if you've fixed it
3) Plan a fix for said problem BEFORE it becomes an issue that stakeholders are even aware of
4) Work collaboratively on the problem without interrupting other priorities
5) look at the measures from step 2
6) Celebrate together

Love nearly everything about this.

Way to go y'all!