_dax

The world isn't so simple that pay scales with skill. There's definitely a base level of proficiency that you need but it's not so high. It's more about making the decisions, choosing industries where this is possible, and managing to stay interested.

I know a few people between ages 40-50 that make this much working at a hedge fund as pure engineers. None of them are incredible, to be honest I could do their job and I'm half their age. They've just put in their time there, didn't get distracted by more interesting opportunities, and don't mind a typical office job with no perks.

I think it's a false dichotomy that great architecture and fast iteration are at odds. In fact, great architecture is what allows fast iteration to happen.

Yes, simplify your system by using as few moving parts as possible. But that also means don't use bloated frameworks that silently slow down your iteration pace with technical debt.

So many startups I've consulted with were stuck with having to redo core architecture right when they found market fit. It's a tough position to be in. The main rule to follow is that good design allows better design to happen later, it's worth investing in that

I actually implemented exactly this a few days ago. It essentially procedurally generates channels from your library that you can flip through. Working on Chromecast support before I open source it