> every time I start a project I decide to do the easy thing first and wait until I critically need streaming. Absolutely reasonable decision making. Do what y

> every time I start a project I decide to do the easy thing first and wait until I critically need streaming. Absolutely reasonable decision making. Do what you need at the time you write the code, or at best, be slightly ahead of the curve. Don't forecast features you do not need. Humans are unreasonable about success of their own projects. >Maybe it’s the right thing to do to avoid over-engineering It is the only thing to do. You do not know the future use cases. > [...] but this comes up often enough that I’m usually in a mild state of frustration about something being under-developed. If your software is subpar with regards to your needs, congrats, it is successful software! Building the perfect software from the beginning is unreasonable because you might just never release or even use it. Build imperfect things, and be reasonably frustrated BH them so that it gives you the energy to improve them!