71
results for "naming is hard"
-
the workflow is part of it but the real hard part is naming things
trwnh
at
2025-03-23 20:35
-
File under "naming things is hard": I'm trying to come up with good names for blocks outside of the main content of my pages. I thought maybe I could borrow vocabulary from book publishing, the there's too much overlap with web vocabulary where the overlapping terms mean different things.
btrem
at
2025-01-17 00:32
-
naming things is hard!
[snarfed]
at
2024-12-17 22:01
-
lol naming is hard
[tantek]
at
2024-11-21 17:03
-
no we do not, because naming the problem is perhaps the hard thing that we (and others) have been stuck on.
[tantek]
at
2024-06-06 17:58
-
[snarfed] naming is hard in that way, when you make names too abstract, they lose their connection to the underlying thing.
[tantek]
at
2024-01-12 06:46
-
naming is hard 🤷
[snarfed]
at
2024-01-09 20:59
-
ok, I added "Criticism: wastes too much time compared to actual utility (for both library creators/maintainers, and clients). OOP encourages lots of time to be spent (wasted) with setting up a ton of boilerplate files (naming is hard), classes (naming is hard), methods (naming is hard), hierarchy (information architecture is hard), when a flat set of functions would suffice for 90%+ of use-cases, and the best way to discover that other 10% is to" to the "See Also" section of /object-oriented-programming-antipattern https://indieweb.org/wiki/index.php?diff=91774&oldid=88663
Loqi
at
2024-01-01 21:52
-
OOP << Criticism: wastes too much time compared to actual utility (for both library creators/maintainers, and clients). OOP encourages lots of time to be spent (wasted) with setting up a ton of boilerplate files (naming is hard), classes (naming is hard), methods (naming is hard), hierarchy (information architecture is hard), when a flat set of functions would suffice for 90%+ of use-cases, and the best way to discover that other 10% is to
[tantek]
at
2024-01-01 21:52
-
OOP encourages lots of time to be spent (wasted) with setting up a ton of boilerplate files (naming is hard), classes (naming is hard), methods (naming is hard), hierarchy (information architecture is hard), when a flat set of functions would suffice for 90%+ of use-cases, and the best way to discover that other 10% is to start flat and then only add hierarchy when the flat set of things gets too large and you need some "chunking" to make it
[tantek]
at
2024-01-01 21:50