Programmer slang expression for "We'll cross the bridge when we get there"

Question

What is the software industry word/term/phrase for the saying "We'll cross the bridge when we will get there"?
I need to refer to a feature that can be deferred until its time comes.
For example, YAGNI ("You ain't gonna need it") is used for software features that won't be used, so they would be redundant to code — i.e. don't over-develop a feature.
Similarly, what will be a term for the feature in question? An acronym would be great, but WCBWGT doesn't quite cut it.

Update (adding example to provide more context)
The part 'not wasting any human resource' fits the bill for YAGNI. The context I meant was 'not wasting ... "yet" '
For example: Suppose your objective is to build an autonomous car that can do navigation (sprint 1), speech recognition (sprint 2), image analysis for road bumps (sprint 3) etc During design discussion in sprint 1, if someone wants to resolve or talk for resolution of cameras for image analysis - because that is clearly sprint 3, you would want to tell her "we will cross that bridge when we get there"

Vishnoo Rath · Answer

If its a defect in the Software after release, it is termed a "Feature". If it is missing from the Software in the first place, its a "Planned Milestone Feature"

harshvchawla · Answer

Update: I came across the term implementation detail and one if its interpretations - a design decision but not a concrete implementation - seems quite close to the context (perhaps like a delegated placeholder but not exactly a stub). 
Though, the nuance is "it can be implemented in different ways" instead of "it will not be implemented until its significance comes into foreground" (I guess deferred detail cuts it ...)

Maybe [Lazy Loading][2]

Lazy loading is a design pattern commonly used in computer programming
to defer initialization of an object until the point at which it is
needed.

Edit: After undercat's comment below, I realize I was not looking for Lazy loading - as that would mean the feature was coded even if not used(loaded) yet.

P.S: I am wondering now if "Lazy Coding" would be acceptable to the ears instead - neologism would work if it doesn't hurt

The Nate · Answer

Project Planning is where one partitions the system into the bits that are needed and in which order, so that's really the industry term for it.

(of course, "We'll cross that bridge when we come to it." or "Let's not borrow trouble." are often used when discussing such planning in my experience.)

Programmer slang expression for "We'll cross the bridge when we get there"

3 Answers

Add your own answers!

Ask a Question