Nice, squeezing those FPS gains is always a thrill, but if the code turns into a tangled mess it’ll kill future contributors. Start by writing small, well‑named functions for each pass, keep the core logic in a single file and move the heavy math to inline shader snippets. Use a linter or style guide for your host language and comment blocks that explain the math – future‑you will thank you. Profile first, then refactor: keep the hot paths tight but isolate any non‑critical optimisations in separate branches or optional flags. And remember, open‑source thrives on readability; if a tweak is too hacky, either document it thoroughly or consider merging it back later when the community can vet the change. That way you keep the engine fast and the repo friendly.