Introduction
Hey everyone! Today I'm sharing the story, insights, and a bit of venting (XD) behind my recent project, GPE Helper.
Just like my previous post on Fake-phone-screen, I'll start with the motivation and features, then wrap up with some development takeaways.
The Origin
To graduate with a Master's degree at NYCU, students need to pass a programming proficiency exam, such as the nationwide CPE or the GPE exam hosted by the department.
There are various ways to meet this requirement, and the threshold depends on the exam difficulty (e.g., 3+ problems for CPE, 240 points for GPE). You can check the department's website for specific graduation requirements.
You can refer to the GPE Facebook page here: [https://www.facebook.com/nctupe]
My undergraduate department had a similar requirement, but I satisfied it back then via the ITSA Laurel Contest. However, it seems NYCU doesn't recognize that competition, so I had to take the GPE for my Master's (CPE sessions are limited, so many people opt for the department's GPE).
Competitive programming gets rusty if you don't touch it for a while, and the GPE exam can be quite... subtle.
Everyone has a different take on competitive programming, so I won't dive too deep, but personally, I'm not a huge fan of it XD.
Anyway, the main issues I found were:
- Outdated problem sets and excessive, useless English descriptions.Sometimes I really can't tell if the problem setter is testing my coding skills or my English.
Combined with the occasional poorly written problem, it's just a proficiency exam, I really...🥴 - The GPE practice system lacks data integration and is slow.I don't blame the system itself; it's been around for years, but the UI/UX is lacking. Things like viewing past problems, categorization, and page refreshes after judging are quite inconvenient for those trying to practice.
Complaining aside, some things are just out of our control—technical debt and legacy systems are tough. Since I couldn't change the status quo, I decided to build my own solution.🙂
Purpose & Goals
Purpose
To help myself practice for the GPE efficiently and pass the graduation requirement at NYCU.
Goal
Create a clean, responsive web interface that uses scraped data to provide a better practice experience for users.
Introducing GPE Helper
🚑 GPE Helper — Saving you and me from programming proficiency exams.
Made 💖 with
- ReactJS
- UI: Semantic UI React
- Python
- Beautiful Soup Crawler
- Integration of
- NYCU Programming Proficiency System https://gpe3.acm-icpc.tw
- Zero Judge High School Programming Contest System https://zerojudge.tw/
Features
- Overview of all exams from 2018 to present.
- List of all problems from 2019 to present.
- Search functionality.
- Sorting by AC rate, OnSite frequency, access count, etc.
- "Favorites" list.
- A completely subjective "Problem Recommendation Score."
- Problem Categorization.
Demo

Thoughts on Passing GPE
You can check out my other post about my GPE exam experience.

Development Takeaways
Frontend
I focused on a clean design. Most of my time was spent handling data and table rendering. Because the data structure was slightly complex, I experimented more with React Hooks.
Compared to my previous project, Fake-phone-screen, I learned much more about combining Hooks and Reducers. I aimed for a clean, organized, and bright interface using the UI framework.
About Semantic-UI
Semantic UI React is a framework I've used for a long time. I love its component design, but I ran into a few issues:
- Overriding the default color scheme is quite tedious.
- The
Semantic UI Reactdocumentation mostly uses class-based components. Trying to stick to pure React Hooks required extra effort, and I encountered some weird bugs during table sorting. - The update frequency of Semantic UI is a bit slow, which makes me slightly nervous QQ.
Favorites
Since there's no backend, I implemented this using browser local storage. The downside is that records are cleared if you switch devices, but at least you can track problems directly on the site now.🥰
Unimplemented Ideas
- Random Problem Generator
One-click Template DownloadI actually implemented this in a script called genTemplate.py, but it should really be on the frontend. The goal is shown in the image below:

It's mainly for easier Git tracking. If it were on the frontend, it would be more flexible—allowing users to select their preferred language (.c, .cpp, .java, .py) and customize their own comment headers.
/*
Problem: {problem_name}, ACs: {problem_acs}
Link: {problem_link}
*/
It would be super convenient, but I ran out of time.orz
Nav- Github Repo Info
I saw this in Material Design and thought it looked great, so I ported it over. It fetches public GitHub user data and displays it. It was a fun little feature to build!XD

Crawler
Data Acquisition
Since this is an integration site, I decided to rely on the original GPE site for the judge system. I use a scheduled crawler to update data, which also reduces the load on the original site.
Embedding?
I initially tried to embed the GPE site directly, but since it's restricted to the campus network and modern browsers have strict security policies regarding iframes, I decided against it. :3
Problem Categories
I realized after designing the database that we need categories (e.g., GCD, DP, Tree) for efficient practice. Since the school's GPE site doesn't provide this, I wrote a crawler for Zero Judge to supplement the data.

Since these categories are often tagged by community members, some problems might not have them if they aren't on Zero Judge. That's a bit of a shame.
Recommendation Score
This is a bit of a "random" calculation, but I wanted a cool star-rating system. I used a weighted average of AC rates and historical frequency. It's just for reference—a proper algorithm would be better!QQ
Conclusion
That was a lot to write! I hope this helps everyone trying to pass the graduation requirement. If you find this project interesting or helpful, feel free to give it a ⭐ on GitHub!
Feel free to leave a comment if you have any questions.
Thanks for reading, and see you in the next post! :)