User interview: terminal-first workflow feedback
Participant
The interviewee is a backend engineer who works almost entirely from a tiling window manager on a Linux desktop, with the editor, build watcher and logs in three fixed panes. They follow the platform team's changelog through Fernpost, which is where they first hear about breaking releases and where most of their questions to the maintainers get answered.
Likes
The participant volunteered four positive themes:
- Cross-platform parity — the CLI behaves identically on their laptop and on the build runners, so scripts move without edits
- Open feedback channels — values both the scheduled research calls and the ad-hoc threads that maintainers reply to within a day
- Call quality on Linux — noted that Loomcall is the only conferencing tool that shares a single window reliably on their setup
- Team-specific rooms — prefers narrow discussions with the team that owns a surface over broad, company-wide announcements
Dislikes
No specific dislikes about the product were raised during the interview.
Pain points
- Discovery is single-threaded — relies almost entirely on Fernpost to learn that a research session is open, which means a quiet week there reads as no activity at all
- Docs lag the release — migration notes usually land two or three days after the tag, so the first attempt is guesswork against the changelog