[–] 4 points 1 week ago

Never understood touchscreen on laptop. I can imagine artists might need this in some workflows but I doubt they’d use shitty touchscreen instead of specialized tools like stylus or dedicated device. But for everyone else idk when do you even want to use them.

  • source
  • [–] 2 points 1 month ago*

    Lack of content for sure. There is no monetization or integration with donation platforms. I think it’s major driver for content creators to prefer YouTube. At some point I wanted to ask YouTube creator to consider Peertube but I realized I’ll be asking them to loose profit. They’d loose view on YouTube and get nothing in return.

    There is also number of things which I hate in app.

    Login and search are stupid in multiple ways:
    • Logged off - explore tab shows videos from multiple platforms. Logged on - only from one platform.
    • Logged off - platforms show vids from selected platform. Logged on - you can select platform but list of vids is empty.
    • On explore tab advanced search is “more filters” on platforms tab - it’s icon.
    • What is the difference between hot and trending
    Other UX:
    • in explore, platform logos take 1/3 of phone screen. Generally a lot of wasted space and duplicated buttons, navigations
    • When filtering by language it’s not clear do I get untagged results or not
  • source
  •  

    Hello my fellow, lemons? I have this problem in my current project I’m out of clue how to approach it. Maybe someone had similar experience and can give an advice.

    Our requirements captured in JIRA. Throughout years we accumulated thousands of user stories. Say suppose following naive requirements team knows about:

    • Day 1: create home page
    • Day 20: create profile page
    • Day 50: add green footer to all pages
    • Day 100: create admin page Day 150: change footer color to blue

    Now I’m doing refactoring (yes, I know, this is the actual problem) on day 400 and noticed that footer on profile page having green footer. Because requirements are just set of individual statements not consolidated with all history of system no one on the team knows why is that, is it bug or requirement did change on day 300 but we cant find it now.

    When I worked in Waterfall we had BRD and FRD stating current actual desired state of system which was “reduced” from individual requirements which were coming in throughout project life. When in doubt devs can check FRD and not only know how system expected to behave but also which are other parts of the system that will be affected. How is it in Agile? To my understanding FRD is not a thing in Agile. Do I need to scan through hundreds of tickets and hope I didn’t miss anything every time i’m doing any non-trivial change to system?

    view more: next ›