4 ms·
I wonder if there's redundancies in terms of MVC patterns or there's just a lot of worker and irregular processes that don't fit neatly into MVC. Another thing
by doggodaddo78 5y ago
I wonder if there's redundancies in terms of MVC patterns or there's just a lot of worker and irregular processes that don't fit neatly into MVC.
Another thing is to be careful about deprecation and feature roadmapping that's developer-whim-/assumption-led instead of customer-led. It's too easy to say "nobody uses this" or "it's not important because nobody uses it" when it can be vital to certain users.
(600 moons ago, I took the SAT-I without studying or prep: 800 math. English... let's not go there.)
- dangoor 5y agoI don't think we have many redundancies, especially after all of this upgrade work. When we deprecate user-facing functionality, that's done with our product managers making the call, and involves usage data and a lot of coordination with our user support people. It's always a tough call, because someone out there won't be happy, but we have to choose the best path forward we can see at every given moment.
- doggodaddo78 5y agoThat's true. Can't please all of the people all of the time without an infinite amount of effort. "Perfect is the enemy..." I do try to think about important but less popular features (like bulk operations for heavy users) and accessibility concerns like deafness, blindness (screen readers, contrast, and fonts), colorblindness, photosensitive epilepsy, dyslexia, nonnative speakers (more icons and pictures), and reasonable device support.