Depends on whether the team I am in uses Scrum or not.

If the team uses Scrum, everything is on the backlog, so rarely do I need personal lists.

If the team doesn’t use Scrum, then I set up my own personal Scrum board. That way, I can deal better with people coming in and saying “hey, snek_boi, this task that I just thought of is urgent and I need you to drop everything you’re doing and do this now”. With the Scrum board, I can then ask them if what they need me to do is more important than whatever’s on top of my personal backlog, and often they themselves realize their ‘urgent’ task is actually not that urgent.

Since you asked about software, I’ve used Taiga and Notion.

Also, I used to do GTD religiously, but now I mainly use Scrum because it forces me to ruthlessly prioritize. Since you asked about apps, I’ll tell you that when I did GTD, I used Joplin with Syncthing (or some combination of Syncthing and a local notes app). I switched to StandardNotes before stopping doing GTD altogether. Maybe I’ll come back to GTD in the future.

I also almost started Bullet Journaling, buying the journal and all, but a friend of mine was quite depressed and seemed to need it more so I gave it all to him.

I’m sorry for having said something untrue. For example, DannyBoy points out that GNOME and whatever Ubuntu uses do have fractional scaling.

However, is my experience untrue? Was I lying when I said that my track-pad two-finger scrolling is frustrating? Furthermore, it’s not unusual for people at work to try my track-pad and it being way too sensitive or too un-sensitive, but no in between.

Was I lying when I said that, for me, it’s hard to get software? Was I lying when I said that maybe this is a skill issue on my part, but even that is indicative of a lack of easy ways of getting reassurance in the way that Apple makes it easy to find software in their App Store?

Was I lying when I said that, to me, GNOME is gorgeous?

Was the creator of the Mojo language lying when he recounted his experience developing Swift?

Was I lying when I said that developers are leaving Linux?

I agree that GNOME and KDE are gorgeous and very polished in many ways. However, I have had some problems in GNOME, Fedora, or Open Suse:

• fractional scaling is not immediately available in Fedora or OpenSuse, at least to users who don’t know how to use the terminal [Edit: Thanks, DannyBoys for pointing out that Ubuntu may have fractional scaling enabled by default and that experimental fractional scaling on GNOME can be activated, at a battery cost]
• the track-pad two-finger scrolling is painful (compared to a Mac) to me and to people who have used my laptop with Fedora or OpenSuse
• sometimes it’s hard for me to get software, especially outside of .debs. For example, in Fedora I had trouble getting Signal Desktop installed from a source that I felt comfortable with (maybe this speaks to my ignorance in how Fedora packages are set up and distributed more than the reality of insecurity, but even this is part of the issue: I couldn’t find any reassurance). To be fair, Open Suse gave me that reassurance, because I understood that YAST was somehow more directly tied to the source (I could be wrong, but that was my impression). However, YAST’s software download software is a far cry from the kind of UX that the GNOME Software app is or the Apple App Store.

Despite these problems, I do have to say that GNOME is absolutely gorgeous. It’s precisely the kind of user-centricity that I want to see in Linux.

However, the end-users aren’t the only users. There are also developers! For example, I remember listening to the developer of the Mojo language talking with Richard Feldman, and the developer said that the development of the Swift language made it clear to him that Apple is aggressively user-centric. I don’t doubt that there are many problems with Swift as with Apple products in general, but I don’t see that kind of discourse in Linux coming from the main maintainers. Instead, there seems to be a vanguard arguing for a better developer experience (such as writing kernel code in Rust), and they find loads of friction. Heck, key developers are leaving Linux!

Edit: Clarified what is strictly my interpretation.

Today, it is practically impossible to survive being a significant Linux maintainer or cross-subsystem contributor if you’re not employed to do it by a corporation. An interviewer to the Linux dev that’s mentioned in the article: “So what did you do next to try to convince the Linux kernel devs of the need for more focus on end-users?”

I appears as if Linux is a nest that is not built with a consistent set of user-centric principles. Instead, it seems that each part of the nest is built with a specific corporation or project in mind.

Assuming I’m right that Linux is built with project-based thinking and not product-based thinking, I do wonder what a user-centric Linux or another user-centric FLOSS OS would be like, an OS that is so smoothly built that users come to think of it not as an OS for tech-savvy people, but an obvious alternative that you install immediately after getting a computer.

If Linux is indeed built with project-based thinking, then I wonder why that is. The uncharitable explanation is that someone doesn’t want Linux to have a MacOS-like smooth and gorgeous experience. If you don’t think MacOS is smooth and gorgeous, I’ll address that.

I know some people have suffered immensely with Apple products not only because Apple builds devices that can’t be repaired, but because of things simply not working. However, there are many people who love Apple. That’s the kind of passionate advocacy that I would love to see in Linux, and not just around freedom and value-based judgements. I want Linux to be thought of as the least-friction tool for professional or recreational use. I want people to think of Linux as gorgeous and usable.

Of course, we can apply Hanlon’s razor to this situation (“Never attribute to malice that which is adequately explained by [ignorance or lack of skill or practice].”). Managing a product is difficult. Managing a community is difficult. When the nest’s design is not built by a team constantly seeking to care about users, but instead by a bunch of users pecking into the nest until their corner is shaped the way they want, it’s not surprising to see a lack of user-centricity.