4 ms·
What we used to do is announce in our team chat: "anyone around for a round of bikeshedding? I need to name a thing". The thing being named is usually not use
by omoikane 3y ago
What we used to do is announce in our team chat: "anyone around for a round of bikeshedding? I need to name a thing". The thing being named is usually not user facing, so it was more of a team building exercise than anything related to compliance or style. We would get it done in a few minutes and never discuss this name again, because we already had this discussion.
The actual names that came out of these exercises are generally pretty good, and often a shorter name would win over a longer one.
- JohnFen 3y ago> "anyone around for a round of bikeshedding? I need to name a thing" I have to come up with many names for things in code every day. I can't imagine the slowdown having to workshop every name would incur...
- Shaanie 3y agoI'm sure the names have different importance, though. A local variable name in a small method probably barely matters, whereas the name of a variable in a widely used external API matters quite a lot.
- omoikane 3y agoThis is the kind of exercise can be done in the background while waiting for stuff to compile. It's also not for trivial things like private or local variables and such, so not really a frequently occurring speed bump. An example would be a set of enum names that I need to share with my teammates, where it might be a lot of hassle to replace them all if we don't decide on proper names now, but any set of names would work.