Yes, readability is very important. Sadly, the trend I now see is that those migrating towards a senior role (or, what they believe an EA is) are unable to progress past the first couple of chapters. Had they, actually, had the proper training and mindset, they would be able to understand what the true value an EA brings to a business by having designed a system that is flexible and won't break as the business grows. Instead, we see senior individuals relegated to pasture and younger, less mature and experienced developers calling for a complete redesign (at significant cost) because they simply don't know what they don't know. It's the role of the EA to make sure the purpose and vision of the architecture and product roadmaps are understood by the team. And, they should help identify the weaknesses of their team and get them the training they need (training? Who pays for training???).
On the flip side, I have seen EAs who sit in their office and abstract away and never interact. Keeping your wonderful ideas and visions bottled up simply doesn't cut it. The less senior folks are put off by what they see and, frankly, rightfully so.
I am one of the EAs who has recently been put to pasture. Our organization decided to restructure and move away from developing products and services. Instead, they have decided to concentrate on just one small aspect of the business - the one that corporate felt makes them the most money prior to going public. Developers are left doing the same thing over and over again with no opportunity to step outside the box and expand their knowledge. There is no mentoring. I found myself hindered in my role in how I could interact with and mentor the developers - it was all about billable time vs growth. Now, I am gone - laid off - six months now. The developers have, thankfully, recognized boredom and all except the H1.B's and greencards have left. It's a very shortsighted and, I suspect, they will feel the ramifications in the future. Nah..they won't...they will just hire more H1.B's and greencards to fill the void because they won't rehire those now unemployed because of their shortsighted vision...we're damaged goods.
But, I can't find a job. I am finding that I am either overqualified or not specialized enough in the language/framework of the week or the role of architect is now being filled by organizations paying $80K instead of the $120K+ we used to command for the same "title". Like everyone else, I've got bills to pay. Yet, many hiring managers seem hard pressed to understand that I am comfortable going backwards and doing more coding for less pay. You might say you will never get in this position - I know that's what I did. Surprise.