Make the games you like to play, because you'll be playing them a lot.

Be patient, because you're not going to make great games in a week, or a month, or a year. It will take much study and practice. You'll probably fail a few times, too.

Start with something simple. Don't turn your nose at text-based games, for example. People love them, and you have to start with something you can handle.

Talk to people. Play their games, too. Then show them your games.

Try all kinds of engines. Try to learn programming. Figure out what you like best and what you can do good work with.

Don't give up easily.

Be kind.

As another already said, start with something simple.

There are lots of game engines out there that don't even require programming skills at all. If you're more of a visual learner that might be the way to go. A game engine like Crey might be a good starting place. 

But if you're like me and want to know what happens "Behind the scenes" in a video game, I would check out QB64 for the Qbasic programming language.  Some people might not remember, but back in the 80s and 90s there were tons of books and tutorials on how to make very simple Qbasic games. Heck, in just the first week of High School Qbasic class I had already figured out how to make a decent text adventure and from there I played around with graphics and other features.

One way to gauge how "easy" or "simple" a programming language is: Research how many lines of code it takes to do something simple, a prime example being the famous "Hello World" project. Some programming languages can accomplish this in 2 lines of code and others require 5 or more.

I hope this helped and welcome to game development -- it's fun!

EDIT: Just saw that you said you know C# already so in that case I'd skip QB64 and stick with that. I'm planning on learning C# myself.

I'd recommend a lite Computer Science background. Not college level education, but you need to be aware of how applications use up CPU and RAM, where it's stored in the memory, etc. Even if you're not a programmer, it's a big help. For instance, a lot of newbies using Unity tend to waste resources on giant 4K textures, even if there's not much detail. (You'd be surprised at how often 256 or 512 resolution textures will suffice in 3D games)

I'd also read up on Game Programming Patterns.  I don't expect you to understand all of it, but I recommend at least reading the bits on Game Loops, States and Object Pools.