The creators of This is Spinal Tap, the most influential mockumentary ever made, have been paid almost nothing due to "creative accounting":
In 2013, Harcourt advised [Harry] Shearer to ask Vivendi for a complete statement of his interests in This Is Spinal Tap. Harcourt combed through the material that came back, and her conclusions were so shocking that Shearer’s response was as unprintable as some of his band’s lyrics. According to Vivendi, Shearer and his three creative partners’ share of total worldwide merchandising income from 1984 to 2006 was $81, and the total income from soundtrack sales from 1989 to 2006 was $98. That’s just dollars, with no zeros at the end. It was Stonehenge all over again: They’d expected feet and got inches.
The co-creators -- Harry Shearer, Rob Reiner, Michael McKean and Christopher Guest -- are suing for 400 million.
A Cuepoint writer flees to Vegas during Coachella to confront the harsh reality of age. But I admit that Vegas during Coachella sounds pretty sweet:
"For that night, every part of what one might want out of a live music experience was available: A critically-acclaimed artist playing her full set, a cloudless night, a gorgeous view of the peculiar neon beauty of the Las Vegas Strip, and as my local friends would remind me, copious amounts of alcohol. St. Vincent finishes, we head inside for a nightcap cocktail, and then I head back to my hotel room, only having to stand in one quick taxi line (rather than the mess of a festival parking lot) to do so."
A nice tutorial on using Big O notation to express the time and space complexity of an algorithm, using sample code in different languages.
I've been brainstorming ideas for using Neat Hobby! to create fun illustrated guides to basic computer science concepts, like complexity, graph traversal, etc. As someone who's always struggled with the abstract concepts in math, I often wish I had a fun way to visualize these. I bet a lot of people who fell into web development from art and design backgrounds feel the same.
An overview of the front- and back-end technologies used to speed up the load time of the BBC homepage. Interesting but unsurprising to note that React in the browser was unacceptably slow for their use case.
An interesting article from the Walmart platform team. For what it's worth, I still prefer the SSR approach to send the user a fully-functional base UX, with non-critical functionality wired up with JavaScript on the client side.