Discover and read the best of Twitter Threads about #LeadDevBerlin
Most recents (7)
“If you’re hiring someone from an underrepresented group who has been underpaid, folks in those groups face a lot of bias.
So you have the opportunity - and I think the duty - to try to fix that” [rather than propagating it or taking advantage] @KevinGoldsmith #LeadDevBerlin
So you have the opportunity - and I think the duty - to try to fix that” [rather than propagating it or taking advantage] @KevinGoldsmith #LeadDevBerlin
“Things to consider:
- current salary
- previous salary (might have taken a cut)
- experience
- company’s stage of growth
- company’s salary bands for the role
- skill scarcity
- budget for role
- underrepresented group membership
- next pay review” @KevinGoldsmith #LeadDevBerlin
- current salary
- previous salary (might have taken a cut)
- experience
- company’s stage of growth
- company’s salary bands for the role
- skill scarcity
- budget for role
- underrepresented group membership
- next pay review” @KevinGoldsmith #LeadDevBerlin
“Things NOT to consider:
- what others on the team make
- how long it’s taken to fill the role
- how much YOU make
The best way for you to improve your salary is to hire the most talented people you can” @KevinGoldsmith #LeadDevBerlin
- what others on the team make
- how long it’s taken to fill the role
- how much YOU make
The best way for you to improve your salary is to hire the most talented people you can” @KevinGoldsmith #LeadDevBerlin
Great talk title from @scott_triglia: Making impossible decisions, one step at a time. Essentially reapplying concepts from Lean Startup to planning for complex uncertain undertakings.
Key principles:
- assume our plan will change
- prioritise getting to market
#LeadDevBerlin
Key principles:
- assume our plan will change
- prioritise getting to market
#LeadDevBerlin
https://t.co/Uk73CuQTCV
“Outcome of planning meeting:
1) Document problem space and any constraints
2) Name and empower a DRI (Directly Responsible Individual)
3) Select directional approach”
@scott_triglia #LeadDevBerlin
1) Document problem space and any constraints
2) Name and empower a DRI (Directly Responsible Individual)
3) Select directional approach”
@scott_triglia #LeadDevBerlin
I was SO delighted when @birgitta410 proposed this Cultivating Architecture talk, as retaining autonomy for teams AND having a reasonable & useful evolving architecture is so important as one scales an organisation. Excited for this #LeadDevBerlin
Great articulation of how things fit together in organisations:
Organisation’s goals + Principles + Practices + Architecture Requirements
@birgitta410 #LeadDevBerlin
Organisation’s goals + Principles + Practices + Architecture Requirements
@birgitta410 #LeadDevBerlin
“An architectural principle is useful when it’s declarative (gives direction), guides architectural decisions (helps with decision making) and helps to achieve specific qualities that you want” @birgitta410 #LeadDevBerlin
SO excited for @lrnrd’s talk on inclusive high performing distributed teams.
First up she reminds us of what high performing teams need:
- Psychological safety
- Dependability
- Structure & clarity
- Meaning & impact
#LeadDevBerlin
First up she reminds us of what high performing teams need:
- Psychological safety
- Dependability
- Structure & clarity
- Meaning & impact
#LeadDevBerlin
“Don’t underestimate the power of the #random channel. It’s cool to know a colleague made a great sourdough loaf this weekend, and another built some amazing Lego w their kids. We need to hone connection on a day to day basis, and acknowledge our humanness” @lrnrd #LeadDevBerlin
“Connection:
- Build trust
- Make space for humanness
- Define expectations
- Grow together #gratitude channel & feedback
- Stay aligned: connect to the bigger picture
- Address remote loneliness
- Share context: deliberately add nuance & perspective“ @lrnrd #LeadDevBerlin
- Build trust
- Make space for humanness
- Define expectations
- Grow together #gratitude channel & feedback
- Stay aligned: connect to the bigger picture
- Address remote loneliness
- Share context: deliberately add nuance & perspective“ @lrnrd #LeadDevBerlin
Really excited for @nickstenning’s talk on what we can learn about what went RIGHT in incidents.
Also ADORE him emphatically highlighting that @UberGeekGirl co-wrote the talk & deserves credit even tho not co-presenting today 💖
#LeadDevBerlin
Also ADORE him emphatically highlighting that @UberGeekGirl co-wrote the talk & deserves credit even tho not co-presenting today 💖
#LeadDevBerlin
Agenda for Learning from Incidents: Understanding How Things Went Right
1) Why do we even try to learn from incidents?
2) Four common traps
3) Four helpful practices
@nickstenning #LeadDevBerlin
1) Why do we even try to learn from incidents?
2) Four common traps
3) Four helpful practices
@nickstenning #LeadDevBerlin
“Your complex system runs in degraded mode. A lot.
We partly learn from incidents to learn how to better prevent them. But also to learn how to better respond to inevitable reality that incidents cannot be completely eradicated in complex systems” @nickstenning #LeadDevBerlin
We partly learn from incidents to learn how to better prevent them. But also to learn how to better respond to inevitable reality that incidents cannot be completely eradicated in complex systems” @nickstenning #LeadDevBerlin
“This is why moving into management is so scary. Gallup found in their research that managers don’t just influence the results their teams achieve, they explain a full 70% of the difference” (!!!) @knotnicky #LeadDevBerlin
Brilliant 10 mins from @knotnicky on what we can reapply from software engineering practices to engineering management:
1) Don't repeat ~yourself~ decisions
2) Don't reinvent the wheel
3) Keep it simple
4) Apply product thinking
#LeadDevBerlin
1) Don't repeat ~yourself~ decisions
2) Don't reinvent the wheel
3) Keep it simple
4) Apply product thinking
#LeadDevBerlin
Especially loved @knotnicky’s point that in engineering management, the unit of reuse is the decision. And people want to know the why behind a decision, but also sometimes they want to know decisions will be fair and consistent. This is what process is useful for! #LeadDevBerlin
“Remember “What got you here won’t get you there”. When you move to a lead developer role you need to develop from “maker” mode into “multiplier” mode. Become more of a gardener” @patkua #LeadDevBerlin
“People are not computers. People cannot be programmed. Blurry is the new binary in your new role as a lead developer. There is no single right answer. You’ll never know what all people want, but you can be certain it’ll be different” @patkua #LeadDevBerlin
“Different models of decisions making:
- autocratic
- consultative (consult but reserve right to decide)
- democratic or consensus-driven.
Even democratic isn’t binary - eg Roman Voting people vote either in favour, opposed, or happy to go w majority” @patkua #LeadDevBerlin
- autocratic
- consultative (consult but reserve right to decide)
- democratic or consensus-driven.
Even democratic isn’t binary - eg Roman Voting people vote either in favour, opposed, or happy to go w majority” @patkua #LeadDevBerlin
