Leadership lessons from growing 3x in 1 year
A tech leader shares lessons on scaling engineering teams 3x in a year, focusing on communication, delegation, and navigating uncertainty in a high-growth startup.
Swizec Teller is a software engineer, speaker, and educator sharing lessons from his journey from junior developer to Silicon Valley. He writes about engineering skills, career growth, mindset, and practical tactics for succeeding in tech.
43 articles from this blog
A tech leader shares lessons on scaling engineering teams 3x in a year, focusing on communication, delegation, and navigating uncertainty in a high-growth startup.
Explores two types of pair programming: expert-driven for speed and learner-driven for teaching, with tips for effective collaboration.
A software engineer's reflection on managing priorities and technical debt in a fast-growing company, comparing it to spinning plates.
Explores using HTMX to create server-side UI components without React, comparing it to tRPC and React Server Components for building interactive admin pages.
Explains how to replace brittle, synchronous side-effects in endpoints with a resilient, event-based system using queues for better error handling and performance.
A software engineer shares three highly effective production alerts for catching bugs and system issues, based on real-world experience.
Explores the responsibilities and mindset shift required to become a senior engineer, focusing on ownership, vision, and business impact.
A software engineer shares practical advice on mentoring, focusing on patience, framing advice, and navigating leadership growth within tech teams.
How Cursor's Slack integration with AI background agents automates coding tasks, changes developer workflows, and reduces mental load for tech leads.
A senior engineer shares their philosophy on mentoring software engineers, focusing on building trust, hands-on learning, and scaling team capabilities.
An engineering manager reflects on the role's challenges, feeling accountable but not directly credited, and compares it to surfing.
A software engineer explains the pitfalls of organizing code into generic 'utils' modules, using a real-world example of circular dependencies.
Argues that AI won't replace software engineers due to the inherent complexity of development and stakeholder management.
Summarizes key insights from three engineering management books, focusing on psychological safety, effective vs. efficient work, and managing hypergrowth.
Explores how Conway's Law influences software architecture, comparing solo development to collaborative teamwork and its impact on code structure.
Explores common pitfalls in software abstraction like DRY misuse, lasagna code, and util files, offering advice for scalable design.
The article critiques the DRY principle, explaining how its overzealous application can lead to complex, hard-to-maintain code and bad abstractions.
Explores the differences between websites and web applications, focusing on scaling challenges, user experience, and the benefits of modern frameworks like React.
A software engineer shares strategies for managing cognitive load and improving productivity through documentation, delegation, and focused task completion.
A hiring manager shares advice for technical interviews, framing them as a mutual sales pitch where candidates should position themselves as problem-solvers.