Engineering Team Management
363 items from kdeldycke/awesome-engineering-team-management ★2,615
-
What makes a Senior Dev news.ycombinator.com
“Time, man. You gotta do your fucking time.”
-
I try to optimize my code around reducing state, coupling, complexity and code, in that order news.ycombinator.com
An engineer's perspective on which priorities should be addressed first to increase robustness of systems.
-
As an Employee, You Are Disposable nelson.cloud
“It's okay to like your job and employer. Just understand that, as an employee, you are disposable.” Also: “This is not news. If you are loyal to your employer and do not own a significant part of the organization, then you should take a good hard look at why you're loyal…
-
Things I Learnt from a Senior Software Engineer neilkakkar.com
“I sat next to a senior software engineer for a year. Here's what I learnt.”
-
Early-career setback and future career impact nature.com
“Despite an early setback, individuals with near misses systematically outperform those with narrow wins in the longer run.”
-
What senior engineers do: fix knowledge holes mooreds.com
“This is the textbook definition of a senior engineer. You see a problem, you solve it (thoroughly), you document it and you level up your team.”
-
7 absolute truths I unlearned as junior developer monicalent.com
“1. I'm a senior developer; 2. Everyone writes tests; 3. We're so far behind everyone else (a.k.a. tech FOMO); 4. Code quality matters most; 5. Everything must be documented; 6. Technical debt is bad; 7. Seniority means being the best at programming”.
-
“Why does the tire company rate restaurants” mobile.x.com
A great example on why you should investigate complementary businesses.
-
Notes on Technical Writing mkaz.blog
An effective list of do and don't when it comes to writing documentation.
-
Things I have learnt as the software engineering lead of a multinational minnenratta.wordpress.com
Some interesting points here, some others needs to be challenged.
-
The Greatest Sales Deck I've Ever Seen medium.com
“1. Name a big change in the world; 2. Show there'll be winners and losers; 3. Tease the promised land; 4. Introduce features as "Magic Gifts"; 5. Present evidence that you can make the story come true.”
-
The product roadmap is dead: welcome to the age of problem roadmaps medium.com
“Fall in love with your problems and not with your solutions.”
-
Book Summary of "Who: The A Method for Hiring" medium.com
The essential of Who, a popular book on recruiting executives.
-
Let's have no managers, instead of managers with no engineering experience medium.com
The title is misleading, article's argument is: we don't need project managers if we already have product managers and scrum masters.
-
You're Not Managing a Team of Software Engineers, You're Managing a Team of Writers medium.com
Because writing software is “a creative process which is by its nature unpredictable and personal, in an environment which craves certainty, predictability and consistency.”
-
Mental Models I Find Repeatedly Useful medium.com
Huge compiled list of mental models. Became the basis of book.
-
Levels of abstraction in engineering management medium.com
Another take on the differences between Manager, Manager of Managers, Head of Org and Head of Function.
-
All the best engineering advice I stole from non-technical people medium.com
“It's intriguing that the stuff that really seems to make a difference in the quality of software never seems to be about software.”
-
Strong Opinions, Weakly Held — a framework for thinking medium.com
“Allow your intuition to guide you to a conclusion, no matter how imperfect — this is the 'strong opinion' part. Then – and this is the 'weakly held' part – prove yourself wrong.”
-
The different skills needed to be a successful CTO madewithlove.be
The premise is a little misleading, as what is detailed there is the journey, in a startup, of the technical founder growing with the company to become a CTO. At which point the position described in the article is not CTO, but VP of Engineering.
-
100+ Lessons Learned for Project Managers llis.nasa.gov
122 aphorisms providing insights into NASA project management success. Covers design, decision-making, managing staff, working with superiors and contractors.
-
Recurring opinions or productive improvements — what agile teams actually discuss in retrospectives link.springer.com
An 3-years analysis of a team's retrospectives, with dire conclusions: people keep forgetting what they already learned, keep discussing unsolveable problems out of their control, and keep debating opinions based on biased interpretations or incorrect understandings.
-
levels.fyi levels.fyi
💸 Compares salary range, compensation charts, and benefits across big tech companies.
-
How the Digg team was acquihired lethain.com
Acqui-hire of a whole team can be seen as a type of reorg. In which managers will have to negotiate the new employment contracts in bulk in one or two days: “Because acquihires are “star” oriented, if you're a senior leaders who doesn't explicitly refuse to move forward…
-
Developers spend most of their time figuring the system out lepiter.io
“A hand drawn picture about the current system is a belief. Decisions should never be based on beliefs. Not in engineering. (…) As software is highly contextual we cannot predict specific problems. We can only predict classes of problems.” And that's why it is hard to estimate…
-
I coached CEOs, founders, VCs and other executive: These are the biggest takeaways leowid.com
Excerpt: “We're all just big, complicated bags of emotion walking around; Power comes with the ability to receive a No; Learning to manage your focus, not your time.”
-
Team Leader Venn Diagram larahogan.me
“A tool for gaining a shared understanding of responsibilities”.
-
Work at different management levels larahogan.me
A great progressive breakup of what it feels like to work at different levels of management.
-
Manager Energy Drain larahogan.me
“How do I handle how tired I am as a manager? 1. Defrag your calendar; 2. Delegate messy and unscoped projects; 3. Say no.”
-
Questions for our first 1:1 larahogan.me
A personal list of high-level questions from a manager.
-
Dear Startup: You have no idea how much that costs kyleprifogle.com
“We are completely clueless about how long things should take.” Here is a trick to handle expectation of unreasonable estimates.
-
The Good, the Bad and the Ugly Standup kristoff.it
Author experienced 3 formats of stand-ups before ending with one working for his team, and concludes that “the details that make up a good meeting are subtle and the pursuit of an artificial standard of aesthetics will prevent you from doing the necessary experimentation to…
-
Managing Remote Teams - A Crash Course klinger.io
Compilation of easy rules and processes to bootstrap a remote team.
-
On Being A Senior Engineer kitchensoap.com
“I expect a 'senior' engineer to be a mature engineer.”
-
Culture Queries keyvalues.com
A sample of question to ask in job interviews to try to understand the values of a company.
-
UX Core keepsimple.io
105 cognitive biases with simple descriptions, brief and detailed examples.
-
Rethinking the Hiring Process karllhughes.com
“Testing programmers at something they aren't actually expected to be good at and expecting to learn something about how they would work at your company is delusional, and I think these kind of interviews only serve to make the hiring team feel smarter and ensure better…
-
Salary Negotiation: Make More Money, Be More Valued kalzumeus.com
“Your salary negotiation — which routinely takes less than 5 minutes to conclude — has an outsized influence on what your compensation is.”
-
Get your work recognized: write a brag document jvns.ca
There's this idea that, if you do great work at your job, people will (or should!) automatically recognize that work and reward you for it with promotions / increased pay. In practice, it's often more complicated than that.
-
When your coworker does great work, tell their manager jvns.ca
Highlighting unseen work in public allows managers to recognize efforts their reports are doing. Still, there is some cases in which it might put your colleague in a tight spot. So always ask if it's ok first.
-
Noise, Cognitive Function, and Worker Productivity joshuatdean.com
“An increase of 10 dB reduces productivity by approximately 5%.”
-
LEGO blocks and organ transplants johndcook.com
“People have been comparing software components to LEGO blocks for a couple decades. (…) Integrating two software systems is usually more like performing a heart transplant than snapping together LEGO blocks.”
-
Incentive Pay Considered Harmful joelonsoftware.com
“Incentives (or bribes) simply can't work in the workplace. (…) Most software managers have no choice but to go along with performance review systems that are already in place. If you're in this position, the only way to prevent teamicide is to simply give everyone on your team…
-
A high-resilience org chart jessitron.com
“If you know what problem you're solving and you know how to solve it, a bureaucratic organization will do. Stick with what you know. If you're writing software, that's a generative activity. You need a high-resilience org chart. Fewer boxes, more flexibility.”
-
Failed #SquadGoals - Spotify doesn't use "the Spotify model" and neither should you jeremiahlee.com
“Why it didn't work? 1. Matrix management solved the wrong problem; 2. It fixated on team autonomy; 3. Collaboration was an assumed competency; 4. Mythology became difficult to change”.
-
Why it's difficult to build teams in high growth organisations jchyip.medium.com
Describes 3 different approach a manager can take to accommodate new people in the team: 1. Sink or Swim; 2. Split and Absorb; 3. Absorb and Split.
-
My questions for prospective employers (Director/VP roles) jacobian.org
Be prepared to ask them as a recruiter or being asked about them for senior management roles.
-
CTO vs VP Engineering: What's the Difference? ivyexec.com
CTO manage a small staff of hackers. VP of Engineering lead an organization of engineers.
-
Programmer Moneyball: Challenging the Myth of Individual Programmer Productivity insights.sei.cmu.edu
“Since software project managers have limited ability to evaluate individual developer capability, they should rely on a productive environment and developing talent.”
-
Do engineering managers need to be technical? increment.com
Yes. “Looking forward to the next 30 years of management trends, only a few things seem certain: Managers should be technical, and the definition of technical will continue to change.”
- next page of items loading…
