

Can’t divulge too many details, but one example was when we had 2 options for solving a problem: 1. The “easy” way, storing a bunch small blobs to s3 as a job was running on an embedded device, or 2. The slightly tricky, implement streaming of said data on the device (not as easy as it sounds).
We went with option 1, the easy one, because it was deemed faster bang for the buck. I did some basic math showing that the bandwidth required upload the high number of blobs to s3 within our time budget was not possible on our uplink.
After we spend a month failing on 1., it was clear that we hit the predicted problem. Eventuelly we implement option 2.
Don’t hesitate or overthink it. Just dive headfirst into it. The day you start is the best moment. The thing you chose to do, is the best.
Learn by playing around. Play to your strengths. Dabble with coding, sound, graphics, mechanics, and figure out what gets the fire going. Feed that fire.
When you’ve had a bit of taste, try to complete a small simple project. This is surprisingly difficult! Learn to remove features and complexity, simplifying until you can actually finish the game.