Zie_Mordecai

I built this open-source framework to solve a structural problem in payment acquiring: rate-slashing to fight merchant churn is a losing game, and legacy aggregate reporting completely misses sub-hourly terminal dropoffs.

For far too long, small businesses in our community have been struggling to get decent foot traffic to survive. I propose we look at their dead hours and interject high-intent customers. I wrote an article that explain my solution a little better: https://damariushayes.substack.com/p/the-velocity-multiplier...

I'd love your feedback on my solution, thanks!

Curious, have you thought of utilizing your tool within performance diagnostic testing?

I like how you put a new spin on an old problem. To get agents to choose your business, you must first get your ducks in a row with your SEO.

Hmm, I am curious what other datasets you see yourself working with to bring out the best experience for the user?

Hey, dope concept, after looking at it, first thing that came to mind was legacy systems and wrangling with business logic underneath.

This is good. Have you sent this to non-profits or local community leaders who have this on their docket? The data will give more context and awareness to the citizens they are working with.

Curious, have you thought about writing articles about the things that you are concerned with?

I agree with your statement. I'll leave with this: slop was there before AI got on the scene. We're discussing work culture, where the bare minimum is the way to the top, and the organization hires and allows that level of work. AI is just masking our own issues within a organization.

Ahh, yes, the talk of the time. I will keep this short, yes what if it does replace software engineers? Then what? There was a time when we had no software engineers or even webmasters, those who are old enough to remember that term. We don't know what we don't know, yet we can assume that our skills are transferable and can differentiate into new roles. In the last few months, I even questioned whether software engineers should be utilized in certain roles like legacy systems integrations, which led me to come up with a new role, software archaeologists, more suitable and with the proper skillset to align with the problem. Here are some of my findings within this post: https://thevelocitymultiplier.substack.com/p/stop-paying-dow...

I think we need to have an open mind for two things: Are we caught up more in the title or the work that needs to be done, and do I have the capacity to re-imagine how my skills can differentiate into new roles?

Really great idea, simple yet effective.