To enumerate skills and consolidate resources associated with success in Software Engineering Leadership
Purpose: To enumerate skills and consolidate resources associated with success in Technology Leadership
None of these skills matter if you can’t articulate them. Always ask, did I explain this well enough for my audience to explain it to someone new?
There are a million books about this subject, here’s something that will hopefully persuade you to take persuation seriously.
Workplace politics might not be what you think. Savvy people use politics to get what they need for the success of their teams, organizations, and selves. We refer to workplace politics in this context.
Most people stumble here because they are either optimistic or averse to delivering ‘bad news.’ For me, I’d rather have the pilot tell me there’s a 10-minute delay coming than to sit on the tarmac for 9 minutes without knowing.
It’s worth noting that a nearly infinite amount has been written on this subject, but I think just 1 thing is important: Make your estimations with short-long ranges, if your stakeholder will not accept the range, use the longest duration. Include the rationale in your estimates too.
You don’t need to know everything about UML, but here are a couple key diagrams you should be using consistently. There is no need to make these documents formal.
Persistence is something you don’t pick up by reading some blogs. It is about who you are. You’ll need to develop this skill intentionally through becoming a better person.
My take: Perseverence is distinct from persistence. Persistence just means to keep trying, “perseverence” describes actually overcoming new challenges that you had previously been unable to.