piekvorst

Primitive technology, modern look

~ is a design mistake.

Nice text editor

Doesn’t the act of reaching for the mouse actually creates a natural moment of wrist relaxation? A fixed wrist position creates static muscle tension.

It’s unfortunate that we can’t settle on an icon set for at least a decade. Constantly changing the icons misses the very point of their function: instant recognition.

This is partly why I’ve escaped to text-only interfaces and monochrome icons wherever possible. Granted, it’s not ideal, but sticking with the icons offers no advantage.

Not just a Futurama reference

English being my language of choice, but not my first language, I got 75/100. Performance breakdown: 18/20, 18/20, 11/20, 18/20, 10/20.

(My first language is Russian.)

The bottleneck, in my case, was indeed the poorly designed GUI of JetBrains and VSCode versus CLI. By migrating to CLI, I have abandoned intelligent queries as well. This project seems like a bridge: it preserves CLI, but restores the queries.

This is a promising road that I would probably not take. I have learned to live with simple per-line regular expressions. I have never felt that they slow me down.

In fact, the opposite is true: they let me craft fuzzy queries clearly, i.e., to balance the fuzziness across the query. I’ve never learned to do that with the black-box intelligent queries, which severely limited my scope in the past.

The icon is traditionally small indeed, but it shouldn’t be. I use the strings “vol-“ and “vol+” as icons, which makes the whole thing 8 characters long.

As a universal law, optimizing the fullscreen experience is a suboptimal goal. Generally, the best solutions are the ones that operate at the appropriate level, and if we optimize the fullscreen experience, then most solutions built for the right level are inaccessible to us.

Instead of using a single menu bar icon “volume control,” I have transferred the lessons of the keyboard to the GUI and placed two buttons in my menu bar: volume down and volume up. I have been using them all the time for about half a year now.

The benefits of this approach, to my knowledge and estimation, include: no waiting for a slider to appear; no nested actions; no need to read the current value; each click does not depend on the current state; Fitts’ Law muscle memory boost (the buttons are effectively infinite-height targets); discoverability compared to scrollwheelable icons.

Thank you for busting the myth of worker self-management.

The social engineering thing runs deep. For example, if you grep for “Key” method, chances are the type/class name would stand on the same line. This is the case in Go and, I think, in many other programming languages (ironically, not C).

Lines are a fundamental building block of text and it’s not unreasonable to optimize them.

)

I have always used traditional grep to search codebases. It serves me better than an IDE when there’re lots of scattered and frequent queries.

grep’s design is surprisingly winning, exceeding expectations to this day.