Project: Paidlancers

Paidlancers is a desktop app designed to help freelancers streamline their event management tasks. It is the brainchild me and my team, who wanted to simplify and automate the administrative side of freelancing.

The app is optimized for use through a Command Line Interface (CLI) while still having the benefits of a Graphical User Interface (GUI). Some of its features include adding and linking contacts to events, tracking rates, marking events as done, creating new events, viewing event lists and revenue, and more.

By centralizing all event-related information and tasks in one place, Paidlancers aims to increase productivity and help freelancers focus on their craft.

Given below are my contributions to the project.

  • New Feature:​

    • Link Contact Added ability to link contacts to events. (Pull Request #88)
      • What it does: Allows the user to link contacts to events.
      • Justification: This feature improves the product significantly because a user can keep track of all the contacts they have and link them to events. This is useful for users who want to keep track of all their contacts and link them to events.
      • Highlights: This enhancement affects existing commands and commands to be added in the future. It required an in-depth analysis of design alternatives. The implementation too was challenging as it required changes to existing commands and the creation of new ones.

  • Code contributed: RepoSense link

  • Project management:

    • Managed release of v1.2.1 on GitHub. (Pull Request #135) (Release v1.2.1).
    • Setup CI and codecov (Pull Request #52).
    • Smoke tested JAR trial release on Windows Operating System (Issue #36).

  • Enhancements to existing features:

    • Enhanced the comparisons of event class (Pull Request #86).
      • What it does: Enhanced comparison of events to account for different cases.
      • Justification: An event with the same name but of a different timing should not be equal to each other. Reason being that the same event can happen twice, both at different timings.

  • Documentation:

    • User Guide:
      • Added introduction section to the user guide (Pull Request #127).
      • Restructured the presentation of the user guide for clarity (Pull Request #127, #244).
      • Added logo to the user guide (Pull Request #127).
      • Added section on how to use the user guide (Pull Request #127).
      • Enhanced first-time-user story (Pull Request #142).
      • Added additional command guides and examples (Pull Request #151).
      • Sorted UG and added callouts (Pull Request #165, #177, #242).
      • Improved overall friendliness of User Guide (Pull Request #245).
    • Developer Guide:
      • Added implementation details of the linkcontact feature (Pull Request #137).
      • Added Activity Diagram for linkcontact feature (Pull Request #170).

  • Community: