4 ms·
The top answers are fine, but I would also like to add naming projects. Nothing kills actual productivity like stopping to name a repo or a folder or something
by ionforce 12y ago
The top answers are fine, but I would also like to add naming projects. Nothing kills actual productivity like stopping to name a repo or a folder or something silly. Lately I've been trying to "go literal" as a way of making it over this hump, but goddamn do I love a good code name.
Codely? Codester? Codr? Namingway? Namegame? Codeboss?
- erikig 12y agoActually just picking useful names for variables, field id's, application sections etc is another huge time-sink.
- ionforce 12y agoYou know, I hear this a lot, but I don't believe it. Generally, if a variable is to store a service, I call it `service`. If it stores a factory, I call it `factory`. I find the space of variable names to be much less confusing and more straight forward. Unless we get to weird code wankery things where the variables don't represent real things but like mechanics. But that's far and few between. val worldDestroyer = summonMe()
- meowface 12y agoI spend way too much time on this too. Unless I can think of a pun or rhyme that clearly works semantically, then I almost never bother with "cute" names like that and just go either with unrelated nouns, or a boring description ("[thing]-finder") as a name. On a side note, what is with all these startups naming their companies "noun-ly"? I find it kind of disjarring, nonsensical, and even annoying. At least the "twttr" type names I can sort of understand.