Some form of tree-shaking type of thing would probably be quite handy for images, but yeah I'm a bit wary here as well. First thought would be what happens when it hits Out-of-Memory, DNS timeout, or loses network connectivity or another edge case that totally happens in Production.
Removing those code paths would not be a good thing, but I guess if you build your apps right you could just have your container orchestration system recover by replacing the Pod.
Glad to see you posting in here, Matt. Your blog post on staying with the USDS popped up a week or so back for me in some subreddit and inspired me put in an application (didn't even know it was a "thing" before that).
Seems like a great opportunity to solve some interesting problems, but more importantly make an impact.
Glad to see you guys are continuing moving along with Percy. Really helped me out when I implemented it at a previous gig a little after Percy launched.
Creativity, Inc. by Ed Catmull
It's the story of Pixar and there's so many things I enjoyed about this book. It helped validate for me many of my instincts in running a creative business.
The Martian by Andy Weir
I very much enjoyed the story and how it was all approached.
Seven Eves by Neil Stephenson
Similar to his other books (Snow Crash and Cryptonomicon) I've gifted these a few times. I really enjoy his method of storytelling and his stories appeal to the geek in me as well.
Depending on the nature of your product and your rewrites in my experience a customer facing system that has parts improved in parts can be interpreted as not solving the right problems (if something UI related is being updated).
The best thing I could say about it is that when approaching behind-the-scenes pieces this is my preferred approach, but for customer-facing pieces I prefer (and have had better reception on updates) to update those pieces as a whole. But again, this depends on the complexity, updating a small piece such as a button should not require a large change but updating the layout or styling would require more significant updates.
Removing those code paths would not be a good thing, but I guess if you build your apps right you could just have your container orchestration system recover by replacing the Pod.