My tech stack is pretty simple. I don’t use a ton of tools because I’d rather get good at a few than be mediocre with many. Here’s what I’m actually using in 2025.
This isn’t about having the most tools — it’s about mastering the ones that actually matter for building systems that work.
Development
Roblox Studio
Where all the Roblox magic happens. Roblox Studio handles everything—LuaU scripting, UI design, building systems, testing mechanics. The integrated UI editor is actually pretty solid for creating interfaces, especially when you need pixel-perfect positioning and responsive scaling across different screen sizes. I use Studio for designing complex UI hierarchies, setting up data binding for dynamic interfaces, and building modular systems that can scale across different aviation projects.
The real-time collaboration features are clutch when working with teams, and the built-in analytics help optimize performance for larger systems. The terrain editor and lighting engine are surprisingly powerful for creating immersive environments, and the physics simulation is essential for testing aviation mechanics. Studio’s constraint system handles complex mechanical interactions that are crucial for realistic flight systems. Sure, the script editor could be better, but the integrated debugger and output console make troubleshooting pretty efficient.
Visual Studio Code
For everything that isn’t Roblox, Visual Studio Code is my go-to. Python automation scripts, JavaScript projects, any config files — VSCode just works and doesn’t get in the way. The extension ecosystem is incredible, and I’ve got some solid ones set up for syntax highlighting, git integration, and code formatting. Most of my non-Roblox coding happens here since the editor is way better than Studio’s, especially for larger projects that need proper file organization.
The integrated terminal is a game-changer for running scripts and managing repositories. IntelliSense and autocomplete features speed up development significantly, and the debugging tools are solid for tracking down issues in complex automation systems. The customizable workspace settings mean I can have different configurations for different project types, which keeps everything organized and efficient.
Design
Figma
Everything design-related lives in Figma. UI mockups for Roblox interfaces, basic branding work, wireframes for dashboards — it all happens here. The component system keeps things organized when I’m working on larger interface projects, and the auto-layout features make responsive design way easier. It’s web-based so I can access designs anywhere, which is helpful when inspiration strikes or quick edits are needed during development.
The collaboration features are excellent for getting feedback on designs before implementing them in Studio. The prototyping tools let me test user flows and interactions, which saves time when building actual interfaces. I’m not doing crazy advanced design work — mostly functional UI stuff that needs to look clean and work well in-game, but Figma’s design systems and style guides keep everything consistent across different projects and team members.
That’s It
Simple tools, consistent workflow, better results. That’s the philosophy.
Yeah, that’s pretty much it. I know it’s not as impressive as having 20+ tools in your stack, but this setup handles everything I need for building internal systems and automation tools. I’d rather spend time actually building stuff than constantly switching between different apps and learning new workflows.
These tools are reliable, they integrate well enough, and they don’t slow me down. If something breaks or stops working, I’ll replace it. Until then, this does the job.