/Tips

GitHub Has Too Many Hidden Features

tl;dr: A variety of lesser-known but useful features on GitHub: (1) Pressing '.' on a repo main page opens it in "github.dev," an online VSCode instance where you can edit code, push commits, and review pull requests. (2) The "feature preview" option allows users to enable experimental features like rich Jupyter diffs. (3) Regex search is available both within a repo and sitewide by wrapping the search in slashes. (4) Keyboard shortcuts like 'Y' to change the URL from branch-based to commit-based, and 'I' to hide comments in a PR. (5) GitHub.dev can be used on other people's repos and saves work across browser sessions. (6) Labeling a backtick-codeblock as 'suggestion' in a PR comment shows it as a line change.

featured in #445

An Effective Team Communicates Much Like Optimized Code: With Clarity, Modularity, And A Focus On Simplicity.

- Addy Osmani tl;dr: “Just as we strive for optimized, clean code, our teams should aim for clear, modular, and simple communication.” Addy shares tips from his time at Google: (1) Optimize communication for the target audience. (2) Speak clearly and slowly. (3) Opt for concise messages rather than apologizing for long ones. (4) Use simple and common words. Remove unnecessary and unrelated words. (5) Avoid English idioms and slang phrases if working with a global team. (6) Use inclusive language that considers all educational backgrounds.

featured in #443

TDD With GitHub Copilot

- Paul Sobocinski tl;dr: The article explores the relationship between Test-Driven Development and AI coding assistants like GitHub Copilot. It argues that TDD remains essential even with AI assistance, as it provides fast and accurate feedback and helps in dividing and conquering problems. The article  shares tips for using GitHub Copilot with TDD, including starting with context, following the Red-Green-Refactor cycle, backfilling tests, and recognizing Copilot's limitations in refactoring.

featured in #441

Git Tips And Tricks

tl;dr: Topics covered include Git aliases for simplifying common commands, using the .gitconfig file for default settings, the --stat flag for an overview of changes, Git stash for managing changes without committing, rebasing techniques, amending commits, cherry-picking commits from one branch to another, and resetting commits. The author shares personal insights and examples, aiming to make daily Git usage more efficient.

featured in #441

Developer Workflow Tips No One Tells You About

- Justin Joyce tl;dr: “These are the tools, tips and advice I wish I had internalized when I was just starting out. Many of the details below are specific to macOS, but similar tips and tricks apply on other systems. I've broken it down very roughly into the following categories: (1) Computer setup. (2) Command-line-related things. (3) Technical but non-CS advice. (4) Potpourri.

featured in #432

Useful DevTools Tips And Tricks

- Patrick Brosset tl;dr: (1) Zoom DevTools. (2) Delete annoying overlays. (3) List the fonts used on a page. (4) Measure arbitrary distances on a page. (5) Detect unused code. And more.

featured in #427

Control, Escape, And Meta Tricks

- Susam Pal tl;dr: Various keyboard shortcuts and sequences related to control, escape, and meta keys in Unix / Linux terminals, this article covers: (1) Terminal tricks (2) Control codes. (3) Meta key sequences (4) Vim tricks.

featured in #426

CLI Tricks Every Developer Should Know

- Kedasha Kerr tl;dr: “We’ve compiled some important tricks and commands that every developer should know from GitHub’s own engineers. By mastering these basic techniques, developers can become more efficient at working with the command line and gain a deeper understanding of how the underlying operating system and programs work.”

featured in #410

I Finally Figured Out How To Take Notes!

- Sam Rose tl;dr: “I had some requirements in mind: (1) I want to tag notes, track things like date, who was there, what the key topics were, and be able to search based on tags. (2) Create action items, and be able to ask “what action items have I not yet done?” (3) It has to be super easy. I want to be able to jump into a meeting and have my meeting notes ready to go.”

featured in #407

Writing Tips for Improving Your Pull Requests

- Jeff Mueller tl;dr: “I’m going to show you how to purposely write less by using the techniques below.” Tips are: (1) Make it scannable. (2) Speak plainly. (3) Avoid adverbs. (4) Simplify your sentences. (5) Avoid a passive voice. Jeff adds examples to each.

featured in #404