โ๏ธ
๐ก
Inspired by friends & personal work experiences. Friends would complain at their work that code was unoptimized, leading to shit piling on top of shit. Personal experience would be that startup culture prefer bootstrapping over optimization (for good reason & proof-of-concept). Why waste your time doing code review and nitpicking at all the files?
๐จ
Laymanโs terms, weโre a mechanic that constantly maintains your car to see if there are any problems of any sort that needs attention.
Technically, mechanic constantly reviews over your commits within PR's to suggest optimizations, apply code changes, and merge suggestions with fleshed documentation. Kind of like if you had an optimization engineer on 24/7.
Using it is really easy -- install it in your repo, and it'll run every time you commit within a PR. It'll also make informative comments, where you can branch the suggestions that it makes and merge with documentation if you like it (and test it...)
๐ง
I built it using Rust, Axum, Groq, and GraphQL. We used Perplexity, Warp, Zed, Arc and Raycast as our development tools.
๐
Executing this project was extremely informative (&frustrating) to me as an engineer โ it definitely showed me the advantages and disadvantages of Rust as a web server and its' conjunction with GitHub apps. I'm proud overall to make an app that my internal will use, and my friends will try.
Log in or sign up for Devpost to join the conversation.