Hyoseo Lee
Home About Projects Blog Thinking
dev-log

my new project: waterloo works extension

Topic ww-extension
Area side-projects
Summary
Introducing ww-extension, a new Chrome extension that uses AI to automate WaterlooWorks job triage, and a reflection on shutting down the unfinished Macro-dashboard project to focus on this new tool.

My new project

As the new term starts, Waterloo Works has opened and I had to spend time on it. And if you know how it feels to spend time on it, you will feel sad about me.

And I thought, it can be really a simple job for ai agents. what I do is literally reading through job details and figure out do I fit or not.

for example, if job requires French speaking, but I cannot speak French, that job is not for me. Also, If job wants someone who have experience of AWS, and I do have experience of AWS, yay. that job is for me.

So basically it is just comparing my spec and job’s spec and find what is good.

you know for coop, you need to apply more than hundreds of applications. normally what people do here is putting that much effort, or skipping that process, just applying based on the job title.

Therefore, I thought AI can do good here, so I decided to make a ai tool for that.

more details about the project.

To add some information about project, I decided to make a chrome extension for it.

actually there were several options, which is just a web app, chrome extension, AI prompt, and more.

I choose the chrome extension just because it has access to the website I’m looking at.

well, there might way to export the contents of waterloo works, but they seemed pretty complex and not familiar. there were three ways I know to a software access the content of waterloo works.

First is using some scraper or api. I searched a little bit, but I didn’t satisfied with the findings.

Second is copy and pasting all the job posts by myself and give it to ai as a file.

Third is the chrome extension, who can read the html of the page I’m looking at.

Since waterloo works requires authorization to view the job postings, first method seemed really uncomfortable. and for the second method? what is the meaning of that if I have to click the link, copy the content, paste it to some file by myself for each of hundreds of job posts.

Therefore, actually the Third option was kind of only option to me. there might be better way but for get about it.

and I thought it is possible that the extension can click on the page like me, and do something useful.

plans

Anyway, I don’t think this project will be a huge project. with help of Claude code, I might build this app within a week, or a day.

all I need is basically more daily limit.

Also, another good thing here is that I have experience of creating a chrome extension and deploy it.

on the Orbt! mini game extension, I really believe it was successful project. actaully, I have 31 users currently have my extension on their browser all over the world. I’m not sure why they play my game

And I know that it is super easy to deploy, without cost.

I can share it to people around me who need these tools like me.

Creating some software I really need is actually fun and I love that.

but your last project?

well, it is shamed to say it but I kind of abandoned my last project. the Macro-dashboard.

I know I have to work on it, and make it profitable, (I have list of todos about the project) but I don’t spend time on it.

And I’m still paying for the api, server and everything.

what I’m thinking is stop this unfinished project and work on something I really think it is good.

I’ll work on this project first and then think about it’s destiny.