- #LEAD VS PRINCIPAL SOFTWARE ENGINEER HOW TO#
- #LEAD VS PRINCIPAL SOFTWARE ENGINEER FULL#
- #LEAD VS PRINCIPAL SOFTWARE ENGINEER SOFTWARE#
Going a bit deeper-but still a high level-is the Designing Data-Intensive Applications. Sure, you will have to go elsewhere for more in-depth insights,īut the System Design Primer is an incredibly detailed map of the territory and the perfect place to start.
#LEAD VS PRINCIPAL SOFTWARE ENGINEER FULL#
It's full of resources on designing highly scalable systems and covers such topics as consistency and availability patterns, load balancers, proxies, caching, databases, protocols, etc. Regarding the basics of system design and architecture, I haven't found anything better than the System Design Primer on Github.
#LEAD VS PRINCIPAL SOFTWARE ENGINEER SOFTWARE#
You have to get yourself the Fundamentals of Software Architecture: An Engineering Approach and read it from cover to cover.
If you want to develop solid architectural thinking on par with Software Architects and learn various architecture styles, techniques and soft skills such as analysis and diagramming, It also goes into other important topics like Cohort and Root Cause analysis, short feedback loops, actionable metrics, and many more. Re-thinking various business processes from the first principles.įinally, although a little bit dry, The Lean Startup is a must-read for everyone who works in a, well, startup.Ĭontrary to the popular belief that a startup needs the "just-do-it" attitude, The Lean Startup teaches the importance of processes and disciplined work. Like the Phoenix project, it's also a "business fable" telling a story of a fictional character by the name Alex, who saves a failing business by It's a business classic, describing the theory of constraints, and is a very approachable read. The Goal: A Process of Ongoing Improvement. It has probably the highest value-to-effort, among other similar resources out there.Īnother book that will change the way you look at business processes in a company, including those in your team - is More importantly, you must stay up-to-date with the changing world of software development, all while keeping your basics stronger than ever.įor people without any business background, the Personal MBA is the most concise guide to general business education. It might not be full time anymore, or you might not get the most exciting features to work on, but you are responsible for keeping the quality high and technical debt low. It's also equally important to help the team evolve their products over time in a maintainable, scalable way. It's vitally important that you have a holistic knowledge of your products: their design and relationships with each other and the company's overall architecture.
Understanding business risks and requirements and accurately translating them into solutions and projects is something you have to do carefully and thoroughly. You've got to live both in the present and the future: anticipate dependencies, figure out unknowns, plan before, plan on the go, and revisit afterward. Tech Lead areas of responsibilities and skills AreaĪs a Tech Lead, you are responsible for leading the process to create and keep an environment where people become empowered.Įffective Tech Leads communicate a lot and clearly to help the team understand the context of their work. Then, pick the next weakest area, and so on. Pick the weakest area and commit to read and practice relevant skills until you feel you progressed by one point in your rate system. Think how confident you are in each of the areas presented below, and rate yourself from, say, 1 to 5. It's a collection of the most effective resources on the various aspects of tech leadership, which, combined with mindful practice, will help you to become a successful Tech Lead! TL DR What are the best resources for each skill?.
Which Tech Lead skills should I focus on?.The are only two questions you should ask yourself: Thankfully, you can learn most of the required Tech Lead responsibilities and skills from books, blogs, or talks and start practicing them right away. Being good at software development is an obvious basis, but it's not enough.
#LEAD VS PRINCIPAL SOFTWARE ENGINEER HOW TO#
If you are already a Technical Lead or want to know how to become a Technical Lead, it's your job to educate and improve yourself on all the aspects of this role. Tech Lead Compass | How to become a successful Tech Lead 🧭 Tech Lead Compass Learn what it takes to become a successful Technical Leader
0 kommentar(er)
