At a senior role, what are things we can accomplish. I agree with the perspective and the work that is called out Link
Technical Work
- Review for technically design/architecture
- Analyze for with security/scalability of design
- Collaborate with other technical teams to agree on interfaces and common APIs
People Work
- 1-1s on a weekly basis
- Regular feedback
Plus my own additions
- Patenting / Knowledge Sharing
- Building your point of view
- Be on top of tech - Code as you need
Ongoing
- Teaching, mentoring and coaching
- Technical conversations and reviewing designs
Plus a perspective on mastering technology vs domain I like this article
Adding my top reasons to solve problems and not to master tech - Work On Interesting problems not Technologies
- Ideas take time and need refinement
- As you keep coding, you keep building perspectives
- Working prototype creates more interest/excitement and keep improving
- Your interest will not die down as you are solving newly known challenges
- Scope, features you will balanace when you spot the unknowns
- Its your idea you will not kill it :)
On WLB - Link
- We collectively create the culture we live in, changes comes from healthy WLB
- 20% of your work produces 80% of your value. Prioritize over priorities
Myth of super performers
I loved the below lines, I have seen this specific behavior. People who deliver but do not share, collaborate within the team. Adding my own perspectives
- X is the only developer who gets anything done
- Do not actively share knowledge with his peers
- Good at communication but bad at collaboration
- Explain simple things in a complicated way
- Good, connect at Leadership Level. Over-communication at the leadership level, limited collaboration at ground level
- Instead, make more people productive will reap the greatest benefits
- Turn our attention from individuals to groups of people
- Don’t mistake humility for ignorance - There are a lot of software engineers out there who won’t express opinions unless asked
Agile principles alternative definition
- Empathy for customer needs
- Actually getting stuff done
- A bird’s-eye view of the product vs market
- Able to balance birds-eye view to product view vs component view
More Reads
20 Things I’ve Learned in my 20 Years as a Software Engineer
Keep Thinking!!!
