I'm interested in simulating things like light and sound, but finding existing tools has been frustrating, so I started making my own. It took two weekends just to get a dot on screen. I've learned a lot, but progress can feel slow, and I'll have less time once school starts. Is this a reasonable way to spend it?
Am I going too deep building simulation tools from scratch?
Answers
If learning how the pieces work is part of the goal, that time wasn't wasted. Getting a dot on screen can involve setting up a window, a drawing surface, coordinates, and a loop. Those pieces can support more than just the dot.
Progress may feel front loaded, though there's no guarantee every next step will be quick. Try putting the drawing code in a function, then use it to make a line. From there, you could experiment with drawing a simple wave.
Reply to this answer
It depends what you want to spend your limited time on. If you're more excited about the behavior of light and sound than about rendering pixels, using an existing graphics library is a perfectly good shortcut. You can still write the simulation yourself without building every layer underneath it.
Reply to this answer
Two weekends for a dot sounds slow until you ask what you learned along the way. If the work is still interesting and you're getting a sense of achievement from it, there's no rule saying you have to optimize every hour.
That said, it's okay to pause when it starts feeling like a drag. Pick a small next goal you actually want to see, rather than treating the whole tool as something you must finish.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Vorlina.6x:
Mixing the two is fine too. Keep the scratch project for learning, and use a library when you want to get an experiment on screen sooner.