Patryk and Wojciech share their favorite less-obvious developer tools they use regularly, focusing on tools that genuinely improve day-to-day work rather than the usual basics like terminals or password managers.

CleanShot X — their go-to app for screenshots and screen recordings, with strong annotation tools, scrolling capture, OCR, webcam overlays, and easy cloud sharing.

Clop — a handy companion for compressing and downsizing screenshots and videos, especially useful for keeping GitHub PR attachments under upload limits.

MonoLisa — a paid coding font they praise for readability, personality, and overall developer experience.

scrcpy — recommended for Android development because it mirrors and lets you control a real Android device from your desktop, making testing much more convenient than relying on an emulator.

Proxyman — their preferred proxy/network debugging tool for inspecting, modifying, and simulating API traffic in mobile apps.

Tuple — highlighted as a strong remote pair-programming tool because both people can interact directly with the shared machine, making reviews and collaborative debugging smoother.

Kaleidoscope — recommended for comparing text, code snippets, and images with a much nicer experience than older merge tools.

DevCleaner for Xcode — a useful Mac utility for reclaiming disk space by cleaning old Xcode caches, SDKs, and derived data.

Objective-See tools — especially LuLu, BlockBlock, and KnockKnock, recommended for monitoring outgoing connections, persistence attempts, and suspicious startup items on macOS.

Reactotron — a long-running favorite for React Native debugging, appreciated for stability in a tooling ecosystem that changes often.

👋 Visit us on https://brainsandbeards.com/

Key Moments

Defining end-to-end tests: The hosts clarify that true business end-to-end flows go far beyond what mobile teams can actually test, so the “ends” are usually artificially limited.

How they’re supposed to work: Tools like Detox or Maestro automate UI taps through accessibility labels, running flows on simulators or devices.

Why they fail: End-to-end tests are flaky, slow, expensive to run, and often break due to infrastructure issues rather than app logic.

High maintenance cost: Teams commonly spend 10–20% of engineering time on setup, debugging, and unreliable failures—often with little real value.

What they can be good for: Tracking performance (e.g., startup time) and generating automated screenshots for design review.

Why they don’t catch UI issues: Tests only verify tappability and flow—not layout, appearance, or subtle bugs.

If you must use them: Cache aggressively, learn your tool deeply, and write tests optimized for reliability, not full coverage.

Big picture: For most teams, end-to-end tests provide poor ROI; solid architecture and good communication usually solve the real problems better.

👋 Visit us on https://brainsandbeards.com/

Key Moments

Onboarding & docs are weak: They highlight that JJ’s official website has limited documentation, there’s no clear “I’m a Git user, how do I switch?” guide, and the flexibility of many possible workflows can be overwhelming for newcomers.

Tutorials that stop halfway: Wojciech describes learning JJ via Steve Klabnik’s tutorial (great for basics and GitHub PRs), but notes it stops at a “to be continued” point and doesn’t cover advanced workflows like stacked PRs or mega merges.

Rebase is harder to discover: Wojciech explains that he frequently has to look up how to “rebase” his feature branches in JJ, because the commands are less obvious than in Git and official docs feel more like technical references than user tutorials.

AI help is hit-and-miss: They mention that asking AI tools about JJ used to produce outdated or incorrect commands; it’s improved, but still tends to lag behind JJ’s latest versions.

Powerful primitives, missing batteries-included UX: JJ gives very low-level, powerful tools (like refsets and named bookmarks), but many higher-level conveniences are missing, forcing users to copy snippets from Discord or write custom commands (like tug to move bookmarks).

Refsets are strong but complex: Refsets are described as a powerful language for describing revision sets, but way too advanced for beginners; newcomers shouldn’t be forced to learn them in their first months just to get common workflows.

Bookmark and branch friction: Because named bookmarks in JJ effectively stand in for Git branches, users must manually move and update them, which can feel as clumsy as moving tags in Git unless you script it yourself.

Tagging still done in Git: Wojciech shares that for release tagging he still drops down to raw Git commands, since he doesn’t have a smooth JJ-based tagging workflow.

GitHub & divergent commits: A big pain point is that when pushing/pulling from GitHub, commits may get different IDs, resulting in “divergent changes” that JJ can’t automatically reconcile, so users must manually pick which ones to keep.

Ecosystem still catching up: They mention tools like Tangled and an unreleased JJ-focused hosting platform being built by core maintainers, hoping it will be for JJ what GitHub was for Git.

Performance & features on large repos: From community feedback, they note JJ can be slower on very large repos due to tracking every file change, and features like workspaces aren’t supported yet.

Interactive rebase vs JJ workflows: Some users miss Git’s powerful interactive rebase that can reshuffle many commits at once; in JJ similar effects often require more manual work or complex refsets, though many gaps already have open issues and planned improvements.

Real-world experience is still positive: Despite the rough edges, both hosts say working with GitHub is still nicer through JJ than pure Git, especially when checking out others’ branches and avoiding git stash/cleanup chores.

Maturity and trade-offs: They frame JJ’s current state as “growing pains” of a young tool (v0.33), with drawbacks that are small compared to the benefits for their everyday work.

Closing encouragement: They stress they’ve been JJ-only for months, recommend listeners give it a try alongside Git, and suggest re-listening to the previous positive episode or watching their Brain Picks YouTube video for a more enthusiastic, hands-on view.

👋 Visit us on https://brainsandbeards.com/