#Feedback

Como fazer uma apresentação de PowerPoint brilhante

O texto defende que uma apresentação deve vender uma ideia ao combinar emoção, fala, slides e material escrito, com regras de concisão, imagens profissionais e feedback claro.

How I give high-quality feedback quickly

The newsletter argues that feedback can be both fast and high quality if you focus on the highest-leverage work, start with structure when needed, and use the right medium to keep the process sustainable.

How to Identify Silent Disagreements?

The post lists signs of hidden disagreement in meetings and execution, and suggests concrete ways to surface concerns early so they do not delay decisions or derail projects.

How a Senior Engineer Effectively Onboards at a New Job

The article says senior engineers should spend the first weeks learning the org, meeting teammates, asking questions, setting achievable 90-day goals, and finding small early wins while staying open to feedback.

The Crucial Difference Between Nice and Kind Leadership

The post argues that nice leadership avoids conflict and protects comfort, while kind leadership tells the truth, makes hard calls, and supports long-term growth.

5 Ways Incompetent Leaders Dis-Empower Good People

The page argues that control-oriented leaders drain good people, while skillful leaders expand power by including others, giving choice, and focusing on meaningful work and candid feedback.

Onboarding de devs: Como integrar novas pessoas ao time

O texto defende um onboarding estruturado de 3 meses, com alinhamento de expectativas, trilhas sobre produto e empresa, desafios práticos, imersões em outros times e avaliação com feedback.

Hate Your Own Work and Ship It Anyway

The beauty and terror of negative feedback

A first conference talk gets mostly praise, then a bare anonymous 4/10 review. Amanda Mayfield traces why it stung and turns the discomfort into a plan to redesign the talk.

The Ultimate Guide to Onboarding Software Engineers

The article argues that engineering onboarding needs structure, emotional support, and expectation management across team, organization, and culture, then lays out a 30-60-90-150 day framework.

Six tips to improve your code review skills

The article says code review works best when reviewers test changes locally, ask questions instead of making blunt statements, praise good work, label comments, separate blocking from non-blocking issues, and add extra explanation to reduce review rounds.

7 ways of giving feedback that encourage change

The article says feedback should be timely, specific, contextual, and rooted in care so it actually helps people change behavior instead of being ignored or misread.

Como não se tornar o chefe que você odeia

O texto defende que o líder precisa assumir responsabilidade, buscar aconselhamento, dar feedback contínuo com empatia e lembrar que muita gente sai por causa do chefe, não da empresa.

Code Review Etiquette

The article explains why code reviews need shared etiquette, how harsh feedback can hurt collaboration, and how to keep critiques focused, specific, and calm.

3 Secrets to Giving Corrective Feedback with Ease and Confidence

The post says corrective feedback helps average performers improve and top performers excel. It recommends giving many positives, waiting for a good moment, and stating the issue quickly and clearly.

Writer as Coder: The Iterative Way to Write a Book

Babauta compares book writing to iterative software development and describes a process of alpha testing, feedback, quick revisions, wider testing, and later editions to improve a nonfiction book before and after print.

The hardest and easiest way to be a better coder

The essay argues that coder-to-coder communication is central to programming, from emotional self-awareness to readable code and kinder feedback, even if improving it is hard.