Whiteboardcoder

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.

Bulk layoffs do not save money. The long-term impact on employee engagement is measurable and significant, and that doesn't even consider the loss of institutional knowledge and not having enough people around to meet demand. That lack of engagement multiples the lost productivity. Even worse, a workplace is a social organization. Some boss stripping away your friends has a serious impact in and of itself. It's cruel to everybody, both those who are pushed out and those who remain. Nobody will "bounce back." [linkedin.com/posts/fresiajac…]