Engineering Team Management
363 items from kdeldycke/awesome-engineering-team-management ★2,615
-
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'.”
-
Management Challenges for the 21st Century - Managing Oneself thecompleteleader.org
“There is a great deal of talk today about the "mid-life crisis" of the executive. It is mostly boredom. At age forty-five most executives have reached the peak of their business career and know it.” In paragraph Ⅴ, you'll find why knowledge workers needs to manage themselves…
-
Eye Candy QA techreflect.net
Retelling of author's job at Apple: “John Louch was my boss. (…) John always shared everything with us, even the don't share this with your team stuff. We were people he trusted, so it was as it should be. It made you feel like you were part of something greater.” Or why…
-
Apple Aperture: Senior QA techreflect.net
How not to manage projects approaching deadlines: “cutting finished features, yelling at people, and working people to the point of nervous breakdowns. Then they came upon a brilliant idea: let's steal over a hundred engineers from other teams and then the project will…
-
The Apollo Syndrome teamtechnology.co.uk
A phenomenon discovered by Dr Meredith Belbin, and exposed in his 1981 book on Management Teams, where teams of highly capable individuals can, collectively, perform badly.
-
How to Read a Paper svr-sk818-web.cl.cam.ac.uk
Outlines a practical and efficient three-pass method for reading research papers.
-
Team Objectives – Overview svpg.com
Why OKRs might not work at your company: 1. You're still using feature teams instead of product teams; 2. Mixed-up manager and individual objectives; 3. Leadership opting-out of active management.
-
Good sleep, good learning, good life supermemo.guru
An e-book-sized synthesis on sleep research “with a view to practical applications, esp. in people who need top-quality sleep for their learning or creative achievements.”
-
How Complex Systems Fail stuff.mit.edu
“Short treatise on the nature of failure; how failure is evaluated; how failure is attributed to proximate cause; and the resulting new understanding of patient safety”.
-
The Elves Leave Middle Earth – Sodas Are No Longer Free steveblank.com
Company stopped providing free soda. The engineers were very upset, but it was just soda and they could afford it. But really it wasn't soda. Soda was the canary in the coal mine, triggering an exodus of its best engineers.
-
The Most Important Performance Management Rule For Software Engineers staysaasy.com
“Merge code every week. That's what you should be saying to your new Software Engineering hire.”
-
Optimize Onboarding staysaasy.com
“Your organization has painfully slow onboarding. Endless HR videos, slow security processes, a mountain of fragile technology setup - these all make for a shitty and counterproductive start at a company. Optimize your onboarding to get people doing what you hired them to do.”
-
Why It's Easier to Manage 4 People Than It Is to Manage 1 Person staysaasy.com
“Avoid at all costs the combination of: new manager, 1 report, report is new-to-industry, manager is not a subject-matter expert.”
-
The Intangible Skills You Can't Interview For staysaasy.com
“1) Cut-Through on Crappy Tasks; 2) Knowing How to Finish; 3) Knowing How to Start; 4) Giving (And Receiving) Diagonal Feedback; 5) Harnessing the Value of Intangibles.”
-
Advice to New Managers: Don't Joke About Firing People staysaasy.com
“The second you became their manager you forfeited the right to joke around in any capacity about their employment at the company.”
-
StaffEng staffeng.com
Once you've reached the Senior Software Engineer level, you're at the crossroad. Either you pursue engineering management or continue down the path of technical excellence to become a Staff Engineer. This isa collection of guides about the later position.
-
Requirements volatility is the core problem of software engineering stackoverflow.blog
“Start by accepting that change is inevitable. (…) As a consequence of this, software is never finished, only abandoned. (…) This means that no software product is ever exactly, perfectly satisfactory.”
-
Avoiding burnout as an ambitious developer stackoverflow.blog
“Be willing to say no; Know what you don't want; Use your energy level realistically; Be kind to your future self”.
-
Burnout From an Organizational Perspective ssir.org
“Extensive research by the military on sustainable performance in stressful conditions teaches that leaders should become champions of health, rather than taskmasters.” Describe the symptoms of toxic organizations and how managers can protect their teams from systemic burnout.
-
Write an Excellent Programming Blog speakerdeck.com
Tips on structure and style to produce great blog posts.
-
Netflix Culture slideshare.net
“The actual company values, as opposed to the nice-sounding values, are shown by who gets rewarded, promoted, or let go.”
-
How Slack Harms Projects silasreinagel.com
“Promote a false sense of urgency, destroy focus, allow for bypassing project prioritization, strip away essential business context, encourage poorly thought-out communication”. To remediate this, see How to Use Slack and Not Go Crazy article.
-
It's Not Sabotage, They're Drowning shermanonsoftware.com
Some kind of push backs shouldn't be interpreted as intentional sabotage, but as drowning people sinking the lifeboat in an attempt to save themselves.
-
Software effort estimation is mostly fake research shape-of-code.com
“The NASA dataset contains 93 rows (that is not a typo, there is no power-of-ten missing), COCOMO 63 rows, Desharnais 81 rows, and (…) the China dataset contains 499 rows.”
- next page of items loading…
