What is a stupid technology that is supposed to save you work that actually causes you more work?

Flaky end to end tests on every pr

Basically using the right tool for the wrong purpose, and NodeJs...

Joking about node thing, I'm just bored

Java reflection. Just don’t.

Email.

Linux

Time sheet tracking.

@ScriptCoded a flaky test is worthless and should be made non-flaky or deleted

CMDB

Microsoftware

Postman. What a fucking time sink.

HomeKit

Other people. Bad invention.

Time Estimation per ticket.

many teams just do it mindlessly because they are used to it, yet never realise it's often impossible and just ends up wasting time and arguing why the estimate was off. When you ask "what happens if this feature takes 5x longer than we thought?" the answer is often "well do it anyway, it has to get done" and at that point you should say let's just do it til it's done.

For some client projects estimates are necessary as the client demands them, but I'm saying for product companies often force it upon themselves needlessly

Clean architecture

Optimizely/Episerver

the internet.

Controversial take:
allowing some anonymous objects can save a lot of time - not having to name classes.

Especially in rare when you need to pass "partial" structures. Like you have a User class and a Subscription class but sometimes you need to pass around an object with just { user.email, subscription.name} and sometimes you need an different set of values.

I can already hear people thinking about how to extend, rename and restructure classes to prevent that need from occurring. But that shit takes so much time and getting all classes right becomes a significant mind share of the project.

Kubespray

@jiraTicket very sane remarks, I agree with ya