wilsonwid / ip

Hello there, nice to meet you! I'm Wilson! 👋

I'm currently a final-year student taking a double degree in Data Science and Analytics (DSA) and Computer Science (CS) at the National University of Singapore (NUS).

Please feel free to reach out through the clickable links below! I'm currently interested in quantitative research/trading, machine learning, or data analytics/science opportunities located in Singapore.

📖 Currently reading:

🏫 Academic reading(s):

• Mathematics of Machine Learning (by Deisenroth, Faisal, and Ong)
• Natural Language Processing with Transformers (by Tunstall, Werra, and Wolf)

🧩 Casual reading(s):

• Range: How Generalists Triumph in a Specialized World (by David Epstein)
• The Daily Stoic (by Ryan Holiday and Stephen Hanselman)

💻 Languages/Technologies:

📱 Contacts/Profiles

Reach out to me via the platforms below! My resume is available on request or on my personal website.

👨‍💻 GitHub/Coding Statistics

📊 Contribution Timeline

✍️ Acknowledgement(s)

• Profile picture by @piermanuele_sberni on Unsplash.
• Inspiration for this README from Lee Pak Shuang and Russell Saerang. Do check out their GitHub profiles for more awesome and cool stuff!
• GitHub README stats from anuraghazra and ashutosh00710

ip's Issues

Sharing iP code quality feedback [for @wilsonwid] - Round 2

@wilsonwid We did an automated analysis of your code to detect potential areas to improve the code quality. The script did not detect any issues in your code (nice!).

IMPORTANT: Note that the script looked for just a few easy-to-detect problems only i.e., there can be other areas/places to improve.

Aspect: Tab Usage

No easy-to-detect issues 👍

Aspect: Naming boolean variables/methods

No easy-to-detect issues 👍

Aspect: Brace Style

No easy-to-detect issues 👍

Aspect: Package Name Style

No easy-to-detect issues 👍

Aspect: Class Name Style

No easy-to-detect issues 👍

Aspect: Dead Code

No easy-to-detect issues 👍

Aspect: Method Length

No easy-to-detect issues 👍

Aspect: Class size

No easy-to-detect issues 👍

Aspect: Header Comments

No easy-to-detect issues 👍

Aspect: Recent Git Commit Message

No easy-to-detect issues 👍

Aspect: Binary files in repo

No easy-to-detect issues 👍

---

ℹ️ The bot account used to post this issue is un-manned. Do not reply to this post (as those replies will not be read). Instead, contact [email protected] if you want to follow up on this post.

Sharing iP code quality feedback [for @wilsonwid]

@wilsonwid We did an automated analysis of your code to detect potential areas to improve the code quality. We are sharing the results below, to help you improve the iP code further.

IMPORTANT: Note that the script looked for just a few easy-to-detect problems only, and at-most three example are given i.e., there can be other areas/places to improve.

Aspect: Tab Usage

No easy-to-detect issues 👍

Aspect: Naming boolean variables/methods

Example from src/main/java/talkingbot/util/Ui.java lines 26-26:

    private boolean continueIter = true;

Suggestion: Follow the given naming convention for boolean variables/methods (e.g., use a boolean-sounding prefix).You may ignore the above if you think the name already follows the convention (the script can report false positives in some cases)

Aspect: Brace Style

No easy-to-detect issues 👍

Aspect: Package Name Style

No easy-to-detect issues 👍

Aspect: Class Name Style

No easy-to-detect issues 👍

Aspect: Dead Code

No easy-to-detect issues 👍

Aspect: Method Length

No easy-to-detect issues 👍

Aspect: Class size

No easy-to-detect issues 👍

Aspect: Header Comments

Example from src/main/java/talkingbot/Launcher.java lines 9-12:

    /**
     * Main method for the whole application.
     * @param args Arguments to be passed.
     */

Suggestion: Ensure method/class header comments follow the format specified in the coding standard, in particular, the phrasing of the overview statement.

Aspect: Recent Git Commit Message

No easy-to-detect issues 👍

Aspect: Binary files in repo

No easy-to-detect issues 👍

---

ℹ️ The bot account used to post this issue is un-manned. Do not reply to this post (as those replies will not be read). Instead, contact [email protected] if you want to follow up on this post.