The Rietta Blog
Utilizing two factor authentication, strong passphrases, password managers, and NIST standards; private company accounts can remain secure. Cover your assets!
When writing user stories, user stories are written; but what about malicious actors? Writing Abuser Stories pushes developers to care about security.
Git add --patch can help keep code changes relevant with their commits. When changes are unsplittable, we can use Manual-Hunk to split changes line by line.
Keep those nasty .gitignored files like node_modules/ from clogging up fzf fuzzy finder and show commited, hidden files such as .circleci/config.
Finding a tool to tame the chaos when you're new to an Agency setting and responsible for organizing "all the things".
Having a clean and focused reading channel in Slack allows us a sanctioned place for in-depth discussion and news sharing.
2019-05-09 (Last Updated: 2019-10-23)—
On GitHub, you can enable branch restrictions allowing only certain users, teams, or apps to be able to push to a protected branch.
Git rebase flows result in clean history. Squashing code review fixups into the PR make it hard to see what changed. Rietta devs use --autosquash instead.
Grab a coffee and listen in while the Rietta team explores why using point estimation can help round out your team's planning process in development.
Learn how to prudently minimize the collection of passwords, authentication tokens, and customer private data in your debug logs to protect your company from legal liability.