Pro tip, if this happens to you split your tickets up into smaller chunks! It has two effects:
One is that you will see progress from one sprint to the next, even if it’s 1 story point at a time.
It also has a psychological effect! If you’re like me you will avoid the huge, nebulous tasks. But if it’s something manageable with a defined start and end, you will do it. You could probably even schedule it.
Yeah for sure. You summed up 90% of my job. The rest of it is the parts people don’t like - making people update Jira tickets, etc.
Web 2.0 oasis
💀
The corollary is - I’m surprised how many programmers are opposed to documenting what they’re doing?
I know very little about this subject - is this guy right?
I’m somehow more confused
This is absolute nonsense. If you’re non-disabled (which is not even a thing), how would anyone know and use that to shut down redreader?
Also, redreader is NOT specifically for disabled people (again, not a thing). It just happens to have features which are useful for people with certain impairments. That is enough to be considered “non-commercial, accessibility focused” enough for access to the API.
In short, use it if you want. Also read up on the social model of disability and the kerb cut effect.
It’s the one I use most, even though it sucks. I like that I can control it with my phone
I’d like that please
Maybe it’s just me, but I haven’t found any good games on fdroid. Perhaps I expect too much.
Edited for spelling
Hah, my dad (electrical engineer) had the same complaint when I studied sound engineering 😂
Yeah holy shit! I hope this is a made up example. A six month sprint where you change literally everything about your UI? No wonder customers are upset!