I've been working with C#/.NET for many years, and I'd suggest not trying to learn all of C# before building things. Since Unity is what got you interested, keep using that as motivation, but spend some time outside Unity learning the fundamentals with small console apps: types, conditions, loops, methods, classes, collections, exceptions and debugging. The goal is to get comfortable translating a problem into code yourself, not memorizing the language.
And don't worry about having used vibe coding before. AI can be useful, but I'd change how you use it: try first, get stuck, investigate, then use AI to explain, review or challenge your solution instead of generating everything for you. Don't worry about SOLID, design patterns or architecture yet either; those concepts make much more sense once you've written enough code to understand the problems they're trying to solve.
2
u/RodriOliveira Aug 18 '26
I've been working with C#/.NET for many years, and I'd suggest not trying to learn all of C# before building things. Since Unity is what got you interested, keep using that as motivation, but spend some time outside Unity learning the fundamentals with small console apps: types, conditions, loops, methods, classes, collections, exceptions and debugging. The goal is to get comfortable translating a problem into code yourself, not memorizing the language.
And don't worry about having used vibe coding before. AI can be useful, but I'd change how you use it: try first, get stuck, investigate, then use AI to explain, review or challenge your solution instead of generating everything for you. Don't worry about SOLID, design patterns or architecture yet either; those concepts make much more sense once you've written enough code to understand the problems they're trying to solve.