https://brainsandbeards.com/

Key Moments:

• Documentation comes in different forms like code comments, README files, external documentation in Confluence, and architectural decision records (ADRs).
• Code comments can become outdated over time as the code changes, so it's better to rely on clear naming, TypeScript types, and unit tests to document code.
• README files should focus on project-specific setup instructions rather than general language/framework documentation, and link to external docs when possible.
• External documentation is better suited for business context, team decisions, and diagrams that involve multiple teams. It's easier for others to contribute to compared to code docs.
• Using a shared terminology ("domain language") is important for communication between teams working on the same codebase or product. This vocabulary should be documented.
• ADRs are useful for documenting past architecture and design decisions in case they need to be revisited. They improve decision making and prevent rehashing the same discussions.
• Writing documentation forces one to better understand a topic. Developers should practice writing to improve their communication and learning.
• Tests can double as a form of documentation, like regular expressions explained through example test cases.
• Commit messages should be concise and avoid too many changes in one commit to allow for informative messages.
• TypeScript's "expect error" is better than "ignore" for documenting expected errors in code.

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

https://brainsandbeards.com/

Key Moments:

• Mobile development teams have responsibilities beyond just writing code, such as providing guidance on design, UX, platform best practices, and APIs.
• Mobile developers should proactively communicate with other teams like design, product, and backend to ensure mobile needs are met.
• Designers may not be aware of mobile constraints, so developers should point out issues and suggest better solutions.
• Developers add value by understanding business needs and constraints around payments, analytics, and security rules.
• Developers should help educate other teams on the latest mobile changes to avoid outdated approaches.
• APIs need to consider mobile use cases around battery life and offline usage.
• Versioning, deprecation, and error handling are especially important for mobile APIs.
• Automating workflows can save significant time spent on manual tasks.
• Mobile teams can build internal tools and services to streamline their work.
• Change logs and release notes should have useful information for users, not just be technical.

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

Find us on https://brainsandbeards.com/

• The hosts discuss their daily work setups and what equipment they use, including standing desks, laptops, external monitors, headphones, microphones, and other accessories.
• One host uses a standing desk to avoid sitting for long periods and stays engaged by walking while in meetings or working.
• Their laptops of choice are MacBooks for iOS development. One also uses an iMac Pro but it has started freezing.
• Other items mentioned include pens, a Rubik's cube for focusing, an external SSD for extra storage space due to limited internal storage, and a cloudlifter microphone amplifier to reduce noise.
• A mechanical keyboard is used for programming tasks, with custom key mappings for shortcuts.
• An external hard drive is used for video editing projects and backups due to large file sizes.
• A multi-channel audio interface and microphone setup provides easy, high-quality and noise-free podcast recording.
• A separate webcam is used for higher quality video calls compared to laptop cameras.
• Photos and decorations on the desk provide smiles and breaks from work.
• The hosts discuss focusing on technical development tips or sharing more of their work environments and setups in future episodes based on listener feedback.

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