@dolanor @chavacava agree.

@dolanor @chavacava both cases are bad for me, I would use:
- response
- user
- posts
- post

@gmhafiz on the other hand, when I see self in my code isn't likely a method receiver, I'm 100 % sure. 😁

@gmhafiz I can't, I tried but I hate it. 😅

@zylad @definitepotato i only use well-known single letter variable for loops, like i, j, or k.

@chavacava @dolanor and this is counterproductive because if you see t.Send() , what's t?, so you need to scroll or go to definition.

@chavacava @dolanor I think is more to laziness of thinking a good name. Naming things is really hard sometimes and we are calling good practice just for that.

@dolanor @chavacava well, first, I can't believe the use single-letter variables can be called good practice, so a prefer do bad practices here and use descriptive names. Second, I don't know how it can improve readability.

@chavacava I hate it. When I'm reading go code and I found a sigle-letter variable and i need to scroll/go to definition to know what that hell means t, for example.
On the other hand, llm models were trained with that ugly pattern, so they write a lot of them, even if you have rules to avoid them. It's so annoying.