As I used to be having a dialogue with another designers and engineers on my staff, it occurred to me that there are sometimes turns of phrase we use that outsiders would possibly discover odd. Listed below are just a few I may consider:
The place does X dwell?
Once we ask the place one thing lives, we’re often asking the place we will discover a explicit file, asset, or operate inside the entirety of the belongings, scripts, code, and many others. within the mission. Relying on the context, the reply might be a single file, a folder inside the mission tree, a line in code or script, or one thing else.
“X land” (e.g. “That operate lives in C++ land”)
The final a part of the mission that handles a specific factor. Associated to the place issues “dwell”, a “land” is a extra generalized location. If a specific little bit of logic lives in “script”, it could ship messages to C++ land – that’s, a specific little bit of script could name C++ features. Telling somebody that one thing “lives in X land” means they received’t discover the definition the place they’re trying, and offers some context as to the place to look.
Damaged
This really has nothing to do with recreation stability more often than not. 9 occasions out of ten, “damaged” implies that the latest model of the sport ({that a} explicit individual pulled) doesn’t work for some motive, often as a result of some mixture of the checked-in information and belongings trigger both a crash or arduous lock someplace. Normally that is due to anyone forgot to examine a typical case, or forgot to examine in a file together with the others. Being damaged is the worst state for anyone to be in, since they can not work. If many individuals on the staff are damaged, it’s a fireplace that wants preventing.
Firefighting
Engaged on sudden excessive precedence duties that aren’t a part of the usually assigned workload, typically to assist different devs who’re damaged get un-broken.
Blocked
Not fairly the identical as Damaged, blocked simply implies that a process has a dependency that hasn’t been accomplished but. If all of somebody’s duties are blocked, they’re successfully damaged.
Downstream/Upstream
A lot of the time, now we have to work in numerous branches of a specific depot – particularly if we’re engaged on content material that can go dwell in numerous content material updates. When adjustments from one department are built-in to a different department, the goal department is “downstream” from the supply department, which is “upstream” from the goal department. Normally in these conditions, the vast majority of the integrations are one-directional for the reason that upstream department wants to keep up stability so it doesn’t take the riskier and fewer secure check-ins from downstream.
Discuss/Take it Offline
This really means “let’s talk about this later”. Normally used to desk a dialogue on a subject introduced up at a gathering so we don’t waste the time of different folks on the assembly who aren’t concerned.
X Full
This implies the mission has reached the state the place the management will not settle for new Xs – options, belongings, content material, code, and many others. We are able to nonetheless repair points with, tune, and iterate on the present Xs we’ve began, however we can not add new Xs anymore. Normally goes within the order of function, then asset, and eventually code.
X Freeze/Lock
A extra superior model of X Full, a function/asset/code Lock implies that no checkins of that sort are allowed with out categorical authorization. The mission has reached the stage the place stability is paramount. Which means that solely particular check-ins which have been vetted by the senior engineers are allowed in. Follows the identical order as X full. As soon as code freeze is said, we’re within the ultimate stretch – the one purpose from then on is to get a submission candidate.
[Join us on Discord] and/or [Support us on Patreon]
Acquired a burning query you need answered?
