↓ Skip to main content
alper.nl

·57 words
English Leadership Software Engineering

Ilya Grigorik notes down a perspective on what people at the higher senior+ levels should be doing. At that level things can get fuzzy and people tend to struggle.

  • It’s not your job to solve the problem
  • Focus on perspectives
  • Build technical leaders

Scroll down especially to read the excellent list of tactical everyday best tips.

https://ilya.grigorik.com/the-principal-engineers-handbook/

Alper Cugun
Author
Alper Cugun

Related

·70 words
English Leadership Software Engineering
“This may surprise you, but continuous deployment is far and away the easiest way to write, ship, and run code in production. This is the counterintuitive truth about software: making lots of little changes swiftly is infinitely easier than making a few bulky changes slowly.”

·45 words
English Leadership Product/Design Software Engineering
Running multiple strategic tracks will set you up to dominate at a large scale, but many organizations can’t run one let alone run multiple at the same time. The visualization and plays as described here by Itamar Gilad look a lot like Wardley mapping.

·57 words
English Leadership Software Engineering
A short guide of how a team can turn around the work they need to do on a legacy system and come out the better for it. I’ve seen lots of teams struggle with this but as described here a lot of it is in the approach and the praxis of doing it and working together.