My 20 year career is technical debt or deprecated

    When I was a King and a Mason - a Master proven and skilled 
    I cleared me ground for a Palace such as a King should build. 
    I decreed and dug down to my levels. Presently under the silt 
    I came on the wreck of a Palace such as a King had built.  

    There was no worth in the fashion - there was no wit in the plan - 
    Hither and thither, aimless, the ruined footings ran - 
    Masonry, brute, mishandled, but carven on every stone: 
    "After me cometh a Builder. Tell him I too have known.   

    Swift to my use in the trenches, where my well-planned ground-works grew, 
    I  tumbled his quoins and his ashlars, and cut and reset them anew. 
    Lime I milled of his marbles; burned it slacked it, and spread; 
    Taking and leaving at pleasure the gifts of the humble dead.  

    Yet I despised not nor gloried; yet, as we wrenched them apart, 
    I read in the razed foundations the heart of that builder’s heart. 
    As he had written and pleaded, so did I understand 
    The form of the dream he had followed in the face of the thing he had planned. 
      
         

    When I was a King and a Mason, in the open noon of my pride, 
    They sent me a Word from the Darkness. They whispered and called me aside.
    They said - "The end is forbidden." They said - "Thy use is fulfilled. 
    "Thy Palace shall stand as that other’s - the spoil of a King who shall build."

    I called my men from my trenches, my quarries my wharves and my sheers. 
    All I had wrought I abandoned to the faith of the faithless years. 
    Only I cut on the timber - only I carved on the stone:
    "After me cometh a Builder. Tell him, I too have known."

Infinitely configurable and extensible system that can accommodate any workflow and any process that comes to mind.

It can be used and also misused, but blaming Jira for its misuse is like blaming Lisp because it's too flexible and too powerful.

The IDE that's written in Java most likely shares nothing with Java ecosystem parts they "hate" (I'm guessing all of the EJB, applets an general 90's Java enterprise stuff). Only irony here is you thinking it is.

The 90's Java was a thing to hate. Running fat complex app server with bunch of code-as-XML for configuration just to run simple API app. IDEs are not doing that (althought Eclipse was a bit of a monster of glued in parts)

> Did anyone in the mid to late nineties / early 2000s really discover Java and Java applets and thought: "Java applets is the tech that'll catch on, I'll invest in that" and not invest in Java itself?

...entirety of management it seems, it was the most popular hammer for the problem for quite some time in enterprise. Hell, we still have some less than decade old servers needing java applets for KVM

.NET and C# are heavily used, so is SAP and other corporate proprietary stuff. Enterprise customers prefer entrenched players that own the whole stack.

No, it's just a fucking product you made. The fact it has to be maintained doesn't mean it is "debt", it's just like any other asset.

You don't get to your car and think "that's technical debt". There is nothing technical about it. It's a tool with maintenance needs.

The difference is choosing worse now to get it faster, that's technical debt.