Work has started. Local changes were made. Changes history needs to be saved and pushed to a remote repository.Congrats. You’re versioning now. This is where you make the switch between what’s saved and what you just did. This is also where you usually break things.
Just created an asset. Don’t know how to name it…Don’t know where to put it… So it’s a naming convention that you need. A good search bar is enough you say? Still. A good folder structure would help. And naming assets consistently won’t hurt.
Failing Faster involves failing. Breaking things along the way. Then doing some damage control. Or at least Version Control. Free or cheap Backup code & assets Work offline Easy to use Console and GUI Git / Git LFS / SourceTree / Bitbucket Now you can break everything. And turn back time. As if nothing ever happened.
Free or cheap Professional grade Code in C# Code offline Great auto-completion Powerful debugging Integration with Unity Visual Studio Code It’s free. Say thank you, Microsoft.
A state of the art tool. Powerful enough to create a whole game. Used by professional game developers. Game engine, baby. Free or cheap Professional grade Lots of tutorials Active community Fast prototyping Easy to learn Unity I know what you’re thinking. Why not go with Unreal Engine 4? I get it. I’ve been there.
List everything about the game in one place. Prioritize each item. Define related tasks. Sounds like a Product Backlog. Free or cheap Easy to use Fast set up Great UX Lightweight = Trello If you are to do good work, you need to focus on what’s important. Because everything can be done. Just not at …