4 ms·
> I have zero expertise and no real design credentials. > If these rules don’t click for you, then you probably have a long way to go in your UX journey. You
by unfunco 8y ago
> I have zero expertise and no real design credentials.
> If these rules don’t click for you, then you probably have a long way to go in your UX journey.
You seem to establish yourself as knowing very little, but then belittle people that might know more than you if they disagree with your rules that you've just made up.
> Wiki and Insights are features I have never used on github and may never use. They should be hidden by default.
Just because you have never used them doesn't mean nobody has used them, and I read the next line about "intelligently" showing them (since when has a boolean comparison been considered intelligence?) if they've been used before; but then how do those features get discovered?
I only want to sound as rude as you were to the person whose work you've criticised for pageviews, so I'll leave it at: stick to DevOps.
> There is always a flexible solution which caters to both experts and novices simultaneously.
That's wrong, regardless of how bold you make the word always.
- lol768 8y ago> You seem to establish yourself as knowing very little, but then belittle people that might know more than you if they disagree with your rules that you've just made up. Yeah, that "you probably have a long way to go in your UX journey" comment irked me when I read it. I'm glad it's not just me who found it patronising. Your point about feature discovery is a good one that the article didn't address. It's all well and good hiding less used 'expert' features, but all experts were once novices.