The Manager's Path
описание
Some notes of The Manager's Path book during reading. Main channel: @happydeveloper_tlg
149
подписчиков
Охват к подписчикам
257,0%
ERR
Реакции к просмотрам
0,21%
16 на 20 постов
Пересылки к просмотрам
0,24%
18
Постов в день
0,0
всего 20
Где отзываются чаще
доля реакций к просмотрам- 20 авг. 2024 г.Key takeaways for the mentor Be curious and open-minded: When we close our minds and stop learning, we start to lose the most valuable skill for maintaining and growing a successful technical career. Working with new people who are learning things for the first time can shed light on hidden patterns and help you make connections you may not otherwise have made. Listen and speak their language: Mentoring forces you to hone your communication skills. You must be able to listen and communicate in a way that the person can understand. Teams have to communicate effectively to get anything done. Make connections: Your career ultimately succeeds or fails on the strength of your network. Mentoring is a great way to build this network. Your career is long and the tech world can be very small, so treat the other person well.1,09%
- 20 авг. 2024 г.Being a mentor It is an opportunity in a safe way about the job of management, and the feeling of being responsible for another person. The mentee gets a supervisor that is solely focused on him.1,05%
- 18 нояб. 2024 г.The tech lead role is not a point in the ladder, but a set of responsibilities that any engineer may take once they reach the senior level. - Regular (weekly) 1-1 touchbases - Regular feedback on career growth, progression towards goals, areas for improvement, and praise as warranted. - Working with reports to identify areas for learning and helping them grow in these areas via project work, external learning, or additional mentoring.0,66%
- 18 нояб. 2024 г.Good manager, bad manager: the process czar The process czar believes that there is one true process that will solve all the team's biggest problems. Agile, Kanban, scrum, Lean, or even waterfall. Engineers sometimes turn into process czars when they become tech leads, seeking out the right tool to solve all issues with planning, focus, time management, and prioritisation. Processes must meet the needs of the team and the work. Be careful on relying on processes to solve problems that are a result of communication or leadership gaps on your team. It's a waste of your time to play rule cops, and automation can often make the rules more obvious.0,48%
- 18 нояб. 2024 г.How to be a great tech lead Understand architecture: Take time to understand it. It's almost impossible to lead projects well when you don't understand the architecture you're changing. Be a team player: If you're doing all the interesting work yourself, stop. Working on the less exciting, boring or frustrating parts of the code base can teach you a lot about where the process is broken and how to fix it. Also, if you are doing the most boring work, stop that too. You want to encourage others on your team to learn the entire system. Lead technical decisions: Determine which decisions must be made by you, which decisions should be delegated to others with more expertise, and which decisions require the whole team to resolve. Make it clear what the matter under discussion is, and communicate the outcome. Communicate: Your productivity is now less important than the productivity of the team. You will pay the price of communication overhead, you represent the team. If one universal talent separates successful leaders it's communication skills. Successful leaders write well, they read carefully, and the get up in front of a group and speak. Don't forget to listen and give others a chance to speak. If you aren't a good note taker, you may need to become one.0,41%
- 18 нояб. 2024 г.#Managing_people0,00%
- 18 нояб. 2024 г.Managing a project 1- Break down the work: Start breaking down your big deliverables into tasks. 2- Push through the details and the unknowns: Work through the unknowns until you really feel that there is no more value to be gained in spending time on them. 3- Run the project and adjust the plan as you go: The value of planning is that it helps you know how far the project has come, and how far it is from completion. 4- Use the insights gained in the planning process to manage requirement changes. 5- Revisit the details as you get close to completion: Run a premortem, an exercise where you run through all the things that could fail on the launch of the projects. Make a launch plan; make a rollback plan. Celebrate.0,00%
- 18 нояб. 2024 г.Managing projects When faced with a project with many unknowns and relatively hard deadlines, you'll find agile processes tricky. You need to understand how to break down work that has complexity beyond the scope of what you can do as an individual. Hiring for project management is bad, but still project management has to happen. As a tech lead, you should be doing it when needed, especially for deeply technical projects. The value of planning isn't that you execute the plan perfectly, that you catch every detail beforehand, or that you predict the future; it's that you enforce self-discipline to think about the project in some depths before diving in and seeing what happens. Take time to explain. Never hesitate to take the opportunity to explain basics and motivations to senior or junior members. It educates them without making them feel small.0,00%
- 18 нояб. 2024 г.Being a lead 101 The main roles of a tech lead: - System architect and business analyst; Have a good sense of the overall architecture of your systems and a solid understanding of how to design complex software. Understand business requirements and translate them into software. - Project planner: Breaking down work into rough deliverables. Part of the challenge here is getting as much productive work done in parallel as possible. - Software developer and team leader: Software developers and leaders write code, communicate challenges and delegate. In your position as a tech lead, you should continue writing code, but not too much. Start looking for opportunities to delegate work. You have to act as a software developer, a system architect, a business analyst, and a team leaders who knows when to do something single-handedly, and when to delegate work to others.0,00%
- 18 нояб. 2024 г.All great tech leads know this one weird trick The willingness to step away from the code and figure out how to balance your technical commitments with the work the whole team needs. You'll often need to balance doing things you know how to do and enjoy doing, such as writing code, with things you don't know how to do. You'll feel uncomfortable about it. The worst scheduling mistake is allowing yourself to get pulled randomly into meetings. It's important to get your team into a schedule that allows them to be focused on development for long stretches of time. Part of your leadership is helping the other stakeholders, such as your boss and the product manager, respect the team's focus.0,00%
- 18 нояб. 2024 г.You can't lead without engaging with other people, and people skills should be important, much more than technical expertise. Tech leads will work on one major new technical skill: project management, or the work of breaking down a project. Being a tech lead is an exercise in influencing without authority. How do I empower my team? How do I remove the obstacles slowing them down?0,00%
- 18 нояб. 2024 г.It is very hard to grow past senior engineer 2 without ever having acted as a tech lead._0,00%