Eric

A codebase shouldn't feel like this, but I see it a lot. unused imports and packages rampant copy/paste half-written features unclear patterns commented out code frequent spelling errors inconsistency 100s of warnings no validation swallowed errors a general sense of disorder

Lots of people are pinging me about the "Adpocalypse on Twitch" and wondering if we're ok. None of our ad-revenue on Twitch has changed because none of the content we talk about has sexual themes or politics. Our ferret rescue is run entirely off ad-revenue and it's gaining income following the normal yearly trends for October/November. There are likely some channels that get misidentified as having political content due to tags or categories but this so-far seems to be rare. A tag lacks critical context for the kind of content being provided and many people use tags in joking ways or to identify themselves in a particular way. I don't feel tags make a lot of sense for targeting ads as it leads to splash damage because of this. An Adpocalypse would be damaging the entire platform as a whole. None of that has been seen yet so there seems to be a lot of jumping to conclusions here. If this was happening in a widespread or apocalyptic manner we'd see impacts far outside of isolated instances like we have. Anyway, doom-scroll less. Look at cute animals more.

Some engineering principles I live by: ✓ Make it work, make it right, make it fast ✓ Progressive disclosure of complexity ✓ Minimize the number of concepts & modes ✓ Most 'flukes' aren't… your tech just sucks ✓ Feedback must be given to users instantly ✓ Maximize user exposure hours ✓ Demo your software frequently to fresh eyes ✓ Sweat every word of product copy you render ✓ You're never done working on performance ✓ You're never done. Software ages like milk, not wine ✓ Visualizing traces of time is the best way to optimize it ✓ Ship frequently and strive to build in public ✓ Errors must have globally unique codes & hyperlinks ✓ Red is not enough to signal "error" (8% of men have red-green color blindness)

I don’t ask for permission to refactor. I don’t ask for permission to optimize performance. I don’t ask for permission to make it secure. I don’t ask for permission to make it accessible. I don’t ask for permission to write tests. I don’t ask for permission to do my job well.