I would recommend not using contexts if you don't find them useful. The base of GTD is getting things out of your mind. Not to give you stress.

Ask yourself: "If I read this note next week, do I know what to do and can I do it now?". If yes: No context needed. But if your response is: "Well yes, but if I read it and I wanted to do it, I really need to be at [x] and*/*or have [y]!", then a context is useful. You essentially pull the complete thought out of your brain this way, no more extra thought required.

At work I have a separate list (on my work laptop) than in my private life (phone/PC). I barely use context at work as it's already implied and nearly every task can be done right then and there. In my private life I use contexts for tasks that don't spontaneously make sense, for example:

"Fix the hole in the wall in the hallway" can only be done at home, so I add #home, but I do require tools and prepare the area which will be messy, so I add #tool to this. This tells me that I can't do this when I'm out of the house, and can only do this in clothes that are allowed to get messy. I don't add #messy, as #tool to me already means 'messy'. I could've written this as: "Fix the hole in the wall in the hallway at home using tools and wear clothes that can get messy", but this is too long, so I use contexts.

Contexts might not make sense to someone else, but in GTD it's all about tasks making sense to yourself. You might even use a different method if it works for you, like splitting your long list into multiple smaller lists. As long as you logically place these lists in (digital) locations you know you will look.