Walter Jenkins

this can wait for tomorrow...

[Nextjs / Supabase example](https://github.com/vercel/nextjs-subscription-payments/blob/main/pages/api/create-checkout-session.ts)

Up until today I have focused on the “elephant”. Taking one bite out at a time. This is the big part of the project that I knew was an industry problem. Dealing with realtime performance data. This is important because it will help me stand out in a working and strong existing market. The pledge was to undercut competition by building some that is “good enough” but better than what 90% has from in house development.

Based on feedback that I have gotten from potential clients there are some missing elements that I needed to work on. Some easier than others. By focusing on design and workflow. I am building something that is simple to build and use by 90% of the users who are not technical.

The idea behind this is that the value additive to my product is that more than analysts will be able to use this. Creating a network effect within a small community.

The main thing that I have heard from people is that they have a hard time communicating and that they are all on different platforms to do the same thing.

My goal is to get low hanging fruit by building features to expand the footprint of the potential network within the organization’s. 😎

woke up this morning to pm2 (an excellent monitor for node) emailing me telling me that I messed up.

Apparently a I pushed the update to my worker. I was unaware of 2 things:
- my server was running Node 14
- replaceAll() was added at Node 15

Steps to solve:
- install node 16 with NVM on DigitalOcean Droplet
- switch to to node 16 on server
- move on with my day

estimated outage: 12 hours

EDIT:
you need to specify the version. for whatever reason it is defaulting to 14.

`pm2 start app.js --interpreter=/root/.nvm/versions/node/v16.16.0/bin/node`

When I first started this project the idea was "simple". Get a historical log and charts for my local transit agency of their on time performance. I knew that I eventually wanted to scale up and out, but going with the quick win I opted for setting up ENV variables for the agency.

I have been focusing a lot on my database as of late and am making it a goal for the next week to get up to 3 transit agencies working on the platform with the current MVP to broaden my likely beta users.

As of right now, the users can have conversations, inspect historical information, and view realtime vehicle locations.

Each user has an "agency". Each agency has a set of parameters that control the data that they query, the comments that they see and what the map looks like. ATM I have migrated the first agency full onto this new model and will work on the 2nd agency tomorrow.

Other than that, this is the farthest that I have gotten. Its taken me 2 years and 4 pivots to get to this point, but I am finally seeing the road... I am getting more interested parties and I'm not embarased to talk about it to people anymore.

Current Stack:
- NextJS / Tailwind / Redux > Frontent
- NodeJS worker / S3 / Athena > Big Data Queries
- Supabase

This weeks goals:
- Start backing up 3rd agency
- Setup agencies on platform under different users
- Updated prospective agencies about potential partnership
- Update mailing list on direction
- 1 blog post
- Migrate to new site
- Bus Stop Issue workflow