| Hey, thanks for your response! Great article and you guys are definitely in a good place now (yay Dark mode!) Your iterative approach to course-correction was absolutely the way to go so hats off for a job well done. >When you're focused on maintaining and building toward better reliability, it's harder to slow down and centralize principles, components, etc. Been there, done that, got the T-Shirt. Routing in Angular, API design and versioning, CMS integration, and more. I get it. >In the end, it's difficult to get people to agree to one thing, much more so when you're adding more and more people to the mix. There are probably a dozen relevant Dilberts on design-by-committee which are probably amplified by the egos and inexperience of dozens of 2x-year olds working at $hottest_unicorn. I strongly suspect that you are a very kind, patient, and understanding man. >We're in a much better place now. More than just having an interface library, we've created a framework for debating the various parts of the system and reinforcing that understanding that was missing early on. Congratulations, again. My sincerest apologies for focusing on the 'start line' when your article was about the race. Hindsight is absolutely 20/20 so hats off for a job well done and thanks for the follow-up. |