QQ: In Slack people refer to the practice of having one BUILD file per directory as "111". What does the 3rd "1" represent? I assume the first two are "1 BUILD file:1 directory" but I don't know what is implied by the last 1.

I think I coined the phrase 111 back in the day at Foursquare, and to be honest I don't remember...

hmm, with parameterized targets that's definitely violated 😄

True, this was coined like 10 years ago, before any of that was a thing

heh

Wasn't there someone who found a quote about 111 in a book last year? Was that maybe you @fresh-cat-90827 ...?

maybe we should rebrand it?

Fwiw I didn't find "111" in the docs on readme

Should we mention this somewhere in the docs, since "111" is out there in ether?

I don't think so -- I doubt our everyday users are reading this book hah. We already have so many concepts to learn, no need for new jargon

Josh hadn't read the book but somehow had been exposed to the term...

only from our Slack because the old-timers (Stu, Benjy, and me) still sometimes use it

If it's going to continue to come up, it'd be good to have it defined somewhere where Slack observers can find it. Otherwise it feels like exclusionary jargon.

i'd bias towards us 3 learning to stop using the phrase then

This is also a fair approach

it's not really necessary to express the idea, and none of us know what the third

:1

is lol

According to that book, the third one is 1 target, which is definitely not a recommendation these days (at least not for python)

I found it in the old v1 docs! 😛

Many programming languages (E.g., Java, Python, Go) have a concept of a package, usually corresponding to a single filesystem directory. It turns out that this is often the appropriate level of granularity for targets. The idiom of having one target per directory, representing a single package, is sometimes referred to as the 111 rule. It’s by no means required, but has proven in practice to be a good rule of thumb. And of course there are always exceptions.

https://v1.pantsbuild.org/build_files.html

Ah, one target, one directory, one package

I've long hated that use of the term "package", but that does make sense in light of how Java and Python use that word