Addy Osmani·3ySoft skill books that will make you a better developer
This article provides a list of soft skill books that can help developers improve their programming and managerial abilities. It covers various topics such as deep focus, high-leverage activities, growth mindset, leadership skills, and more. The article highlights the importance of developing soft skills alongside technical skills for developers.
Stay SaaSy·3yThe Future of Remote Work
Some companies are reversing prior decisions to go remote, while others cancel the last of their office space. Debates around the value of remote work have continued feverishly, especially since both sides are incentivized to normalize their own point-of-view. In-person businesses operate with more intensity than remote businesses, on average.
Community Picks·3yScrum sucks.
Scrum is an Agile project management system that helps teams deliver value incrementally in a collaborative way. However, the implementation of Scrum in real-world scenarios often leads to complex ceremonies, poor planning, and a lack of true collaboration. Making Scrum work requires teams to take a team-level approach, focusing on flexibility, adaptability, collaboration, and results rather than rigid processes and metrics.
swizec.com·3yLet juniors speak first
Engaged engineering teams prioritize the input of their least experienced members, fostering collaboration and valuing diverse perspectives. Seniors encourage juniors to speak up, ask questions, think critically, and contribute early in discussions. The fluidity of roles allows for the empowerment of team members and the sharing of relevant expertise.
Community Picks·3yBeing a good mentor – a developers guide
Mentoring is an integral part of personal and professional growth, both for the mentor and the mentee. The power of mentorship can shape careers, change mindsets and adapt life trajectories overall. A mentor-mentee relationship, just like any good relationship, needs a sturdy foundation.
Community Picks·2yjordan-cutler/path-to-senior-engineer-handbook: All the resources you need to get to Senior Engineer and beyond
A repository containing a curated list of resources to help software engineers reach senior engineer positions and beyond, including newsletters, books, courses, and more.
Ido Shamun·2yEngineering Handbook
Daily.dev is creating an engineering handbook to streamline processes, normalize culture, and improve collaboration among engineers. The handbook includes sections on expectations, decision records, epic owner and individual contributor roles, communication preferences, and project management.
Substack·2yA good engineer thinks like a product manager
Engineers need to think like product managers to create solutions that customers love. They should focus on solving customer's problems rather than the technical aspects. To improve product-mindedness, engineers can pair with non-tech people, explain technical solutions to non-tech people, ask business and customer-related questions, talk directly with customers, do freelance work, and take on different roles. Simplifying solutions before implementation is also crucial for better results.
Substack·3yWhat is a Staff Engineer?
The article discusses the role of a Staff Engineer, including its definition, career progression, and responsibilities. It explores how roles work in big tech firms like FAANG, the different archetypes of Staff Engineers, and the differences between Senior Engineers and Staff Engineers. It also delves into the duties and challenges faced by Staff Engineers, as well as their typical day. The article concludes with insights into the Staff Engineer career path and tips for aspiring Staff Engineers.
Ido Shamun·3yThe Journey of Becoming a CTO
The path to becoming a CTO is a journey that evolves along with the company's growth. It starts with coding and product work, then progresses to managing teams and bridging the gap between business and engineering. Lessons include focusing on exponential impact, setting aside time for coding, using prototypes for alignment, and hiring and documenting wisely. The role requires adaptability, flexibility, and continuous learning.
Community Picks·3yBreaking down a design
Breaking down a design involves being clear on the outcome and opportunity, doing it at the right moment, presenting the designs in a walkthrough, working at the right fidelity, accepting the CoWs (chunks of work), slicing thinly, identifying releases with outcomes, designing for interim releases, being prepared to trim the tail, checking in against your appetite, and allowing enough time.
Hacker Noon·3yMaking a Good Engineer a Great One: Training Your Skills and Training Your Mindset
Learn how to navigate the three phases of learning new skills, from the adjustment phase to the intuition-building phase and the stagnation phase. Adopting a growth mindset can help with the learning process. Remember to seek feedback and avoid overconfidence. Consider your professional goals when faced with the decision to take on new responsibilities. The Dreyfus model is a helpful framework for understanding skill acquisition.
Stay SaaSy·3yHow To Be An Engineer That PMs Don't Hate
To be an engineer that PMs don't hate: Be responsible with the power of shipping code. Don’t make Product Management your QA team or your project manager. Don't mistake technical knowledge for intelligence. Explain the value of tech debt in a way that is easy to understand.
Charity·2yWhy Should You (Or Anyone) Become An Engineering Manager?
The article discusses the reasons why someone should consider becoming an engineering manager. It highlights the changing perception of management and the importance of good engineering managers in driving productivity and quality. The article also mentions the skills that can be developed through management, and how it can benefit personal growth and relationships.
Substack·2yFrom Senior to Staff Software Engineer... A managers perspective
To get promoted to Staff Software Engineer and beyond, you need to focus on impact and visibility. Impact involves being able to lead a wide array of projects and foresee roadblocks. Visibility includes regularly engaging with various stakeholders and measuring the success of initiatives.
freeCodeCamp·3yTransform Your Engineering Management Career Path
Learn how to be an exceptional engineering manager with a course that focuses on leadership, skill development, communication, and personal growth. Discover the fundamental differences between being a software engineering manager and a technical lead, uncover pivotal skills for career advancement, and learn about effective communication and feedback within a team setting. The course emphasizes the importance of empathy, communication, and team dynamics in a successful leadership role.
Pointer·3yTime Management
We never have enough time, so we need to make the most of what we have. By prioritizing tasks that give us energy and focusing on our personal strengths, we can create a schedule that aligns with our goals and values. Auditing our time allocation periodically allows us to make corrections and ensure we are investing our time judiciously. This same technique can be applied to managing any portfolio of scarce resources.
Better Programming·3yWhy an Engineering Manager Should Not Review Code
Emily Dresner: Why should the TL not lead the team and why should an EM with a team of sufficient size not review code? We consider three aspects when answering this question: role definition, team communication complexity, and team size. A manager builds a well-working team on solid communication fundamentals, she says.
Community Picks·3y🤠 "Where have all the hackers gone?" + a way to discuss programming languages 👨🎤
The post discusses the different aspects to consider when comparing programming languages, including soil (properties of running code), surface (features and syntax), and atmosphere (community and ecosystem). It also explores why discussions about programming languages often focus on atmosphere and the challenges of quantifying its impact. The author argues for a more open-minded approach to tech choices and suggests that training and mentorship can help developers quickly become proficient in new languages.
