I read a piece that I wish I'd saved that suggested that one of the reasons programmers often have better experiences with computers is we've internalized what is likely to be the well-trodden path and we stay on it. Hence we encounter mostly smoothed edges. The same article postulated that some programmers don't internalize this, and they encounter bug after bug, the same way Zed does.
Oh, and this. A million times this:
I don’t fucking work for you. I’m not going to waste 15-30 minutes
navigating your bullshit bug tracker, filling out every random
Jira/Bugzilla/Confluence/AgileXPHardon12000 tracking data point just so you
can ignore me.
I suffer from this syndrome. I can break anything in 5 minutes just by using it my way. I have "power user" setup (wrapping scripts, custom environment variables, etc.), and my own ways which collide with any shortcomings, hacks and ignorance software has. Part of the reason I'm such a Python hater. Python ecosystem is so broken and ignorance flourishing that anything-Python breaks 99% of the time. Before using any new software I check if it was written in Python, and if I can find an alternative written in something else.
If you want an example on what I'm talking about, just create Linux user with a space in the name of home directory, try working as it this user, and watch the world burn.
I have a nasty habit of saying to myself "What if I do it this way instead?" and I end up breaking things. The problem is I know how software should behave so I purposefully go against the grain to see how it handles situations.
I find satisfaction in breaking software and finding bugs. If it allows for user input - I will try to break it.
