DEV·2yMy first experience as a Tech Lead
The author shares their experiences and insights from their journey of becoming a tech lead. Emphasizing the importance of soft skills, they discuss the nuances involved in evaluating candidates, the distinction between junior and senior developers, and their personal anecdote of leading a project for the first time. Valuable lessons from various types of senior developers are also recounted.
Community Picks·2yCode Refactoring: 10 Lessons I Learned on Improving Code
Refactoring involves modifying the structure of code without changing its behavior to improve readability and maintainability. Key lessons include analyzing the code beforehand, refactoring as a team, composing smaller methods, simplifying conditional expressions, ensuring code understanding, setting clear objectives, making incremental changes, and considering performance. The goal is to maintain an efficient and manageable codebase.
groCTO·2y6 atomic habits of highly efficient CTOs
Kovid Batra, founder of groCTO, shares six crucial habits that distinguish highly effective CTOs: holding daily stand-ups, scheduling deep work sessions, conducting regular one-on-ones, continually updating one's knowledge, and moving quickly with immediate feedback loops. These habits foster alignment, productivity, strong team relationships, and continuous improvement.
Community Picks·2yHow To Be Productive
No matter where you are in your journey, inaction is inevitable at some point. To overcome it, consider four approaches: start with any small action and keep moving, connect your actions to your core values, find opportunities in crisis to drive purposeful change, and reward yourself for taking steps, no matter how small, to build motivation and momentum.
Substack·2y5 reasons why your best developers will quit - and how can you postpone it
Many software developers quit due to feeling unappreciated, lonely, bored, stuck, or apathetic. To retain them, it's crucial to make them feel valued, connected, challenged, and passionate about their work. Managers should actively provide salary increases, recognize achievements, encourage team bonding, delegate interesting tasks, and support career growth. Ultimately, some factors are beyond control, and employees will still leave for various reasons, but these tips can help postpone their departure.
Saiyan Growth Letter·2yHow to join a new company effectively
To quickly contribute at a new company, use the product to understand its problems and suggest improvements, learn the company's origin and user behaviors, review past issues to avoid repeating mistakes, and set up 1:1 meetings with teammates to build relationships and gather vital information. Note-taking is crucial to retain and understand important details.
Community Picks·2yThe Dual Nature of Seniority in Software Development
The expectations and roles of senior developers vary widely across companies, often evolving due to title inflation and the need for specific skill sets. The current industry trend prioritizes reliable delivery over innovation. To succeed, developers must adapt to the unspoken needs and strategies of their bosses and teams, often requiring professional mindreading and subtle influencing without overstepping. Senior roles demand balancing technical skills with interpersonal dynamics and understanding when to take the lead or step back to align with business goals.
Medium·2yThe 5 Deadly Sins of Text Communication for Software Developers
Developers often face communication challenges that hinder productivity, such as not providing enough context, writing multiple short messages, and not trying hard before asking for help. Effective communication includes asking direct questions, providing sufficient context, and composing clear messages. Tips also include pre-explaining problems and investing in communication practices to build better relationships and get faster help.
Code Like A Girl·2yCode Review Best Practices: Enhancing Development Efficiency and Quality
Effective code reviews are crucial for maintaining high-quality software and reducing development costs. Key practices include setting clear objectives, maintaining coding standards, crafting efficient review processes, and fostering team collaboration. These strategies help in catching bugs early, ensuring maintainability, performance, and security, and promoting continuous improvement. Code reviews should focus on providing actionable feedback and creating a positive, constructive environment for better teamwork and software quality.
Substack·2y15 Life and Work Principles from Jensen Huang (NVIDIA CEO)
Jensen Huang, CEO of NVIDIA, shares 15 principles on leadership, strategy, and personal growth. His insights include empowering employees with information, encouraging public reasoning, and maintaining transparency. Huang prefers feedback in public settings for shared learning opportunities and emphasizes strategic decisions over market share. He values resilience, humility in failure, and dedicating oneself to lifelong crafts.
Game Developers·2yHow many of you were, or still are, Software Developers?
The post explores whether game developers can be considered software developers, given that game development is a specialized branch of software development. The author shares their journey from a background in cyber-security, commerce, and mobile app development, to game development. They emphasize the importance of a solid software engineering background for effective collaboration in large teams, noting skills like CI/CD, Source Control, and design patterns as essential. The post raises the question of how many developers transitioned from software development to game development and shares experiences with this pathway.
InfoQ·2yThinking Like an Architect
Key insights into the role of architects include their function as IQ amplifiers, enhancing team intelligence by simplifying complex concepts and fostering better decision-making. They bridge organizational levels, use metaphors to make technical ideas relatable, and leverage simplified models for effective problem-solving. The ability to see multiple dimensions enables architects to introduce innovative solutions, tackle constraints, and balance standardization with innovation.
LogRocket·2y10 tips for a great project kickoff
Project kickoffs are crucial for setting the initiative's course. Effective preparation, such as sharing relevant information in advance and defining a core team, is key. Strong facilitation, starting with icebreakers and focusing on discussions rather than presentations, enhances engagement. Post-meeting activities like detailed summaries and follow-up meetings ensure accountability and sustained momentum. Continual improvement through feedback will elevate future kickoffs, leading to a smoother project trajectory.
Tech World With Milan·2yHow to coach people through the Change Curve
Leaders need to understand and listen to their team members to effectively manage change. The Change Curve, developed by Elisabeth Kübler-Ross, outlines the emotional journey people experience during transitions: denial, self-criticism, confusion, acceptance, solutions, and commitment. Effective communication, especially during the early stages of denial and anger, is crucial. Active listening, which involves listening for content, structure, and deeply, helps leaders connect better with their teams. Open-ended questions and allowing silence in conversations are key techniques to improve understanding and support during changes.
Engineering Enablement·2yHow Spotify maintains autonomy at scale
Spotify maintains team autonomy at scale through a structured balance between leadership control and squad-level decision making. While leadership oversees organizational structure, strategic priorities, and long-term vision, squads independently manage work execution and contribute within their domains. Challenges such as technical dependencies and immature squads exist, but strategies like formalized code ownership, creating alignment practices, and encouraging knowledge sharing help mitigate these issues. Effective use of RFCs, technology constraints, and social interaction initiatives reinforce these practices.
Substack·2yHow to get promoted: Lessons from an ex-Amazon VP
Ethan Evans, an ex-Amazon VP, shares career lessons on how to get promoted. Key strategies include understanding the gap between your current and desired role, asking for feedback, understanding the promotion process, building trust, and expanding your work scope. Additional tips include adapting to your manager's style, building relationships with mentors and higher-ups, and increasing visibility within the organization.
Community Picks·2y15 principles for managing up
Managing up is an essential skill that helps elevate your career by making you a competent operator who communicates effectively and drives towards business goals. Key principles include focusing on getting to the point, showing your thought process, flagging potential issues, bringing solutions rather than complaints, using information hierarchy, over-communicating if necessary, and being explicit about what you need. Recognize if you're being genuinely micromanaged or if you need to improve your communication. Manage up throughout your career, regardless of your seniority level, to build strong relationships and advance within your organization.
Hacker News·2yHow and why we built our startup around small teams
Small teams at PostHog, typically composed of 2-6 people, allow the company to scale while retaining the speed and culture of an early-stage startup. These teams are autonomous and responsible for their own missions, projects, and performance. Each team runs retrospectives and sprints independently, and team leads, who focus on product rather than management, drive their operations. The structure emphasizes minimal management layers, strong ownership, and flexibility, although it requires careful hiring to maintain effectiveness.
Substack·2y10 common ways engineering managers get stuck
Engineering managers often get stuck in common pitfalls such as ignoring destructive behaviors, trying to please everyone, and neglecting personal development. To avoid these traps, they need to address issues promptly, build strong relationships inside and outside their teams, balance their roles effectively, and maintain their own growth. Recognizing and adapting to these challenges can significantly improve management effectiveness and team success.
Community Picks·2yYour Company's Problem is Hiding in Plain Sight - High Work-In-Progress (WIP)
High Work-In-Progress (WIP) is a major culprit behind slow delivery and productivity issues in software development. It creates stress, delays, and a bottleneck in task completion. The remedy is counterintuitive: work on fewer tasks simultaneously and allow for more idle time. This approach prevents the traffic jam of tasks, leading to faster feature delivery and improved morale.
GamesIndustry.biz·2yHow to survive until 2025 in the games industry
Developers and business leaders offer strategies for surviving in the games industry until 2025, including seeking non-traditional funding, listening to advisors, pivoting business strategies, raising funds proactively, planning for failures, and forming external partnerships. Emphasis is also placed on leadership, maintaining team morale, focusing on existing games, and cautiously navigating new industry norms.
Community Picks·2yYou Might Be Better Off Without Pull Requests
Pull requests and mandatory code reviews are popular practices in modern software development, especially in open-source projects. However, some argue that Continuous Integration (CI) and direct merging to the main branch may be more beneficial, particularly for teams that trust each other. The post explores the history of version control, the rise of pull requests, and the benefits and challenges of CI. It advocates for small, frequent merges to the main branch to improve team flow and code quality, suggesting that developers reconsider older practices to enhance productivity.
Jacob Kaplan-Moss·2yAll I Need to Know About Engineering Leadership I Learned From Leave No Trace
Principles from the outdoor ethic 'Leave No Trace' can provide valuable insights for engineering leadership. Key takeaways include the importance of planning and preparation, using sustainable and proven technology, managing technical debt, contributing to open source projects, mitigating security risks, understanding existing systems before making changes, and being considerate of others in both the engineering and natural environments.
gitconnected·2ySuccess as an Engineering Manager
The main goal of an Engineering Manager (EM) is to ensure their team is successful, rather than focusing solely on individual management. A team-oriented approach leads to effectively achieving objectives and long-term engagement among team members. Successful team outcomes also simplify people management by minimizing common challenges such as lack of reward, achievement, and growth.
