Don’t over-architect, but also don’t architect yourself into a hole.
The best advice I was ever given was don’t do more than you need to, but make sure that you design in such a way that you can rearchitect without rewriting the while damned thing.
Always have an escape plan. That escape plan being having the ability to lift and shift.
Or, another job opportunity and litter the code with comments like “have fun parallelizing this code, sucker!”
Your post with 0 comments.
Honestly helpful when I’m feeling overwhelmed with my side project. I really started getting in my head about load balancing and hosting before remembering “chill, it’s a hobby project literally no one is using yet. You could run it off a pi in your basement.”
But on the plus side, it’s nice to learn those skills and have examples of them running to put on your resumé.
Dream big
It’s just practice is what I tell myself. One day you might need something to scale and then you’ll regret it not having made it scalable. If you have a previous project to copy that’s probably good too.
