Speeding up code review with `small-change`(lethain.com)
38 points by alexmolas | 22 comments
Will Larson describes Imprint's `small-change` process, which uses CI checks and AI review skills to fast-track approval of small, low-risk pull requests.
32 stories tagged engineering-management, newest first.
38 points by alexmolas | 22 comments
Will Larson describes Imprint's `small-change` process, which uses CI checks and AI review skills to fast-track approval of small, low-risk pull requests.
60 points by keyle | 36 comments
A blog post on Terrible Software titled "The Brain Sandwich," likely about engineering management and how to deliver feedback or communicate ideas.
23 points by weli | 23 comments
A personal blog post by a new Head of Engineering at a startup reflecting on hiring and how much more than skills it takes to get a job today.
346 points by amortize | 72 comments
Blog post by Sujith Jay Nair on how staff engineers on platform teams find what to build next using signals from systems, users, organization, and industry.
45 points by fagnerbrack | 38 comments
A Substack post by Mark Grebler describing his practice of asking interviewers for real-time feedback as a closing move at the end of job interviews.
382 points by mooreds | 205 comments
Blog post by Michael Heap recounting an SVP who refused the details of a failure, arguing that explanations make problems seem reasonable so they recur.
41 points by fagnerbrack | 29 comments
A Manager.dev newsletter post by Anton Zaides recounting a hackathon built with Lovable to explain to business people why building software is still hard.
398 points by tosh | 225 comments
Dan McKinley's 2015 essay arguing that engineering teams should favor proven, well-understood technologies and spend limited 'innovation tokens' carefully.
877 points by florianherrengt | 785 comments
Blog post arguing that AI-generated code floods senior engineers with huge PRs and is hollowing out the middle tier of software engineering roles.
569 points by throwarayes | 495 comments
A Pragmatic Engineer newsletter deepdive by Gergely Orosz reporting on how Meta leadership's AI-driven changes are affecting its engineering organization.
372 points by kiyanwang | 238 comments
Blog post by Viktor Cessan analyzing the financial costs of software teams, why organizations lack visibility into them, and how LLMs change the picture.
364 points by flail | 259 comments
A Manager.dev newsletter post by Anton Zaides arguing that engineers should reconsider accepting promotions to engineering manager roles.
450 points by mattjhall | 268 comments
Sean Goedecke's blog post on how he approaches estimating software work as a staff engineer, arguing accurate estimation is impossible.
514 points by jampa | 133 comments
A blog post by Jampa Uchoa sharing non-obvious lessons learned over ten years working as an engineering manager.
537 points by yuppiepuppie | 263 comments
Blog post by Andrew Graham-Yooll on the promotion advice "try to take my position": doing the next-level job and taking on responsibility before getting the title.
380 points by mooreds | 281 comments
Blog post on the Helmet Hair blog arguing that most technical problems in software teams, such as accumulated technical debt, are really people problems.
469 points by matheusml | 245 comments
A Terrible Software blog post arguing that engineers should engage in, rather than avoid, workplace politics.
322 points by mooreds | 163 comments
A blog post on the Chaotic Good Engineering Management newsletter about how to lead a team when morale and the general mood are low.
405 points by jnord | 119 comments
Blog post by Ibrahim Diallo on how to lead effectively when managing a team of experts who know more than you.
554 points by jnord | 475 comments
IEEE Spectrum guest article by Honeycomb CTO Charity Majors arguing against the myth of the "10x engineer" and in praise of normal engineers on strong teams.
551 points by simonebrunozzi | 187 comments
A GitHub-hosted Markdown book by Zach Goldberg, The Startup CTO's Handbook, covering essential skills and best practices for leading high-performing engineering teams.
333 points by zdw | 211 comments
A Jessitron blog post discussing the tension between hitting OKRs (objectives and key results) and actually doing your job well.
356 points by kaycebasques | 215 comments
Steven Sinofsky's Hardcore Software essay on engineering and systems patterns that sound good ("Let's just...") but almost never work as intended.
586 points by zdw | 363 comments
A rachelbythebay blog post in which the author describes changing her view on measuring employee performance with metrics.
451 points by zdw | 216 comments
A July 2024 blog essay by Yossi Kreinin arguing that competent management makes some desirable outcomes, like efficiency, harder to achieve than incompetent management does.
345 points by jbredeche | 134 comments
First Round Review article on unexpected anti-patterns for engineering leaders, drawing lessons from Stripe, Uber and Carta.
350 points by mrled | 210 comments
Ben Collins-Sussman's personal blog FAQ explaining his layoff from Google after 18 years as an Engineering Director and reflecting on mass tech layoffs.
462 points by serialx | 218 comments
Blog post by Swizec Teller arguing that software engineering salaries come from one of three company budgets, which shapes engineers' daily work and career trajectory.
405 points by kanodiaashu | 121 comments
Ask HN thread where a first-time startup CTO requests book and blog recommendations, with comments suggesting titles like An Elegant Puzzle and The Staff Engineer's Path.
358 points by nlavezzo | 226 comments
A Medium essay by David K. Caudill arguing that companies eliminating dedicated QA teams may have harmed software quality.
346 points by mooreds | 105 comments
GitHub repository for The Startup CTO's Handbook, a book on leadership, management, and technical topics for leaders of software engineering teams.
357 points by admp | 122 comments
Blog post by Ben Kuhn, adapted from a talk at Anthropic, describing mistakes he made as a new manager and strategies to mitigate them.