So, I've coined new term to completment the notion of "technical debt": technical malfaesance. I put the following in that category (this is not an exhaustive list):

* Deliberately writing garbage code to "get it out the door faster."

* Deliberating writing garbage code, saying "we'll fix it later."

There is "intentional technical debt," but that's more along the lines of using a flat file with key/value pairs rather than a real database because we don't have enough customers to justify the work. The implementation is high quality, but we know in our hearts that it's insufficient in the long term. Deliberately writing sloppy, buggy code is malfeasance.

Related to the above is:

* Agrandisement-driven design: Writing code (selecting tech) only to pad our résumé.

* Ego-driven design: Elevating our "cool idea" over the needs of actual customers, often with the platitude "the customers will love it." No, they won't.

Source: x.com/allenholub/status/1847684168987164745