News for hackers. Stuff that matters.
Re:How to name things: the hardest problem in programming (2... by ardit33 on Tuesday June 20, 2017 @05:19PM (#14598706)
That's why almost all IDEs have "renaming" a class as a feature.

I'd say roll with whatever name comes first, as you can always change it later. Dwelling too much with it can be a sign of perfectionism.... or procrastination, or ADD.... or just in-experience.

As I got older and had more experience "naming" things stopped being a problem, as I always knew I could change things later on, and trying to be perfect on first shot is futile.

Thinking of programming as an essay that will need some editing/revisions when done, helps a lot.

Re:How to name things: the hardest problem in programming (2... by Omnius on Tuesday June 20, 2017 @05:27PM (#14598775)
"I'd say roll with whatever name comes first, as you can always change it later. Dwelling too much with it can be a sign of perfectionism.... or procrastination, or ADD.... or just in-experience."

-- I will take "things i will never do" for a 100 Alex.

Re:How to name things: the hardest problem in programming (2... by AstralStorm on Wednesday June 21, 2017 @03:40AM (#14601712)
And then you end up with the eternal TO-DO. Congratulations.
Re:How to name things: the hardest problem in programming (2... by Omnius on Wednesday June 21, 2017 @11:05AM (#14604387)
I was trying to be funny but the point i was making is that "i'll fix this later" just leads to a ton of technical debt that usually doesn't get fixed.

In this one specific example being paralyzed about naming something is silly.