tl;dr:The European software engineering market is split into three distinct groups that have little overlap: (1) Companies benchmarking against local competition, (2) those benchmarking against all local companies, (3) Big Tech: companies benchmarking against all regional.
tl;dr:"This post attempts to summarize the most common equity compensation setups you might come across, help you understand their value, and point to additional resources. This is the information I wish I knew earlier to understand how equity works at the high-level."
tl;dr:"The idea of setting up a mobile platform team will probably come around to you if your area has around 20 or more mobile engineers working on one or more apps." Gergely talks through how to approach this and challenges ahead.
tl;dr:Performance review feedback should be specific. If it's too generic e.g. "you're overly cautious" or speculative e.g. "you could have done this", you should ask for examples. Gergely outlines eight biases he's experienced, such as recency, strictness and leniency.
tl;dr:A healthy relationship between engineering and product lead has (1) two people, one voice inside and outside the team. (2) Frequent communication. (3) Empathy towards the other. (4) Clear understanding of where roles start and end. Gergely discusses how to forge such a relationship.
tl;dr:7 recommendations, including (1) read two books per year on software engineering thoroughly i.e. take notes, talk to others about it, etc... (2) Learn your language "in-depth, to the very bottom," so you understand its strengths and weaknesses.