Try   HackMD

NTUST 2019 Internship - My Daily Report

Preface

Hi everyone, welcome to Taiwan and please make yourself here! Allow me to introduce, maybe again, myself, my name is Aldy, a Indonesian student from University of Indonesia. I take my internship program on Summer 2019 on NTUST under Prof. Ray-Guang Cheng supervise.

In NTUST, I take my internship on Broadband Multimedia and Wireless Laboratory (BMW Lab). I met with many good friends there and enjoy my work as much as I enjoy this life. I hope this internship program will be one of the my best experience in my life which I will never regret about anything.

In short, this section will be my daily report when taking internship in lab. Also, if you want to see my pre-intern weekly report you can see Progress Report here. Here listed the daily report from 1 July to 29 August:

Main Goal

Use Progressive Web Apps (PWA) to Develop a Management System for Smart Water Dispenser

Objectives

  • Build user app using PWA
  • Build repairman app using PWA
  • Maintain the applications until the internship is done

Table of Contents

July Report

Table of Shortcut

This is the table of shortcut for July daily report, if you want to see more details please go here.

Use this to add more: | Nth | Your_target | Not yet | - |
Date
Target
HackMD Report
More Details
1st Getting up everything Done Here
2nd Summarizing meet up with mentor and team Done Here
3rd Storage information of device ID of parameter passed from last page Done Here
4th Using local storage for Nearby Machine page and Maintenance Progress page Done Here
5th Implement session for login system and save session ID and email Done Here
8th System that store ID as session when user login and implement into login page Done Here
9th Implement the session login system in all pages inside project, also change the API called using service Done Here
10th Dispenser API service is implemented in pages needed, no longer to call http POST/GET from the pages Done Here
10th 1st Weekly Report
(Professor in present: Prof. R.T.)		 Done -
11th Searching material for manifest PWA and create the UI Done Here
12th Fixed the problem on manifest json for PWA, document by commenting the services, also classes, code in Github Done Here
15th Write report about coordination when build PWA in process Done Here
16th Finalize code for login, register, maintenance progress, and nearby dispenser page Done Here
17th Finalize code maintenance progress, integrate with dashboard page, discuss for Repairman PWA Done Here
18th 2nd Weekly Report
(Professor in present: Prof. Ray)		 Done -
18th Fix some bugs found in project and report into HackMD Done Here
19th Start to merge project with others, cleaning debugging code, add some features Done Here
22nd Add loading bar as identify wait progress, segment view for multiple maintenance progress, commit to github Done Here
23rd Implement loading screen in all pages, finish maintenance progress issues, search and implement lazy loading for images Done Here
24th Finish all remaining task, giving documentation, clean up code, deploy to domain, and report in HackMD Done Here
25th 3rd Weekly Report
(Professor in present: Prof. Ray and Prof. R.T.)		 Done -
25th Import important and will be use components from User App to Repairman App, documentation that show what being imported Done Here
26th Create authentication (login and register) page for repairman app Done Here
29th Add feature to show more information on each item in Nearby Dispenser and Maintenance Records page Done Here
30th Create the service API for Repairman App, implement into dashboard page Done Here
31st Integrate the Dashboard page so all three fragment pages can dynamic get data from back end code, use dummy data to test Done Here

More details for July daily report

This is the details of daily progress, click the report link to see more in HackMD.

Use this to add more:

M. July_August Nth Daily Report

  • Title:
  • Outcome:
  • Deadline:

Summary:

Report:

1. July 1st Report

  • Title: Getting up in Taiwan
  • Outcome: Summary of my journey
  • Deadline: -

Summary: -
Report: July 1st Report

2. July 2nd Report

  • Title: Getting up everything
  • Outcome: Summarizing meet up with mentor and team
  • Deadline: 3 July evening, because in 2 July I haven't write the report

Summary: -
Report: July 2nd Report

3. July 3rd Report

  • Title: Local storage
  • Outcome: Storage information of device ID of parameter passed from last page
  • Deadline: 3 July evening

Summary:

  • Want to use local storage
  • Storage using app preferences, this system as same as shared preferences
  • Shared preferences has weakness, it cannot be use by browser in emulation, has to be build first and run in real device
  • For storing will using LocalStorage
  • Data will be stored is device ID which passed from another page

Report: July 3rd Report

4. July 4th Report

  • Title: Local storage for saving device ID
  • Outcome: Using local storage for Nearby Machine page and Maintenance Progress page
  • Deadline: 4 July evening

Summary:

  • write code for preferences system on nearby machine page
  • same as above for maintenance progress page
  • edit some front end (HTML) code on maintenance progress: add image background, add ionic icon
  • help my teams for http POST on dispenser report problem page

Report: July 4th Report

5. July 5th Report

  • Title: Session for login page
  • Outcome: Implement session for login system and save session ID and email
  • Deadline: 5 July evening

Summary:

  • looking for the way how to implement session id system in Ionic
  • Session id system like in PHP is server side so it cannot be implement
  • Making the new way using preference to save the login time and email as session id
  • Using comparison of last time and now time to get if the session has timed out or not

Report: July 5th Report

6. July 8th Report

  • Title: Create session id system for login
  • Outcome: System that store ID as session when user login and implement into login page
  • Deadline: 8 July evening

Summary:

  • making new service to create functions that can be called from all pages in project = Preference Manager
  • making new class to store static variable that can be got from all pages directly = Static Variables
  • implement the Preference Manager service and Static Variable class in Home and Login Page to create the session login system
  • the session login system will store the time when login as last_date and email as session_id
  • when access new page or refresh page, there are conditions which make the user going back to login page, consider as timeout, or continue
  • when continue, system will refresh the last_date by store the new value of date

Report: July 8th Report

7. July 9th Report

  • Title: Session login system and service for API
  • Outcome: Implement the session login system in all pages inside project, also change the API called using service
  • Deadline: 9 July evening

Summary:

  • session login system implemented in pages on project
  • when the user reach timed out, doing refresh or going back will prompt to re-login
  • making new service for all dispenser API = Dispenser API
  • now any page use http POST and GET can implement Dispenser API service to get the method and return the value needed

Report: July 9th Report

8. July 10th Report

  • Title: Implement service API to project
  • Outcome: Dispenser API service is implemented in pages needed, no longer to call http POST/GET from the pages
  • Deadline: 10 July evening

Summary:

  • implement the Dispenser API service to pages in my local project
  • merge my project with team partners' project
  • testing and success to run team project after being merged
  • write some documentation in Dispenser API service

Report: July 10th Report

9. July 11th Report

  • Title: Start working on manifest
  • Outcome: Searching material for manifest PWA and create the UI
  • Deadline: 11 July evening

Summary:

  • Documenting on dispenser API service is done
  • Has push the files to master project, in tested by Ian and Thariq
  • Some of the functions has been fixes by integrating from others project
  • Searching learning material of manifest for PWA
  • Discuss with Mr. Johnny for the use of API, some function has been changed
  • Discuss with Ms. Annie to invited into mock up UI project

Report: July 11th Report

10. July 12th Report

  • Title: Manifest fixing and documenting services
  • Outcome: Fixed the problem on manifest json for PWA, document by commenting the services, also classes, code in Github
  • Deadline: 12 July evening

Summary:

  • Manifest for Ionic project cannot be add manually instead must be added via Angular command
  • Fix some code on dispenser API service and testing them
  • Integrating with teams project to my local project

Report: July 12th Report

11. July 15th Report

  • Title: Working together to build app
  • Outcome: Write report about coordination when build PWA in process
  • Deadline: 15 July evening

Summary:

  • Preference manager service now has documentation for use of functions in order to use them with ease.
  • Add deleteValueOnly function into it to replace the value with empty string value instead remove with the key as well.
  • Helping with the report problem page to use ReportProblem and WantToTrack functions in Dispenser API service.
  • Create the login system in Dashboard page when user wants to track dispenser (press the "Star button") or report a problem.

Report: July 15th Report

12. July 16th Report

  • Title: Build app part 1
  • Outcome: Finalize code for login, register, maintenance progress, and nearby dispenser page
  • Deadline: 16 July evening

Summary:

  • Finalize code for authentication pages: Login page and Register page
  • Finalize code for Nearby Dispenser page.
  • Get some API changes from Johnny for maintenance progress problem that needs timestamp for every steps.
  • Maintenance Progress page still in progress because of API changes and new idea to display the data, this will finish tomorrow.

Report: July 16th Report

13. July 17th Report

  • Title: Build app part 2
  • Outcome: Finalize code maintenance progress, integrate with dashboard page, discuss for Repairman PWA
  • Deadline: 17 July evening

Summary:

  • Maintenance progress has steps to display with different time for each of them.
  • Because of more than 4 steps from Ms. Annie design, only 3 steps from time stored in database, we should add more time attributes to database.
  • There should be at least 7 steps of maintenance progress: (start) initial report, client receive, company confirm, repairman fix, repair done, company re-confirm, and client receive report (complete).
  • Further changes will be later discuss between my teams, Mr.Johnny, and Ms. Annie, this also discussing about Repairman App and testing Company Dashboard.
  • Integrate the Dashboard Page to Maintenance Progress with condition if already log in and has report been submitted before.

Report: July 17th Report

14. July 18th Report

  • Title: Build user app part 3
  • Outcome: Fix some bugs found in project and report into HackMD
  • Deadline: 18 July evening

Summary:

  • Mr. Johnny will adjust the database to return 7 different time attributes to use it on Maintenance Progress Page and Repairman App.
  • Bugs found in project for today has already cleared, tomorrow should be tested again to find another bugs.

Report: July 18th Report

15. July 19th Report

  • Title: Build user app part 4
  • Outcome: Start to merge project with others, cleaning debugging code, add some features
  • Deadline: 19 July evening

Summary:

  • Add back component to Login and Register Page, necessary for iOS device which not has back button.
  • Clean up code on Login Page, Register Page, Nearby Dispenser Page, and Maintenance Progress Page.
  • Searching how to get parameter from URL in Ionic using ActivatedRoute.

Report: July 19th Report

16. July 22nd Report

  • Title: Build user app part 5
  • Outcome: Add loading bar as identify wait progress, segment view for multiple maintenance progress, commit to github
  • Deadline: 22 July evening

Summary:

  • Loading screen is use to identify the user that the page is still load some data from API before display them.
  • Making a loading screen in Ionic using Loading Controller, it can be controlled when to start and when to dismiss.
  • To display multiple maintenance progress for same user and same dispenser, using Ionic Slides which make multiple container that using slide/drag to move one to another.
  • For next part before compile with main project, should: (1) implement the loading screen in all pages when loading the data, (2) filter list with time for maintenance progress, (3) estimate completion time in maintenance progress, (4) session logout in dashboard page, (5) maybe login button in dashboard page but this out of main design, and (6) lazy loading for images when loaded from API.

Report: July 22nd Report

17. July 23rd Report

  • Title: Build user app part 6
  • Outcome: Implement loading screen in all pages, finish maintenance progress issues, search and implement lazy loading for images
  • Deadline: 23 July evening

Summary:

  • Implement loading screen with Loading Controller using two function, one to create and display and the other to dismiss/remove it.
  • In order to prevent function to dismiss being called before function to create, using await as asynchronous handler to return Promise so until it being created and displayed it will not run to dismiss/remove it.

Report: July 23rd Report

18. July 24th Report

  • Title: Build user app - final
  • Outcome: Finish all remaining task, giving documentation, clean up code, deploy to domain, and report in HackMD
  • Deadline: 24 July evening

Summary:

  • Dashboard page finalization with add integration to another page, device_id error handling, after login also session login handling.
  • Finalization the other page.
  • Add updateCurrentSession function to all page to update the session time for every action that user's perform.
  • Fix some codes in project and commit to Github.

Report: July 24th Report

19. July 25th Report

  • Title: Import component from User App to Repairman App
  • Outcome: Import important and will be use components from User App to Repairman App, documentation that show what being imported
  • Deadline: 25 July evening

Summary:

  • Dispenser API will have function to login, register, get repairman assignment (next, today, and done), send notification when arrived, send report when repairment has complete.
  • Repairman can register through the app using company email address and will receive verified account notification by the company.
  • Preference manager use to store and get data about session ID, it will store the employee ID and maybe also the email address.
  • The API will be created soon and after that the Repairman App can be writen to send and get data.

Report: July 25th Report

20. July 26th Report

  • Title: Build authentication pages
  • Outcome: Create authentication (login and register) page for repairman app
  • Deadline: 26 July evening

Summary:

  • Using authentication pages in Student App to re use in Repairman app with some changes.
  • Create new theme for UI design on Login and Register Page
  • Authentication system still on going because the API still on work, yet has the same flow.

Report: July 26th Report

21. July 29th Report

  • Title: More feature on User App
  • Outcome: Add feature to show more information on each item in Nearby Dispenser and Maintenance Records page
  • Deadline: 29 July evening

Summary:

  • Nearby Dispenser page now has feature to direct the user to see more information about dispenser nearby.
  • By adding this, user can see each of water temperature and location so the user has choice which dispenser nearby he wants to come over.
  • From Maintenance Records page now every item can be seen the progress has been done in details with timestamps.
  • It will direct the user to Maintenance Progress page which display the user the progress of every record steps ever had.

Report: July 29th Report

22. July 30th Report

  • Title: Start code system on Repairman App
  • Outcome: Create the service API for Repairman App, implement into dashboard page
  • Deadline: 30 July evening

Summary:

  • Listing the API from Mr. Johnny and create service to handle the API for Repairman App.
  • What has to be add furthermore: Authentication API, Report Done for repairman API.
  • On Dashboard page, named Home page, for Repairman App has to receive data from API and create list of all attributes that should be displayed.
  • Using dummy data to perform the design, Dashboard page on Today Mission can listing the mission and each of them can be clicked to get the details.

Report: July 30th Report

23. July 31st Report

  • Title: Modify the dashboard page
  • Outcome: Integrate the Dashboard page so all three fragment pages can dynamic get data from back end code, use dummy data to test
  • Deadline: 31 July evening

Summary:

  • Modify the Home page for Future mission, on "Future" fragment, by get the data from backend code (.ts) and display dynamically on frontend (HTML and SCSS).
  • Using dummy data to perform demo so the design can be displayed as expected.
  • For Home page on Done Mission fragment will be developt and test using dummy data on tomorrow because it has to generate photo (up to 3 images) on each item.

Report: July 31st Report

August Report

Table of Shortcut

This is the table of shortcut for August daily report, if you want to see more details please go here.

Use this to add more: | Nth | Your_target | Not yet | - |
Date
Target
HackMD Report
More Details
1st Design the front page of Dashboard page on Done Mission with integrated data from back end Done Here
2nd 4th Weekly Report
(Professor in present: Prof. Ray)		 Done -
2nd System to parse the JSON object get from API into the format needed for each of three fragments of Home page Done Here
5th Midterm Report
(Professor in present: Prof. Ray and Prof. Riri from Indonesia)		 Done -
5th Shows that the system in home page of repairman page can work properly, testing using MongoDB with dummy data Done Here
6th Testing using MongoDB with dummy data, shows the other page can work properly with data from API Done Here
7th Build the authentication page (login, register, reset account) for Repairman App both front end and back end Done Here
8th Build the authentication page (register, forgot password, reset password) for Repairman App both front end and back end Done Here
12th Build the forgot password and reset password page for user app, add some changes from Ms. Annie Done Here
13th Update the UI for user app on nearby dispenser page, report problem page, and create profile page on repairman app Done Here
14th 5th Weekly Report
(Professor in present: Prof. RT)		 Done -
14th Create profile page on repairman app Done Here
15th Integrate workflow of how the login page route to home page, and route to profile page for log out so back to login page on Repairman app Done Here
16th Giving documentation for repairman app services and classes, add more functions from API to dispenser api service Done Here
19th Use the new API of get done, today, and future missions for Home page, also write the documentation code Done Here
20th Giving all codes in Repairman App comment lines for documentation Done Here
21st 6th Weekly Report
(Professor in present: Prof. Ray)		 Done -
21st Implement the arrived system using the API Done Here
22nd Implement the session system to block repairman access to Home page when no login status and to Auth pages after login Done Here
23rd Finding bugs on Repairman App and fix it soon Done Here

More details for August daily report

This is the details of daily progress, click the report link to see more in HackMD.

Use this to add more:

M. July_August Nth Daily Report

  • Title:
  • Outcome:
  • Deadline:

Summary:

Report:

1. August 1st Report

  • Title: Modify the dashboard page part 2
  • Outcome: Design the front page of Dashboard page on Done Mission with integrated data from back end
  • Deadline: 1 August evening

Summary:

  • Design rework has been implemented Dashboard page on Done Mission section, now all three fragments (Done, Today, and Future mission) has the same theme.
  • Done mission has item to display image from what repairman sent the report images, for this it will generate base64 string which stored in database and convert into image so it can be displayed.
  • In order to display the data from API, must remake the JSON object into the format needed, all three fragments of Home page has their own format.

Report: August 1st Report

2. August 2nd Report

  • Title: Remake data get from API for Home page
  • Outcome: System to parse the JSON object get from API into the format needed for each of three fragments of Home page
  • Deadline: 2 August evening

Summary:

  • Build the system to convert the data from API into three different JSON object format for each fragments in home page.
  • Tested using dummy data but has the same JSON format as when get from the API.
  • Data can be displayed successfully with still missing data because undefined either from the API or no information for this yet.
  • Discuss with Ian and Johnny about repairman app system about how repairman should finish or can't finish the mission, repairman app API needed, and other (can be seen in HackMD report).

Report: August 2nd Report

3. August 5th Report

  • Title: Testing the home page of Repairman
  • Outcome: Shows that the system in home page of repairman page can work properly, testing using MongoDB with dummy data
  • Deadline: 5 August evening

Summary:

  • Testing using the data from the API, change some parameter in the backend code (.ts) because the time component (RepairDoneTime) which is used for determine the timestamp doesn't has value, change using CompleteTime.
  • Testing is done and the result can be displayed although some parameter still missing and Johnny, my mentor, said that he is on progress for creating the authentication database for repairman and the rest of API needed.
  • Has installing Robo3T to access the MongoDB (database) of smart dispenser, guided by Johnny and Thariq because last week Thariq already use this tool to verify the data.

Report: August 5th Report

4. August 6th Report

  • Title: Testing the home page of Repairman part 2
  • Outcome: Testing using MongoDB with dummy data, shows the other page can work properly with data from API
  • Deadline: 6 August evening

Summary:

  • Use the Robo3T to access the database, do the testing Home Page by set some attributes which is the value hasn't set yet.
  • By adding the timestamp on some time uses attributes and Maintainer ID now the data will resemble as the real data in their status, for example the item with status equals to 7 must has all timestamp being set, value in result of repairment, and maintainer information.
  • To modify the database, I must create new data by add the report problem using the User/Student App and modify the value of parameter needed.
  • Result in three parts/fragments of Home Page is successful, three of them can display the data although using the dummy data with self-insert to the database.

Report: August 6th Report

5. August 7th Report

  • Title: Authentication page for Repairman App
  • Outcome: Build the authentication page (login, register, reset account) for Repairman App both front end and back end
  • Deadline: 7 August evening

Summary:

  • To handle the data which get from the dispenser API service, it must has two condition when the data is empty and when is not empty or the data is present.
  • The purpose is to handle the compiler not get error and stop the process so the first condition will not being processed and return null value, in front page also handling if data is null then shows only text instead of list of items.
  • Implement the API from Johnny for authentication pages, they are Login Page, Register Page, Forgot Password Page, and Reset Password Page.
  • Already test using Postman, implement into Dispenser API service, and then implement into Login Page to test the service.
  • Login Page is success, the rest of authentication pages will be worked on next progress.

Report: August 7th Report

6. August 8th Report

  • Title: Authentication page for Repairman App part 2
  • Outcome: Build the authentication page (register, forgot password, reset password) for Repairman App both front end and back end
  • Deadline: 8 August evening

Summary:

  • Register page for Repairman app has already integrated with the API, now it can send the submission of new repairman registration form.
  • Forgot password page for Repairman app has been created, system has been build and can print the return value from Dispenser API service.
  • Same as forgot password page, reset password page also has been created and will print the return value from the service.
  • Furthermore more feature will be added for Authentication pages so it will more user friendly, like adding the alert or error when mistake has been made.

Report: August 8th Report

7. August 12th Report

  • Title: Reset Account on User App and Update for User App
  • Outcome: Build the forgot password and reset password page for user app, add some changes from Ms. Annie
  • Deadline: 12 August evening

Summary:

  • User can use Forgot Password page to reset his account password, this page will generate verification code and send to user mailbox, also it will notify whether verification code is successful sent or not.
  • Along with Reset Password page, user can use this to input email, new password, and the verification code from mailbox, also it will notify whether password reset is success or not.

Report: August 12th Report

8. August 13th Report

  • Title: Update UI for User App and Profile page on Repairman App
  • Outcome: Update the UI for user app on nearby dispenser page, report problem page, and create profile page on repairman app
  • Deadline: 13 August evening

Summary:

  • Update the UI design of nearby dispenser page on User App based on Ms. Annie request, the result can be seen in this report while the mock up or Ms. Annie's design can be seen in previous report (12th August).
  • Update the UI design of report problem page on User App, same as above where it is based on Ms. Annie's request.
  • Profile page for Repairman still in progress

Report: August 13th Report

9. August 14th Report

  • Title: Profile page on Repairman App
  • Outcome: Create profile page on repairman app
  • Deadline: 14 August evening

Summary:

  • Have get information from Mr. Johnny that API for getting the client information, like name, address, and etc., has been created.
  • Profile page UI design for Repairman App has been created with displaying general information of repairman account, also it has access to perform log out from account.

Report: August 14th Report

10. August 15th Report

  • Title: Login to Profile page integration on Repairman app
  • Outcome: Integrate workflow of how the login page route to home page, and route to profile page for log out so back to login page on Repairman app
  • Deadline: 15 August evening

Summary:

  • Add function in dispenser api service to get data from API about repairman information so now we can display the name, email address, id, and the profile picture.
  • Implement the function into profile page so it display the repairman information and home page to display the profile picture as icon on top right corner.
  • Login page store the email address and ID into preference after repairman successfully do login, and it will be erased again once after the repairman do log out in profile page.

Report: August 15th Report

11. August 16th Report

  • Title: Cleaning up Repairman App code
  • Outcome: Giving documentation for repairman app services and classes, add more functions from API to dispenser api service
  • Deadline: 16 August evening

Summary:

  • Update the functions for Login page, Forgot Password page, and Reset Password page in dispenser API service so using either email address or employee ID will using the same function.
  • Add more functions into dispenser api service: 1) to get repairman on going missions, 2) get repairman done missions, 3) post done repairment, and 4) post repairman has arrived.

Report: August 16th Report

12. August 19th Report

  • Title: Cleaning up Repairman App code for Home Page
  • Outcome: Use the new API of get done, today, and future missions for Home page, also write the documentation code
  • Deadline: 19 August evening

Summary:

  • Write the documentation for back end code as comment lines, both as function's header and between lines of code, it can help our team member and next developer to understand easier.
  • Using the new API which Johnny has created for Home page to fetch repairman's currently on going and already done missions, now Home page has update beside using new API also the system code to adjust with the data.
  • Keep continue giving comment lines as documentation on back end code.

Report: August 19th Report

13. August 20th Report

  • Title: Full documentation for Repairman App
  • Outcome: Giving all codes in Repairman App comment lines for documentation
  • Deadline: 20 August evening

Summary:

  • Add documentation with comment lines for Home page, Login page, Register page, Forgot Password page, and Reset Password page.
  • Add REGEX function to handle invalid input on Register page and Reset Password page.

Report: August 20th Report

14. August 21st Report

  • Title: Arrived system on Repairman App
  • Outcome: Implement the arrived system using the API
  • Deadline: 21 August evening

Summary:

  • From today weekly meeting, me and Ian should finish the remaining task before final presentation, also on Friday we should deploy the Repairman App to Johnny domain so it can has online access.
  • Arrived function has been created with using Post Repairman Arrived API, this will update ArriveTime attribute in database also update UI in Repairman App.

Report: August 21st Report

14. August 22nd Report

  • Title: Session system on Repairman App
  • Outcome: Implement the session system to block repairman access to Home page when no login status and to Auth pages after login
  • Deadline: 22 August evening

Summary:

  • Create a service to handle login session, the purpose is to block the access of repairman when the login status (already logged in) is valid/invalid.
  • This service will prevent the repairman to access authentication pages, like login or register, once he has been logged in, and also prevent to access main pages, like Home or Profile page, if he hasn't logged in yet.
  • With using service, every pages in Repairman App only have to call the correct function to prevent the repairman to access wrong pages.

Report: August 22nd Report

15. August 23rd Report

  • Title: Finalization on Repairman App
  • Outcome: Finding bugs on Repairman App and fix it soon
  • Deadline: 23 August evening

Summary:

  • Fixing the filtering data for Future Mission so it can fetch all missions with greater Year, greater Year and Month, and last greater Year, Month, and Date.
  • Import the First Time Preference from User/Student App to Repairman App so when this app was opened from smartphone and create empty string with KEY in Preference Manager using service.
  • Creating preference value and KEY at first time is to handle problem when get data which hasn't be set the KEY from preference will return nothing.
  • Display the Detail modal page when click item in Future mission so the repairman can check earlier what the details of the mission he got.

Report: August 23rd Report

This is the end of the daily report. If you like to see my final presentation you can go here.

End Note

Well, this is it, the end of my internship journey, but it's not end. I will add some bonus after this, like my experience when living in Taiwan, my paper, etc. Basically all of these is one of my responsible when taking the internship so I lazy to add something new hehe. For you who interested in taking this opportunity too, please don't thinking too long or someone will chase it after you. It's very great experience to be part of this internship.

As for you know, you may found some of your friends are smarter than your. Some people can take internship or student exchange to the country you have dream to be there someday. Maybe you have thought like, "Why they can go to there? I can go there too", but in the other side you may found that, "Yeah, he is more than me, he is smarter so he worth to have that than me".

BUT PLEASE, NO!

I have ever have this thinking too and, as for you know, maybe, I'm the lowest of all my friends who taking this program. If you have ever think like me then congratulation we are in the bottom of people who not grateful of what we have. We are all the same, we taking the same program and we will finish this together. I don't want to think again that I'm the lowest, or I'm just lucky to be here. Just because other than you are get more money or talking smarter than you, it won't make us lower than them.

Here is the point, you can get this program then you have been increase your position from they who can't get this opportunity. How can be this doesn't make you happy, right? Another one, you may see someone who are very smart, or very clever, or very know how to get scholarship and go abroad here and there, right now your position is "wanna be like him" but for what? Making you become like him doesn't making you become someone you know for the entire your life. Your life has you own way, you may seem worry to see someone chasing you or someone after you, but when you see their track, it's different than yours. You can make someone as example but you can't ever do copycat.

If something has bothering you because you see the sky is too high for you then please see the ground that you still stand on it. Chasing the sky is challenging but everyone out there also know where to stand. This is just my advice so you can follow it, or throw it. Me also not a smart guy, not a good student, but I will to learn how to see this life as something worth for me. Let's try to be someone who more grateful to this life, never give up to chase and seek the hope we want, and build more connection to people we have met.

tags: intern
Last changed by 
 
Muhamad Aldy B.
Student of Universitas Indonesia, batch 2016.
0
396

Read more

NTUST 2019 Internship - My Progress Report

Jan 11, 2020
Read more from Muhamad Aldy B.
Published on HackMD