I switched to zellij, but I made more like my tmux was because I didn't want to learn new binding; C-q activates tmux mode. C-q + g locks so I can pass through comamnds to inner zellij. C-g unlocks. on super+enter for it opens a ghostty it and atached it to zellij session named $(hostname).
On reboot it remembers my tabs and panels and even commands that ran inside last (i.e there is popup in every panel that had something runing to run it again or just open a terminal)
Before my great wayland migration I ran patched st and it was great. Terminal job is render what terminal multi-plexer gives it and passes input to multiplexer.
You use MCP to provide dumb-down API that LLM can consume. It's not that hard. If you MCP server is 1:1 map to your REST - you're doing it wrong.
Then there things like browser-mcp and some tools you make yourself to make workflow easier (adding self-describing MCP is easier than telling agent about your CLI tool in some markdown file that LLM forgot about 20k tokens ago.
- write a test for method that does not exist, it just calls the method and nothing else
- write method that does nothing
- add/extend test that uses that method <-- this very loop starts
- modify method until tests passes
- go back to loop start until you're done
I always hated it. When I work with LLM i first massage interface that tests, then tests, then implementation until all these tests pass.
> for example when it re-outputs the complete file when you ask for a tiny change).
well with sonnet 3.5 and 4.5 (can't say about 4.6) it often will get stuck in a loop trying to update just the required parts and iether waste tons of tokens doing these updates or waste tons of tokens to a point where restring file from git is required. Tokens get wasted regardless.
I like tests, but I don't bother with TDD because it's so ceremonial. I design the API, or at least sketch it out (using a whiteboard or drafting some notes, and doing research). Then I iterate and refine. I only bother with tests once I can commit or when it's no longer viable to tests manually (edit-compile-run cycle). And a lot of time I follow the table pattern.
When it comes to graphic content on the internet I usually consume it's for entertainment purposes. I didn't care where it came from before and don't care today either. Low quality content exists in both categories, a bit easier to spot in AI generated, so it's actually a bonus.
On reboot it remembers my tabs and panels and even commands that ran inside last (i.e there is popup in every panel that had something runing to run it again or just open a terminal)
Before my great wayland migration I ran patched st and it was great. Terminal job is render what terminal multi-plexer gives it and passes input to multiplexer.
reply