Micheal Shallop 🐧Even tho I retired years ago, #ai kind of got me restarted coding using pair programming and I've been working on this project as an "excuse" to learn #rust - because when I first started, all languages were compiled and rust bellowed at my inner 🦖 to wake up so I created rustyBeds:
I used a PHP project I worked on the last ten or so years prior to retirement that was a non-generic back-end data-processing system built around #amqp scaffolding
It went into production on a couple of iterations, with one hitting 952 days of uptime w/out a reboot or restart 💪
But the project, as it was, isn't good enough...
Working with #AI, various AIs, I finally started talking to Github CoPilot and we finally found a purpose for this project
of course, lots of refactoring and modernizing, but AI walked me through the proposed changes and I signed-off
All this is reflected in the project wiki
#amqp is still the binding fabric but we've shattered the previous exchange and queue bindings, eliminating #bi-focused consumers, and in doing so have increased our throughput exponentially 🎆
I hopefully expect to whitepaper and demo by showing that, with a configuration file properly constructed, (implying: no changes to source), we can deploy a back-end data infrastructure compatible with a twitter-like messaging service and that processing is schema agnostic 🙊
I would expect github copilot to be the superior coding paired programming AI considering the corpus of code microsoft glutted, acquired, to train it on so no surprises
But, please note the "still requires adult supervision" part... 🙏
tl;dr: this entire project is just an exercise - how quickly can a senior dev port an existing PHP project to Rust, a previously unknown language, using pair programming