build → break → debug → fix → break again → push
name: Tomer
handle: TomerGamerTV
status: "probably building something"
specialty:
- native apps
- automation
- game tools
- web experiments
- compatibility & runtime projects
bugs_created: "yes"
bugs_fixed: "eventually"I make whatever seems interesting enough to turn into a repository.
Sometimes it's an app. Sometimes it's a game tool. Sometimes it's automation. Sometimes it's a project that started with "this should be easy" and ended three days later inside a debugger.
If it worked perfectly on the first try, I'm immediately suspicious.
These are based on languages that actually show up across my repositories — not a wishlist of things I touched once in a tutorial.
A few examples of the kinds of things I end up working on:
- FeatherPlus — iOS / iPadOS app management and sideloading work in Swift.
- UAT-Global-Server — Python automation built around an Uma Musume auto trainer.
- VibedWorldTools — Minecraft tooling written in Kotlin.
- discord-video-player — a JavaScript site that plays random Discord-hosted videos.
- blog — my attempt at having a blog without getting distracted by rebuilding the blog itself.
- My-Roblox-Scripts — exactly what the repository name warns you about.
Make something interesting.
Break it.
Figure out why it broke.
Fix it.
Break something completely unrelated.
git push
Windows installations broken : 11
Lessons learned : debatable
Would do it again : probably
README powered by questionable decisions, unfinished side projects, and git push.





