This is what I and many other programmers have done (not the removal, but fake delays), because it improves user experience, actually:

1.When the user clicks a button that should take long in their mind (like uncompressing a zip file etc) but is actually fast, it might seem like something is wrong and it didn’t work

2.When the user transitions between layouts of the application, if it loads everything too fast it will look too abrupt, a fake delay will be made here if a transition animation is not possible/doesn’t fit

I’m kissing all of the tummies and you can’t stop me ~unless you don’t give consent~

Mechanical keyboard. Almost had no money back then, but wanted to treat myself. It costed 100$, and I regretted it the next morning. Felt like shit, but it was so cool to type on.

After 5 years, this metal-frame keyboard managed to survive many outside gigs, long travels, literal war, and it’s still with me. And I still love typing on it. Sometimes I code just to type. You can guess why I don’t use code completion tools.

With thighs

It’s called amd64 because AMD invented the x86-64 processor instruction set, it works both on Intel and AMD