Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
That *is* a hard guideline. If you are unable to at least temporarily dissociate your thought process from that of a developer who knows everything about the software's functionality, and associate it with that of a user who has never seen it before, then it's an issue.
Share your software with others. Observe how they try to use it. Solicit feedback after a user-testing session, but have enough recordings or internal logging in the software to reconstruct enough info to not rely on the faulty human memory.
![[ColeJ]](https://pbs.twimg.com/profile_images/1043000626056065024/vDRPnUpt_normal.jpg)
And more than anything, resist the urge to dismiss usability feedback out-of-hand based on the stereotypical user-antagonistic view that "users are stupid". What they say isn't 100% dogmatic truth, but it's your duty to root out the core issue and address that.
(One way to make this easier is to ask them what they *dislike* about working with a thing, not how they would want it to work instead.)
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
