Friday, February 28, 2020

Friday Links

Cloud Computing Is Not the Energy Hog That Had Been Feared

Preparing for Coronavirus to Strike the U.S.

Google programming language scorecard: How C, C++, Dart, Rust, Go rate for Fuchsia

Introducing Hanami::API

Love it or hate it, Marmite is having a massive foodie moment

What is a Tech Lead? The 4 worst things about this promotion

Some MVP and Experiment Tips

Second Sock Syndrome – What It Is and How to Fight It

Slack etiquette at Zapier

Google releases Lighthouse web dev extension for Firefox

Who cares about Emacs?

The Causal Analysis of Cannibalization in Online Products

Coronavirus COVID-19 Global Cases by Johns Hopkins CSSE


A Mathematician's Guide to Beauty

The One About Time Management

Friday, February 21, 2020

Friday Links

Debian discusses how to handle 2038

The Pyramid of Unit Testing Benefits

Internet of Things Candle

A Blueprint for Internal Open Source

Open sourcing DataHub: LinkedIn’s metadata search and discovery platform

Titan Security Keys - now available in Austria, Canada, France, Germany, Italy, Japan, Spain, Switzerland, and the UK

When To Be Concerned About Concerns

About Rails concerns

Tech Debt Developer Survey Results 2020 - Impact on Retention

Survey results: What makes a company People-first?

8 Best Professional Development Goals for Managers


The One About Meetings (Pt. 1)

The One About 1:1s

The Pragmatic Programmers

Back to Agile's basics (Uncle Bob)

Intro to Rust programming

Good tech debt

The Data Exchange with Ben Lorica

Productionising real-world ML data pipelines

Monday, February 17, 2020

Using multiple git configurations

It is fairly common that you might be contributing to multiple git repositories which make different git configuration necessary.

Mine and probably the most common case is that I am using different contributor email addresses for my private and work git repositories. You might also want want to have separate global git ignores or other options that differ in multiple repositories.

The way I do it is having one ~/.gitconfig which looks like this:

  name = Christof Damian 
  email = 

  excludesfile = ~/.gitignore_global 

[includeIf "gitdir:~/devex/"] 
  path = ~/.gitconfig_devex 

This defines the defaults for my name, email and a global gitignore. It also tell git to look at another git config for all repositories that are below the ~/devex/ folder. This file is very short for me, as it just changes the email address (~/.gitconfig_devex):

  email = 

The ~/.gitignore_global is just a normal gitignore file, which excludes all the files the editors or tools I use create. It could for example look like this:

# whatever files your local editor/tools config generates

You could use for example to generate this

Friday, February 14, 2020

Friday Links

Supercharge your command line experience: GitHub CLI is now in beta
3 (+1) Questions for impactful Sprint Goals!
Getting Started With System Tests in Rails With Minitest
I love Free Software Day 2020
Unlearning toxic behaviors in a code review culture
Agile as Trauma
Rotary Cellphone
Interview with Yukihiro Matsumoto: Ruby is Designed for Humans, not Machines
How to Use the Distance Matrix API
Mythical man month : 10 lines per developer day
How Big Technical Changes Happen at Slack

Podcasts / Videos

Getting Real about Managing up
Presto with Justin Borgman

Friday, February 07, 2020

Friday Links

3 research-backed principles that help you scale your engineering org

Paris mayor unveils '15-minute city' plan in re-election campaign

UN poverty expert's visit shines light on struggles of Spain’s poor

Street View’s 15 favorite Street Views

A new hash algorithm for Git

Istio as an Example of When Not to Do Microservices

Monoliths are the future

Browsers, web sites, and user tracking

Austerity, gentrification and big tunes: why illegal raves are flourishing

What we do and don’t know about the 2019-nCoV coronavirus

NYC Parks Are Using a Designer’s ‘Tree Font’ to Plant Secret Messages with Real Trees

AppSignal Ruby Gem 2.10: Better Diagnose (And More)

This Week in Programming: Forget Microservices, Monoliths Are the Way Forward

Retrium: Public Team Rooms


The journey to fast production asset builds with Webpack

Facebook’s Platform Opportunity

Letters To A New Developer: Develop empathy

Things I Believe About Software Engineering

Google Maps Hacks

NSA Security Awareness Posters

Integrated systems for integrated programmers

The dark side of expertise

Podcasts / YouTube

Leadership is Language

John Deere: Farm Software with Ryan Bergman

Ryan Bergman - Walking Into Mordor: The History and Future of DevOps