Engineering Team Management
363 items from kdeldycke/awesome-engineering-team-management ★2,615
-
source x.com
).
-
source x.com
) - Maybe the best indicator of a happy team is how little it is disturbed outside office hours.
-
Bryan Cantrill defines that the role of management x.com
“is in constructing that environment, not micromanaging it. If engineering performance is suffering, it's (likely) a management problem: wrong problem, wrong mission, or wrong team -- or all three.”
-
Advice to new managers x.com
9 fundamental principles of the behavior required to be a great manager.
-
sacrificial lamb product x.com
a massive unpopular re-architecture required to pave the way for future innovative release. That's the cautionary tale of why you should be ready for intense criticism and adversity, if by chance or fate your wander down the path of monumental changes in a business software.
-
Devs I really enjoy pairing with x.com
“Don't act like know-it-all; Openly admit if they don't know something; Try to figure stuff out together”.
-
source x.com
).
-
Amazon Wants to 'Win at Games.' So Why Hasn't It? wired.com
“Any product manager can go between any business—from groceries to film to games to Kindle. The skillset is interchangeable. They just have to learn the particular market.”
-
Fizz Buzz Test wiki.c2.com
“Designed to help filter out the 99.5% of programming job candidates who can't seem to program their way out of a wet paper bag.”
-
Story Points Revisited web.archive.org
The alleged inventor of story points says they are probably a mistake.
-
What Google Learned From Its Quest to Build the Perfect Team web.archive.org
“Google's data indicated that psychological safety, more than anything else, was critical to making a team work. (…) The behaviors that create psychological safety — conversational turn-taking and empathy — are part of the same unwritten rules we often turn to, as individuals…
-
Detecting Agile Bullshit web.archive.org
US Department of Defense guide to detect software projects that are really using agile development versus those that are simply waterfall or spiral development in agile clothing (“agile-scrum-fall”).
-
Akin's Laws of Spacecraft Design web.archive.org
Lots of wisdom about space program management.
-
Great PMs don't spend their time on solutions web.archive.org
Not on solutions, no. But on customer's problems.
-
Asynchronous Communication: The Real Reason Remote Workers Are More Productive web.archive.org
“Remote workers are more productive than their office-bound counterparts.”
-
Why new hires often get paid more than existing employees web.archive.org
“and why the best way to get a bigger pay is to move to a new job.”
-
Why individual OKRs don't work for us web.archive.org
Spotify decision to stop using OKRs for individuals.
-
Disney's Frozen web.archive.org
.
-
How to discipline overeager engineer web.archive.org
Over-achieving talent is looking for a management promotion. Management does not recognize effort. Engineer become disgruntled and management is looking to discipline him. A case-study of a bad situation in which both side shows clumsiness.
-
How to Freaking Find Great Developers By Having Them Read Code web.archive.org
“Instead of writing code, consider having the candidate read existing code and talk about how it works. 1) Reading code is 95% of what a developer does as part of their job. 2) A candidate can tell you a lot about their programming skill in the first five minutes of reading. 3)…
-
Reverse Engineering A Successful Lifestyle Business web.archive.org
Targets lifestyle entrepreneur, but still full of fantastic quotes from reference books on customer relation, pricing and marketing a product.
-
The Technical Interview is an Ego Trip web.archive.org
Starts with anecdote of developers using a job interview as a vehicle to demonstrate their superiority. Then the author details a reasonable interview process that is trying to not waste anyone's time.
-
Presentation Rules web.archive.org
A set of 16 rules to avoid boring and ineffective presentations, and have your message reach your audience.
-
Industry Data Models web.archive.org
A huge list of database templates collected over 25 years by Barry Williams to represent any business process.
-
Kasparov's Law web.archive.org
Weak human + Machine > Machine > Strong Human.
-
-
FizzBuzz 2.0: Pragmatic Programming Questions for Software Engineers web.archive.org
Five multiple-choice questions to easily separate the real software engineers from the rest.
-
Symptoms of Groupthink web.archive.org
Overconfidence, tunnel vision and conformity pressure can led a group astray.
-
The Horrifically Dystopian World of Software Engineering Interviews web.archive.org
The dark side on relying too much on algorithm challenges.
-
Intellectual Humility Cheat Sheet web.archive.org
“is about being open and able to change your mind about important things, and being able to discern when you should.”
-
Your daily standups should be async. Here's why web.archive.org
“Daily, real-time meetings aren't practical for remote teams” might be the best practical reason.
-
How to Celebrate the Small Wins web.archive.org
My takeaway: “Celebrating Slow Progress; Hunt for Key Milestones”.
-
Technical Debt Is Like Tetris web.archive.org
Another way to explain technical debt: “Scenarios like these create technical debt within the product code. A buried gap in Tetris represents technical debt. (…) Paying down technical debt keeps you competitive. It keeps you in the game.”
-
US Air Force's Strategic Leadership Studies web.archive.org
A reference of leadership's competencies and skills.
-
How to answer the “What's your current salary?” job interview question web.archive.org
This article explain the dynamic of that sneaky question and how to defuse it.
-
How to Misuse Code Coverage web.archive.org
“If a part of your test suite is weak in a way that coverage can detect, it's likely also weak in a way coverage can't detect.” I.e. the great benefit of a coverage report is that it tells you what you forgot to think about when you wrote the test suite itself (source).
-
The IT revolution and southern Europe's two lost decades voxeu.org
If you still doubt management culture could make or break an industry: “inefficient management practices have kept southern European firms from taking full advantage of the IT revolution”.
-
-
We Cancelled Standups and Let The Team Build. Here's What Happened… usehaystack.io
Team felt burned out by long, daily status update meetings masquerading as standups. Eliminating these faux standups got the team back on track.
-
6 Signs You're a Micromanager (And What to Do Instead) unito.io
“You're more involved with your employees than ever, yet they seem disgruntled, unhappy, and less productive than usual. Your check-ins seem to go unappreciated. And no one seems receptive to all of your great feedback on their work. What's going on? Well, we hate to break it…
-
Developer Tropes: "Google does it" tomaytotomato.com
It's cargo-cultish to imitate the big names in our industry as a path to success. Instead, the take home from this article “would be that managers and other leaders should be like ecologists; who measure, observe and nurture their ecosystems. Doing so will help build a unique…
-
I wasted $40k on a fantastic startup idea tjcx.me
A tale of building a product no user want to pay for. “You can't just create value for the user: that's a charity. You also can't just create value for your company: that's a scam. Your goal is to set up some kind of positive-sum exchange, where everyone benefits, including…
-
Should we take a few long holidays, or lots of short ones? timharford.com
Short ones. “Reason one: holiday memories tend to depend not on how long the holiday was, but on the intensity of the experiences. Reason two: a change of activity can be a spur to creativity. Reason three for taking a short break: if we need rest to prevent exhaustion, a…
-
4 Clues to Identify a Destructive Leader tilt365.com
“1. I'm kind of a big deal! 2. None of this is my fault! 3. Just do what I say! 4. Trust me; I'm never wrong.”
-
source threadreaderapp.com
) - Contemplating to switch from the industry? The grass is not greener in academia. Given a significant size, any organization comes with its political game.
-
A Good Tech Resume thetechresume.com
A compilation of advice and example, but containing a good description of a typical hiring pipeline.
-
The principles of Amazon service-oriented collaboration theregister.com
A compilation of anonymous sources from AWS which ehoes the interview above: “teams are ostensibly autonomous and can make any important decision needed to meet their goals.”
-
The Punctuation Guide thepunctuationguide.com
Simple reference on how (and why) to use these special characters.
-
First principles and asking why theengineeringmanager.com
“Our ability to think in abstractions can weaken our judgement, as those abstractions may no longer be as true as they once were. Also a similarly dangerous evolutionary trait is our ability to think in analogy, where we make assumptions based on the comparison of two things…
-
Huge success in business is largely based on luck theconversation.com
“Management research and education should focus on prescriptive theories that can help business practitioners move from 'incompetent to OK', rather than focusing on those that address how to move from 'good to great'.”
- next page of items loading…
