A modern programming language that makes developers happier.

kotlinlang

`Day64`
• Fixed bug(Menu bar status not being updated after refund - Called GET me at the end of each branch, probably not the smartest approach)
    ◦ App life cycle is so interesting. I first called that GET me on `onDestroy` of mypass fragment. However the menu was still not being updated. As I printed the logs, `onResume` of main activity was being executed earlier than `onDestroy` of mypass fragment. Since menu drawing logic was handled inside `onResume`, GET should be executed earlier.
• Showing dialog when refund is impossible, Showing dialog when purchasing a new pass is impossible
• Handled user who never purchased a pass, Fixed date formatting for expiration date
• QA ing
`Day65`
• Fixed inapp url for Store fragment (I did not update the temporary url with inapp url…. my mistake.)
• Hiding refund button after expiration or refund
• QA ing 
`Self-Comment`
• QA takes really long. Especially, this sprint has too many scenarios to check. I prepared a checklist for each type of pass(hourly pass, count pass, original promotion pass), user type(New user, user who’s currently using a pass, user who owns a pass but did not start a ride yet, user with expired pass etc.). Since I’m the one who can test all these (cuz I build the app..), it became my job to found bugs from server-side and web-side. But, server engineer has other issues to handle, so I have to wait QA for that bug. It is somehow inefficient, but I can’t think of any better solution for now. Current process goes like :  (rough project design) - (rough development) - (QA detailed discussion with regard to the project design and implementation) - and umm, though it’s quite troublesome for everyone, this can be the most lean cycle. (I mean, developers can’t wait for designers and project manager to fix every small details)
• Fortunately and finally, store sprint is almost done. Now it’s time to wrap up QA on monday, put some data gathering logics for data analysis team to analyze. Hope there’s no other huge or small bugs to fix further.
`Goals Tomorrow`
• Amplitude jobs
• Finish store QA
• As far as I know, next sprint requires uh.. sdk..?job. (Which I don’t know at all.) Should check things related to sdk developing..