“Tell me and I forget, teach me and I may remember, involve me and I learn.”
Often we do a 'group QA' session to validate the quality of Hyperledger Composer; we have QA scripts that we follow but also this gives the opportunity do some freestyle testing. This gives the opportunity to use the code for real, and also allows people to learn about parts of the product they haven't worked on recently.
This is good - but sometimes you can get staid, and just follow the same routes too mechanically. Are we really testing the code or just looking at the minor niggles too much 'really should add an extra pixel to that image'. Plus as the complexity and usage of the product grows, how many simple 'hello world' scenarios can you really write that are useful?
This week we did something different. An internal Hackathon based on tracking Airline parts. This allowed us more time to get into a scenario learn some features that many of us had not worked on (or honestly forgotten about). And also to really use the code as other users will do.
We had two hours starting from the idea above to produce something - it's impressive what was done in two hours.
Go and take a look at what we achieved - https://github.com/ampretia/airline-regulation
If you're interested in learning more about how to take advantage of unique abilities of a blockchain but quickly go look at Hyperledger Composer.