This was quite straightforward to code ’manually’, but we got stuck for some hours when trying to send the first message.
CPU topped, fans spinning, no message through. Analyzed, and after a while when we got same block the nth time, someone proposed Claude.
So Claude got the repo, prompted Claude:
”You got one job, why isn’t message through and why CPU usage high?”
He didn’t solve it. Probably could have if we kept Clauding.
But we found the problem. The issue was that the code was hitting the terminal 300 times trying to send the message :)
For clarity reasons Claude got the job to write the README, personally I don’t like that approach, but we got many other projects so time management basically.
We are building Cobolsky too.
Right now we are building the part to get images through using Apples old algo. Will be 576x720 using the Föoyd-Steinberg dither, 1984 Apple algorithm :)
We had to rewrite the main system so those who are not into code and tech much could run it more easily. They are used to MarineTraffic and VesselFinder web sites.
This is tailor made for them, check loitering, export CSV.
Main system is no secret, but it got loads of ML and frontend is a bit messy. But one day we will ship it too.
If you check the link to GUR War and Sanctions web site in the README, they got a map where they plot harbors and similar.
The main Shadow Fleet Tracker does next port prediction and handles flag change.
We’ll sort mire user-friendly frontend and onboarding for the main version in future. Then people can use it as they need.
Thanks for all the feedback folks! Will try to reply a few times a day here. And post some more blog articles.
This was quite straightforward to code ’manually’, but we got stuck for some hours when trying to send the first message. CPU topped, fans spinning, no message through. Analyzed, and after a while when we got same block the nth time, someone proposed Claude.
So Claude got the repo, prompted Claude:
”You got one job, why isn’t message through and why CPU usage high?”
He didn’t solve it. Probably could have if we kept Clauding.
But we found the problem. The issue was that the code was hitting the terminal 300 times trying to send the message :)
For clarity reasons Claude got the job to write the README, personally I don’t like that approach, but we got many other projects so time management basically.
We are building Cobolsky too.
Right now we are building the part to get images through using Apples old algo. Will be 576x720 using the Föoyd-Steinberg dither, 1984 Apple algorithm :)