I know that even before I finish my studies, the game industry is not for me. However, I firmly believe that the skills required to make video games are applicable to other computer-oriented fields.
"This is just programming, right?"
Okay, no. My experience writing code in the game engine with a visual appearance to help development only touches the vast ocean of "programming."
Video games may of course be incredibly complex software during their heyday, and some popular games were originally written in Java, such as Markus Persson ’s masterpiece "Minecraft", which was sold for $ 2.5 billion Microsoft. However, the idea of writing a simple web application from scratch is more frightening than the idea of attracting people in my narrow comfort zone.
You can easily install a game engine (such as Unity) by looking at a game similar to the game you made and installing the engine used. Unity runs scripts written in C #, so with native Visual Studio integration, there is no need to worry about which programming language or where to write it. However, using the same method to select the IDE and all the plugins needed to optimally build a specific application is a challenge-especially if you are not sure what to build in the beginning! The choice between the game engine and the IDE is subjectively similar, but for those who have not yet tried several of these methods, his choices seem a bit wider.
The best option is to learn through trial and error:
Fortunately, just like in game development, the programming documentation for almost any application is comprehensive, and there are many channels full of information (usually free). There are also features and plug-ins, such as code completion, that can help overcome the initial difficulties. After finally getting my footsteps into "real" programming, the available help covered all the problems I encountered. In addition, there are several active forums where people are discussing these topics. So far, I have asked and answered any questions I can ask.
When it comes to actually generating code, the lack of visual construction, such as Unreal Engine's friendly "Blue Print" system, makes it difficult to see all the connections in the code. It's hard to read ... just like learning to read for the first time.
Now, imagine from elementary school to high school: in the new environment is the same garbage, and you are slightly older than a few months ago. That's it!
It is precisely as my childish desire for what I am good at fades away, the fear of the unknown disappears, and my coding experience is like that.
When designing a UI with Vaadin, continue reading and try that Java syntax is similar to game design, even if the process occurs in other settings. I have spent some relatively interesting days studying, which has made me cringe in my initial attempts and shows that my progress is obvious. Shortly thereafter, my first web application was up and running. Adapting and iterating what I have done becomes a breeze, rather than blindly browsing through completely unfamiliar things. This actually includes learning a new programming language / environment / tool or anything.
So, what is the purpose of this subjective, specific and short blog post? Sounds tacky, but your knowledge base can always expand and adapt to new things.
The road to learning paves the way to everywhere-all you have to do is move on.
Until next time, Mikael
from: https://dev.to//mikaelsu/indie-game-developer-attempts-real-programming-3l4o
