3 posts tagged with "Job Interview"

This post is about the git skill level I expect when someone puts “Git” on their CV – practical, professional usage rather than just knowing git commit.

• Know this before you write Git on your CV
• Git basics if you are getting paid
• Git Warrior
• Git Guru & beyond

Before you write GIT on your CV for your next job interview, make sure you know how to use GIT professionally; read on.

If you are here you know that GIT is likely the most popular version control system used in the known universe. If you are a developer looking to get paid GIT is one of your most important tools for doing a professional job.

Any developer can write code. Professional developers know how to organise code changes so that they can be easily reviewed, patched and reasoned about. GIT like other version control systems is the tool that helps us to work professionally.

Unfortunately, there is a disconnect between using GIT and using GIT Professionally.

Working with MFA‑enabled AWS accounts from the CLI can be painful; this post walks through the small tool I built to make that workflow bearable.

• TL;DR
• Managing MFA credentials
• Why build another tool?
• What problem it solves
• One more thing

Using MFA enabled AWS accounts & CLI​

TD;LR​

Simplify your life when using MFA-enabled accounts with AWS profiles by installing this command-line tool.

Install awsmfa from npm or fork the project on GitHub.

Managing MFA credentials​

Enforcing multi-factor authentication (MFA) on AWS accounts is a security best practice that can provide some usability hurdles for engineers that rely on the SDK and AWS command line tools to get work done.

The typical workflow for working with MFA-enabled accounts is to request a temporary session using the AWS STS service. The STS service will then return a session token which includes temporary credentials as well as a session token. Depending on the use case these data can then be used either in a profile definition, environment variables or as arguments to call AWS Apis that require MFA.

Here I’m less interested in tooling and more in how to think about pull requests as a learning tool and a way to be a better teammate.

• Why we have pull requests
• What is a pull request?
• Things to consider
• Pull request checklist

Why do we have pull requests?​

As software developers, we enjoy that feeling of being immersed in the flow, that wonderful state of being where hours whizz by in an instant, and our mental model stands clear; where we can be hyper-productive as long as we can keep the outside world at bay and remain in blissful uninterrupted solitude.

However, building modern software is also a complex team sport where collaboration and continuous feedback loops with fellow developers are key to personal development and high-quality code.

Code reviews are the most obvious contact point with other developers and a foundational process in working towards becoming a part of, remaining in or working towards building a high-performing team that creates code that is stable and fun to work with.