> ## Content Index
> Fetch the complete content index at: https://www.waterboy.tech/llms.txt
> Use this file to discover other available public pages before exploring further.

# Fixing the tracker
- URL: https://www.waterboy.tech/fixing-the-tracker/
- Published: 2026-09-21T16:21:28.000Z
- Updated: 2026-09-22T14:43:59.000Z
- Author: waterboy
- Tags: QA Monk

Today Claudius Maximus told me that there were some issues with the tracker.

Issues with session management. 

Who even asked for session management, mate?

I am realising the easiest way to solve problems is to first look at why we are doing it in the first place. 

Most complexity will eventually breed retardation.

In this case I just went line by line and asked it why it was doing what it was doing.

I guess im just lazy most times and never do this.

If I dont know of the bad code, it must not exist lol.

Its also important not to be too worried about bad code.

You will never know what the best solution to get from A to B is. 

The best solution to get from A to B is relative to how get from B to C to D

You cant think that far ahead in the first use case or feature set. 

Once you solve multiple problems, you will automatically see areas to refactor. 

Anyways back to the tracker...

This is essentially the most important element.

All other steps come from this. 

Here is the code.

[trackertracker.js3 KBdownload-circle](https://www.waterboy.tech/content/files/2026/09/tracker-1.js "Download")

I deployed it live and saw some events. 

Now, tomorrow I will make the agent do a proper run-through of all cases to create more events.

Let's see.