I make games

  • 0 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • As someone who makes indie games professionally, I taught myself how to program by making video games. Maybe it’s just my adhd, but I have a difficult time with organized learning, but I pick things up really quickly by doing. I wouldn’t get too caught up in the “I need to learn it the right way before I make games” part, since the making games part is exactly what kept programming interesting and engaging enough to prevent me from getting bored.

    Second I also wouldn’t get too locked up trying to decide which programming language to use. Modern programming languages are all conceptually pretty similar. It’s really only minor syntax differences. Learning a new programming language is mostly just a matter of “how do I write a for loop in this language again?” It doesn’t take too long to adapt.

    I use Unity and C# right now, and I’m in the middle of learning Godot to make the switch. I would generally agree with what other people have said. C# is a pretty good language to start with. Just low level enough to make sure you learn fundamentals without being so low level that you have to fiddle with memory addresses and pointers like c/c++.

    As for codecademy, I tried it when I was first starting out like 10 years ago, so I can’t vouch for it now, but it seemed to very much be “Learn how to type code” and not “learn how to actually program.” Just explaining how to write if statements and for loops isn’t really teaching programming. I still don’t think there’s really a good universal way to teach it, even after taking programming classes in college. Everyone sort of picks it up differently, at different paces, and enjoys different parts of it, so I still think picking a project you think sounds cool and finding and following along with YouTube tutorials and just trying stuff out until it works is a pretty good way to get started. You can always take the time to read a book or take a course after you’ve determined if programming is even something you’re vaguely interested in.



















  • So to answer your last question, yes. Video editing is probably one of the most demanding things you can do with a drive, and will shorten the lifespan of the device. But this is true for literally any kind of drive, and any operation you do with a drive. Hard drives may not have a write cycle limitation like ssds, but they have moving parts that wear with use. So theres not really anything you can do to avoid the issue. To video edit period, you’re going to put wear on your drive.

    Also to give some context, average SSDs have about 100,000 write cycles per cell, before write failure can have a chance of happening. Since it distributes it out across the cells, you could write 1GB to a 1TB SSD about 100 million times. This isn’t a small number really, it’ll take a while to do that. I’ve been editing here and there on my ssd for 5+ years on top of full time video game development and it still works fine, with no signs of stopping. I read some guy online who edited video nearly every day for three years, and the ssd software still said he had about 10% of the ssd life remaining before write failures. So depending in your work flow your drive could last 4 to 10+ years.

    The only real differences here are cost and speed. Do you want to wait around for a slow hdd while you’re editing, or do you want to edit quickly and enjoy the process? I personally would always edit on an SSD because you’re not solving the problem by using something else. Like yea, maybe a hard drive would last twice as long as an ssd, but it’s also twice as slow, so you’re just stretching those, say, 5 years of man-hours into 10. You’re not actually getting more work done.