I used to compete in esports with Team Liquid & Cloud9.
Now I build software and AI tools, mostly by breaking things first and figuring them out second.
No real plan, just a lot of testing, iterating, and occasionally wondering why something stopped working.
Git and side-projects coming soon
Despite my Ex Wife’s attempts to drag the process ad infinitum, I found a way to bifurcate my married status, with the judges blessing, effective immediately. 😎
Never give up no matter what they throw at you. Stay true to your goals and keep pressing forward 🤙
Try it yourself (no setup, no signups, no API keys):
git clone https://t.co/om31YC8K39
cd loopforge
pip install numpy
python run_demo.py
You'll watch it test four versions of a function, drop the two that break it, and keep the fast one that still works.
My "find people nearby" function was way too slow in a proximity based social app side project I am working on, so I built a tool that got that exact function running about 50x faster.
It's called LoopForge. It tries faster versions of your code, checks every one against the original, and throws out anything that changes the result. You only keep what's faster AND still correct.
I uploaded the tool for others to try it as well. It includes a demo using my findings as an example: It will walk you through the process as it tried to speed up my code, attempting multiple avenues and eventually showcasing the two faster versions that broke, and then the ~50x one.
Free and open source (MIT). About 30 seconds to try, steps in the reply.https://t.co/zlaZnAytKS
A bit more for anyone who wants to run it on their own code:
You can give it your function, a few example inputs, and a way to check the answer is right. It tries new versions and only keeps the ones that are faster and still correct.
The demo uses pre-written versions so you can watch it with zero setup. The real idea is to let an AI write the new versions for you. The instructions it follows are in the repo (AGENT_PROMPT.md), so you can plug in your own model.
It works best on small, self-contained code like sorting, matching, scoring, or number crunching. Not for code that mostly waits on a database or the internet, since the slow part there isn't really your code.
@IndustriousHQ Our office has been horribly under supplied for two weeks now. I reached out on LinkedIn and received no response. Does no one in your company care about customer service?