I try to train my systems to behave just the way I like them. It's no different than coding: you are bending tech to your will. I don't see the difference in configuring a brand new Virtual Machine and that of coding a new piece of software. For me, the definition of non-sucky technology is the ability to configure, tinker, and otherwise mess with systems to make them do your bidding.
This is why I love computers, because no two computers are in the same state, and I always laugh using other people's computers because you can be sure they have configured it in a weird idiosyncratic way, entirely different than one's own configuration.
The definition of non-sucky technology is not having to waste time on any of that.
If you think tinkering and configuring are fun you should stay as far away as possible from software design, because you have no insight into what most users expect from tech.
> If you think tinkering and configuring are fun you should stay as far away as possible from software design
You overlook that not giving the user options to configure their systems is bad practice as it can force all manner of dark patterns on them, and they are left constrained in that software, unable to bend it to their will. Let them tweak, I say!
This is why I love computers, because no two computers are in the same state, and I always laugh using other people's computers because you can be sure they have configured it in a weird idiosyncratic way, entirely different than one's own configuration.