Great stuff! I am wondering if you can give me an example of how this works because for some reason I get confused on "software health trend monitoring solution aimed at legacy systems". Maybe I am overthinking it though.
20+ years of coding experience across video games, logistics, finance, real estate, and legal/law industries. I'm a versatile, abstract-thinking solver of problems across many domains and disciplines
I'll break down what you quoted in hopefully better words.
My API sits in the cloud and essentially pings another GET endpoint every X minutes. The resulting response plus a couple extra metrics are recorded. This is the "software health monitoring" part. The "trend" part comes in after a bunch of responses have been recorded. Using any data visualization tech, user's can see the trends of the monitored system over time.
It's "aimed at legacy systems" or old systems because that's what I built it for and there's no integration or changes needed on the system being monitored. Alterations could help, but typically aren't required. This is assuming the software being monitored has at least a single GET endpoint that my system can reach from the cloud.
Does that make sense? Is there anything else I can word differently or clarify? I just assume there are things I say that don't make much sense and hope for questions. 😅
That would makes sense if you are doing a GET request. I think I am more confused on what data it contains when you mention "trends of the monitored system over time.". Just a high level understanding is where I am stuck on pretty much I believe. Though, explanation makes sense overall :)
20+ years of coding experience across video games, logistics, finance, real estate, and legal/law industries. I'm a versatile, abstract-thinking solver of problems across many domains and disciplines
Right. Of course I left that part out! 😅
The metrics that get recorded from every watch/ping response are
datetime (UTC) of request
status code
total response time (in ms)
the first 64 characters of each response body
My dashboard plots the response times on the graph and shows the status code locations within the data (like the bottom watch in the screenshot/post image).
Yep! I actually have to take the time to think about it for couple of days and for some reason it just clicked (I read it closely and just had to marinate it a bit). Not sure why it was so hard. Thanks for the explanation!
20+ years of coding experience across video games, logistics, finance, real estate, and legal/law industries. I'm a versatile, abstract-thinking solver of problems across many domains and disciplines
I’ve developed a demo version of a file‑syncing software that connects two PCs through a secure, one‑time 6‑digit pairing code. Once paired, each PC designates a folder for synchronization. Any file dropped into the shared folder on one machine is automatically mirrored to the paired folder on the other.
The system uses peer‑to‑peer transfer when both devices are online for fast, direct syncing. If either device goes offline, files are temporarily stored in a database. Once the offline device reconnects, it automatically fetches the pending files from the database, ensuring no data is lost. Synchronization is fully bidirectional, keeping both folders up to date.
20+ years of coding experience across video games, logistics, finance, real estate, and legal/law industries. I'm a versatile, abstract-thinking solver of problems across many domains and disciplines
Oh, that sounds cool! I've never built a file sharing anything like that before. I like the pairing code for a bit of security. What did you build that for?
Have you made a post on what you've built? I'm curious to hear more of the technical bits and the "whys" behind it all.
ebSync – Backstory & Vision
The idea for ebSync came from a simple but frustrating experience. One evening, I made some code changes on my PC before dinner. Later that night, I felt the urge to continue building, so I opened Claude and downloaded the file again—only to realize that the changes I had made earlier weren’t there. That’s when I thought: What if there were an app that automatically synced files between devices, regardless of whether the other device was online or not?
That spark led to ebSync.
How ebSync Works
You connect two devices by entering the same pair code on both.
Once connected, you assign a shared folder.
From that point forward, any file added to the shared folder on one device is automatically synced to the shared folder on the other device.
Initially, I built this using WebRTC peer-to-peer connections, with Supabase as a fallback for file transfers. I’m now exploring a shift toward direct TCP transfer architecture for greater efficiency and reliability.
Current Development
I’m iterating quickly to refine the product-market fit and uncover real-world use cases. One of the most exciting features I’m working on now is intelligent file organization:
Files are automatically tagged, summarized, and categorized into newly generated folders.
This means you no longer have to dig through endless chat threads or cluttered mobile storage to find a document.
Even if you don’t remember the exact filename, you can simply search for something like “Payment to John” and ebSync will surface the right PDF instantly.
The Goal
The vision is to make file syncing and retrieval effortless—not just keeping your devices in sync, but also making your files discoverable and meaningful. + to earn lot of money.
20+ years of coding experience across video games, logistics, finance, real estate, and legal/law industries. I'm a versatile, abstract-thinking solver of problems across many domains and disciplines
Oh, that's interesting. It sounds like a sort of "smart cloud". Where is your Supabase stored/running? I've heard of it, but never used it. How's the market-fit part going?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great stuff! I am wondering if you can give me an example of how this works because for some reason I get confused on "software health trend monitoring solution aimed at legacy systems". Maybe I am overthinking it though.
Great work!!
Absolutely! I know, it's a bit of a word salad. 😅
I'll break down what you quoted in hopefully better words.
My API sits in the cloud and essentially pings another GET endpoint every X minutes. The resulting response plus a couple extra metrics are recorded. This is the "software health monitoring" part. The "trend" part comes in after a bunch of responses have been recorded. Using any data visualization tech, user's can see the trends of the monitored system over time.
It's "aimed at legacy systems" or old systems because that's what I built it for and there's no integration or changes needed on the system being monitored. Alterations could help, but typically aren't required. This is assuming the software being monitored has at least a single GET endpoint that my system can reach from the cloud.
Does that make sense? Is there anything else I can word differently or clarify? I just assume there are things I say that don't make much sense and hope for questions. 😅
That would makes sense if you are doing a GET request. I think I am more confused on what data it contains when you mention "trends of the monitored system over time.". Just a high level understanding is where I am stuck on pretty much I believe. Though, explanation makes sense overall :)
Right. Of course I left that part out! 😅
The metrics that get recorded from every watch/ping response are
My dashboard plots the response times on the graph and shows the status code locations within the data (like the bottom watch in the screenshot/post image).
Does that make sense?
Yep! I actually have to take the time to think about it for couple of days and for some reason it just clicked (I read it closely and just had to marinate it a bit). Not sure why it was so hard. Thanks for the explanation!
Awesome, glad I could clarify things!
FWIW, I frequently step away and let things simmer/marinate in the back of my mind. 🙂
I’ve developed a demo version of a file‑syncing software that connects two PCs through a secure, one‑time 6‑digit pairing code. Once paired, each PC designates a folder for synchronization. Any file dropped into the shared folder on one machine is automatically mirrored to the paired folder on the other.
The system uses peer‑to‑peer transfer when both devices are online for fast, direct syncing. If either device goes offline, files are temporarily stored in a database. Once the offline device reconnects, it automatically fetches the pending files from the database, ensuring no data is lost. Synchronization is fully bidirectional, keeping both folders up to date.
I would really love to hear your review on this.
Oh, that sounds cool! I've never built a file sharing anything like that before. I like the pairing code for a bit of security. What did you build that for?
Have you made a post on what you've built? I'm curious to hear more of the technical bits and the "whys" behind it all.
ebSync – Backstory & Vision
The idea for ebSync came from a simple but frustrating experience. One evening, I made some code changes on my PC before dinner. Later that night, I felt the urge to continue building, so I opened Claude and downloaded the file again—only to realize that the changes I had made earlier weren’t there. That’s when I thought: What if there were an app that automatically synced files between devices, regardless of whether the other device was online or not?
That spark led to ebSync.
How ebSync Works
You connect two devices by entering the same pair code on both.
Once connected, you assign a shared folder.
From that point forward, any file added to the shared folder on one device is automatically synced to the shared folder on the other device.
Initially, I built this using WebRTC peer-to-peer connections, with Supabase as a fallback for file transfers. I’m now exploring a shift toward direct TCP transfer architecture for greater efficiency and reliability.
Current Development
I’m iterating quickly to refine the product-market fit and uncover real-world use cases. One of the most exciting features I’m working on now is intelligent file organization:
Files are automatically tagged, summarized, and categorized into newly generated folders.
This means you no longer have to dig through endless chat threads or cluttered mobile storage to find a document.
Even if you don’t remember the exact filename, you can simply search for something like “Payment to John” and ebSync will surface the right PDF instantly.
The Goal
The vision is to make file syncing and retrieval effortless—not just keeping your devices in sync, but also making your files discoverable and meaningful. + to earn lot of money.
*The whole code is written by Claude
Oh, that's interesting. It sounds like a sort of "smart cloud". Where is your Supabase stored/running? I've heard of it, but never used it. How's the market-fit part going?