Currently I am doing both actually; Practicing code in C++ and Java, while studying how C# works in Unity. The problem is, it has been a long time and I have yet to make myself known for what I really want to do in this industry, but based on my tight schedule, I cant really focus on much until / unless I am fully involved…
If your goal is to build a game as fast as possible then you will probably be better off using an existing engine. There's still plenty of reasons to write your own engine: you'll have full control of how everything works in the background, you won't have to pay any royalties to third parties, you will fully understand how…
I wouldn't consider not writing your own engine as "cutting corners" although I've seen some arrogant programmers make ridiculous claims like that. At the end of the day, you should take steps to move towards your ideal job. If you want to develop or improve a game engine, then learning how one works is an important step…
This sounds reasonable. I dont know much about coding, I only do it when I have to but, maybe you could take an opensource engine and add to it. Would that teach you more?
Unity is a great engine/editor. Its developing fast and I dont think you could ever get tired of it. Not sure I understand the part about making your own game without an editor. Does it mean if you code everything yourself you walk with clanging sounds and wear iron under-trousers?
Unless you have a large team and lots of funding you just won't be able to match the convenience of using a 3rd party engine. Especially when it comes to how the art looks. However I do know a few programmers who have turned indie and made their own custom engines. It's usually been because the game they're making is…