In this episode of Brains & Beards, Patryk and Wojtek share why, after more than a decade with Git, they’ve switched their daily work to a new version control system called JJ (Jujutsu). They explain how JJ can sit on top of existing Git repositories, letting you use it even if your whole team stays on Git and GitHub, and why concepts like the operation log, easy undo/redo, and working with “changes” instead of “finished commits” feel much more natural to developers. The hosts walk through quality-of-life improvements such as effortlessly jumping between branches, editing old changes, splitting work cleanly, and avoiding painful tools like git stash and complex rebases. They also touch on the current limitations and dreams of a future “JJ hub”.

The podcast discusses various types of documentation for software projects, including documenting code and external documentation. It explores what should be documented within code comments versus other approaches like TypeScript. Maintaining outdated documentation is an issue, so validation through tests or expected errors is preferable. External documentation like readmes should link to other sources rather than include details likely to become outdated. Architectural decision records are recommended to explain important design choices. The discussion also covers establishing a domain language to reduce ambiguity and standardizing terminology between teams. Overall, the podcast emphasizes writing documentation that remains useful over time rather than just explaining code.

The podcast discusses the responsibilities of a mobile development team and how they differ from teams that only focus on writing code. Mobile developers can play an important role by providing expertise on mobile design patterns, technologies, and best practices to help other teams. They also need to work closely with backend developers to ensure APIs are optimized for mobile and address issues like battery life. In addition, mobile teams can help with testing, deployment automation, and even building internal tools to speed up their work. The podcast emphasizes that mobile developers should act as advisors and not just code contributors if they want to fully utilize their skills and provide the most value to their organizations. It highlights how mobile expertise can influence product design and strategy in ways that benefit both business and users.

In this episode, we will explore what Patryk and Wojciech have on their desk for fun and profit. And maybe they will even lift the veil of secrecy of what is hiding under their desks 😱 Socking news!

In this episode Wojciech will tell us about a new course he is preparing for us all. It’s called Maintainable React Native. Enjoy!

In this episode, we're talking about different ways you can distribute test builds of your app to other members of your team, from very simple setups to elaborate workflows for product teams in larger organizations.

We discussed today Code Reviews and looking into its missed opportunities ᕕ(ᐛ)ᕗ

Today we talk about a tool no mobile project should miss, and its limits.

Today we discuss our most "favourite" technology, the Pre-Commit Hooks. Do you agree? Or you want to change our minds?

Let's agree to disagree. Coding tests are something many of us have to face, a few of us like them. In this episode you can hear our angle (-s) on the topic. What's your opinion?

Did we learn anything about getting things done in the last 15 years of professional life? Well, judge it yourself. ᕕ(ᐛ)ᕗ

Will the webviews save you implementation time, or cause headaches down the road? This episode will tell you where webviews are safe to use and where the dragons are 🐲

Today we discouse how the backbones of our projects looks like. Are you curious what are the most helpful libraries we are using in 90% of our work? How to set up Typescript in your project the right way? Tune in for our top picks ᕕ(ᐛ)ᕗ

In this episode we discuss code sharing between web and mobile apps written using React. We talk about what can be shared and what can't, about different tools to do that, and workflows that various teams use. Finally, we share a secret technique that's much easier to implement that code sharing, but still gives you most of the benefits. Listen carefully!

We discuss in-depth different strategies for sharing a test builds (development snapshots) of your mobile app with the rest of the team for QA and validation purposes. Starting with techniques for small teams / solo-developers, up to enterprise techniques for big organisations. We talk about how, why, techniques and workflows.

We discuss the advantages of using TypeScript over writing plain JavaScript, why not everybody does that (yet!) and how to fix that. We also discuss common problems, type-driven development, and share our favourite techniques of using types in a React Native codebase.

Estimating software is inherently difficult. In this episode we talk about things we commonly forget about when being asked to do that.