A friend recently asked me a question about whether or not I am a Unity expert. I was caught off-guard. I have used Unity for roughly 2 years now, since early version 3.something… I’ve done a lot of different things. But I wasn’t sure if I’d consider myself an expert, because I don’t know what an expert looks like.
I guess no such thing as Unity Expert - exert those guys who developing it.
But I think goal should be not to become expert of Unity or C# or some other language or technology, but to become expert in your filed. In our case this is game development.
I think to be good game developer you should now:
Specifics of platform you working with. Even if you use soem cross-platform solution’s like Xamarin or Unity.
Techniques of CPU and GPU optimization.
Techniques of reducing RAM suage.
Techniques of reducing build size.
How to build strong game architecture and clean code.
Understanding of networking , pear to pear, socket server, http server
Techniques of network optimization, understanding client-server protocols
Point is that I use C# all the time, dut I do not know how exactly double lock work, so what? It doesn’t make me bad programmer. I just do not need threads in my work now, and if I do, I will learn it. As game developers we working with a lot of tools and languages and of course deep knowledge of those tools will give you benefits, bu I think it’s better to concentrate on more global things.
A unity expert is nothing like a C# expert. You could code in BOO and know ZERO C# and be the number one expert in unity. The key to being a unity expert is know EXACTLY how unity fits together. How to extend the editor. How to talk to components. How Unity’s engine behaves. The quirks, the issues, the Physx and middleware components that make up Unity and more.
A C# expert is an expert in C#.
A Unity expert is an expert in the unity engine, player runtimes, middleware and editor.
While i agree with the above posts that it doesn’t relate to unity expertise (except the few in between generic framework .net questions that apply to all languages including unity’s mono versions), i’d like to add that the questions, even for a regular .net / C# dev are very bad
They’re extremely outdates, 2005! This is ages ago in the .net world! Hell there are questions about APIs which have had replacements, twice! since they were considered the de facto API. (ASMX services anyone? System.XML?)
I rather disagree with many of the questions in there even for a .net business dev, many of the questions in “everyone who writes code” are pretty specific (windows service, PID, interop PIA) or flat out newbee level (thread process? exe dll? seriously?).
A touch of QFT there. You can be awesome but you’re only as good as your weakest member of the team. If you’re all in the same ballpark in skill but the result is still crap then you need to look at the decision making process.