At first I thought I was on LinkedIn lunatics.
I’ve lost count the number of times I’ve taken on a project because something was annoying me.
Paid engineers often don’t even want to implement anti-features, but have really no options if they wish to receive their pay
A paid skillful engineer, who doesn’t think it’s important to make that sort of a change and who knows how the system works, will know that, if success is judged solely by “does it work?” then the effort is doomed for failure. Such an engineer will push to have the requirements written clearly and explicitly - “how does it function?” rather than “what are the results?” - which means that unless the person writing the requirements actually understands the solution, said solution will end up having its requirements written such that even if it’s defeated instantly, it will count as a success. It met the specifications, after all.
This guy requirements
chiptune music plays
I bet it’s playing a song from Sonic the Hedgehog.
We know who runs the internet.
Don’t worry. Our silent guardians will always get around.
No, but do worry though. Shit ain’t easy nor food is free. Send some bucks their way every once in a while.
Ublock origin won’t take my fucking money!
Donate to the listmakers
