Sorry...I thought when you said "blending", you meant an engineer would be doing both. I want my engineers focused on code and my UX people focused on the customer. It's two completely separate work streams. The best engineers are the names you never hear and don't go anywhere near the UX outside of executing their code through the frameworks created by UX and architects.
Thanks. Sorry I wasn't clear.
My guess is in all the mix of how everything is made, the final output product to the consumer will continue to be heavily UX focused. That's what the good companies do.
And for Twitter, there is clearly room to grow. Not having the ability edit was famously an issue. Things like that. Geting that right of course takes a mix of lots of different skill sets. But my expectation is they continue to focus on getting it right for the user. We'll see.
You're probably right. I'm probably overreacting to his letter... But he's an engineer. Engineers think differently than product and UX folks about product. So "engineering-driven" company gave me pause.
My main point: engineering-driven companies are less customer focused than product driven companies. Which may work for Twitter because they already have a large user base. It's not a startup in search of a customer pain to solve.
The funny thing is the botched rollout of blue is probably an example of something that wasn't customer-focused. It solved a business need: generate revenue. But didn't solve a customer pain. It actually was a worse user experience because it was harder to tell if an account was a real entity.