View profile

Level Up - Issue #16

This week I had a number of conversations with people, reflecting on progress, dealing with change an

Level Up

December 1 · Issue #16 · View online
Level Up delivers a curated newsletter for leaders in tech. A project by Ideal for busy people such as Tech Leads, Engineering Managers, VPs of Engineering, CTOs and more.

This week I had a number of conversations with people, reflecting on progress, dealing with change and uncertainty. In a rapidly changing environment, I emphasised how important it is to recognise improvements. As a leader it’s important to celebrate and encourage others to celebrate success. I find it is much easier to continue multiplying this energy than always focusing on what’s wrong.
I hope you enjoy this week’s content. If you find it useful, please forward to someone else and send me feedback.

2019 State of 1-1s Report
Visibility in a blameless culture leads to process improvement
In praise of blame
Do engineering managers need to be technical?
On Being a Manager
A Probe by Any Other Name
5 Things I've Learned in 20 Years of Programming
Bits On the Wire
A domain-driven Vue.js Architecture
Egnyte Architecture: Lessons learned in building and scaling a multi petabyte content platform
Organisation & Processes
Successfully Merging the Work of 1000+ Developers
Hiring Engineering Leaders
The Requirements For Aftermath Projects
The epistemology of software quality
Diversity, inclusion, and belonging at GitHub in 2019
Interesting tweets
These sort of tweets are always fun! Share those tools with each other.
John Papa
First things I installed on my new MacBook Pro 16"

0. VS @code
1. @alfredapp (better spotlight)
2. bartender (organize)
3. divvy (window mgt with keyboard)
4. wifi signal (detailed)
5. @snagit (screen caps & animated gifs)
6. insomnia (http)
7. Amphetamine
8. Dropbox
9. Chrome
Some very good advice when you’re working with distributed systems. Click through to see the follow on tweets
Savvas Kλeanthous 🇬🇧🇪🇺🇨🇾
When messages are transmitted they should include at minimum:
1. Message name
2. Name of service which owns the contract of the message
3. Message version
4. Message unique id
5. Correlation id
6. Causation id
7. UTC Timestamp

[1 of 5
Thanks for making it this far! 🤗
If you enjoyed this newsletter, please send me feedback and share with others!
Did you enjoy this issue?
If you don't want these updates anymore, please unsubscribe here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue
Patrick Kua, Postfach 58 04 40, 10314, Berlin, Germany