I'm putting more effort in WW Extension project

Why I decided to work more on the extension

After finishing V03 of my Waterloo Works Extension, I thought myself “That is enough. It is usable product and that is fine for this project”. And look for some other project to work on.

Even it is Study term and co-op application season, I don’t know why but I feel more desire in monetizing product.

I think that is because I’m learning the value of money.

Few years ago, money was just something that is better to save for me. there wasn’t any passive spending or active earning.

However, by experiencing the real job, Military, I learned the concept of Earning money. Also, by experiencing Living abroad, I learned the concept of Passive spending. there is cost that exist to survive.

and those made me dream about Passive Income.

Therefore, I looked for a project that can be monetized.

I was thinking about whole new project that can bring passive income, but it wasn’t easy to think of it.

But there was one easy option. which is using old project.

Waterloo Works Extension was perfect source for it. becuase I used it usefully, and my brother used it usefully. I’m pretty sure others will too.

Software that does things for me always works (I guess).

There were more reasons I choose this project but in large scope, that’s why I decided to work on this project more.

How I’m gonna extend this extension?

well, to monetize something, you need to do three things. make product, find customer, and get paid.

I do have a product, but not a payment system. so I started with that.

Adding user account system (for tracking who paid and who didn’t), Paid credit system (for enable paid people to use our product) is the first thing I’m doing.

There were some several concerns about this Project since it is highly depends on Waterloo Works website. and some infos I’m using are really critical such as address and phone #.

But that doesn’t stop me.

Anything Special with previous projects?

As I said, I’m managing all documents in html in this project.

And by upgrading this project to small business level, I restructed whole architecture of the project.

I let claude code to research about efficient and productive documentation architecture, and applied that structure to my project.

The key point of the structure is ADR(Architectural Decision Record).

This is like adding rules that stack but in architecture-wise.

I just start using this architecture, so I need to see the progress before evaluate its productivity.

For now, All I can say is it was much better than my previous “Plan, Implementation, history stucture”.

I can say that was one of the worst structure of vibe coding. Agent kept loss track, and not following rules.

Anyway, new strucure seems more regulated, efficient and straight forward.