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"

  • 2
    It is normally just called a placeholder. – Chenmunka May 30 '17 at 11:32
  • 1
    "Vaporwear" is a common term, though not with precisely the above meaning. – Hot Licks May 30 '17 at 11:36
  • 1
    @Chenmunka : placeholder does not carry the connotation of deferring. The word instead should mean "something that is not to be touched until its time comes." @ Hot Licks : I could not find "vaporwear" meaning on Internet, can you please explain it a bit more and perhaps cite some source too – harshvchawla Jun 1 '17 at 4:50
  • Really. You couldn't find the Merriam-Webster definition. Or the AHD definition. Or the Wiktionary definition. Or the Oxford Dictionaries definition. Or the Dictionary.com definition. Or the Wikipedia article. What version of the Internet are you using? You need Web 2.0 or higher. – RegDwigнt Jul 21 '17 at 4:05
  • 1
    Could you give a more concrete example of what you are asking for? Some well known case from the industry would be perfect. Depending on the context, not wasting any human resources on a feature that no one would probably ever need may be either wise management or utter lack of foresight. – undercat applauds Monica Jul 21 '17 at 7:14

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"


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.)

  • "Let's not borrow trouble" is a good expression (new one for me atleast) but it gives the 'future' feature a 'problematic' connotation. Sure coding it right now will thus be problematic to current project planning but that is an 'implication' and not the 'action' Project Planning, however, is a very broad-spectrum antibiotic though I am just looking for a thermometer :) I might as well rephrase what I intend to articulate about the feature - "this feature is not important as of now so we will code it when its time comes". – harshvchawla Jul 21 '17 at 4:06

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

  • 1
    In your question, did you mean deferring the implementation of a feature (thus saving human resources), or deferring the loading of said feature into computer memory (thus saving RAM and CPU)? Lazy loading only applies to the latter. If a feature was not implemented because no customer has asked for it, that is NOT lazy loading. – undercat applauds Monica Jul 20 '17 at 20:03
  • @undercat: I see the light in your point. I have marked my answer "unaccepted" again :( – harshvchawla Jul 21 '17 at 3:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.