I loved this and would go so far as to say that anyone working a tech company who isn't an engineer needs to read this post and pretty much all the posts on tha

I loved this and would go so far as to say that anyone working a tech company who isn't an engineer needs to read this post and pretty much all the posts on that blog. They do an excellent job of breaking this stuff down and helping you understand why engineering is not the same as manufacturing teh widgets. The latter is all about creating and replicating efficient processes; the former is about sui generis creation, like sculpture. FWIW in my mind after all these years, I've come to some of the very same conclusions but these do a great job of articulating WHY. Sort of like learning to play music by rote vs learning to read music. So in my "not a developer" mind I've chalked it up to the fact that every website is a cathedral. Each one is different. Each one is built by artisans from scratch. But this post and other posts on the blog really explain exactly why each site is unique and the issues around research in a way no other engineer has ever explained to me before. Now I fully understand what to look for and how to ask for it. I'd had product owner/scrum training so I thoroughly understood story points, break stuff down, but the clincher for me here was the idea of prioritizing the smaller stories that help us learn quickly, almost MVPing the MVP. Again, this is stuff I've sort of picked up over the years, but what a gift to help others skip that way of learning. These need to be in a book and they need to be taught to anyone working in technology.