[akira2501]

> It's such a neat way to remove cruft.

I don't disagree, the problem I have with it is, I have to pay for that up front and have to factor it into my design immediately. This also combines with the fact that the namespace is very flat with no heirarchy, so, choosing good public names is something I feel like I spend way too much time on.

Go is the only language that causes me to pull out a thesaurus when trying to name methods and struct members. It's kinda maddening. Although, after going through this exercise, I end up with code that reads like English. I just wish I could refactor my way into that state, rather than having to try to nail it up front.

[lanstin]

Choosing names is something that often is in the bucket of oh I wish I had thought a little more before sharing these names.

[aatd86]

>I just wish I could refactor my way into that state, rather than having to try to nail it up front.

Procrastination looms. :o

[bbkane]

ChatGPT is really good at suggesting 20 names for <vague description of thing>. Try it out!