undefined | Better HN

0 pointsthaumasiotes3y ago0 comments

> Codenames is the equivalent to call your variable John.

Imagine that you have a singleton object floating around your system, every single function written anywhere in the system must interact with that object heavily, and as a consequence everyone is familiar with what the object does and where it's defined.

What problems do you think might arise if that object were named "John"?

0 comments

2 comments · 1 top-level

hourago3y ago· 1 in thread

That each new developer needs to learn that name. That it's difficult to understand what is that variable scope: does this new functionality fit in John or not. That most people know John but what happens with that other one that is rarely used named Jack and you find in in the code, and Anna and Maria?

It would be the same for the computer running the code, the problem is for the developers trying to understand how to use it, how to expand it, etc.

thaumasiotesOP3y ago

Let me rephrase: what problems might arise that wouldn't be just as bad if a name other than John was picked?

Everything you list is potentially a problem, but not a problem that got worse when we named the system John.

j / k navigate · click thread line to collapse