linkding

#software-practice | If you’ve only recently turned to the dark side, you might not have thought of all the possibilities yet. So here’s a list of code-review antipatterns, for the dark-side code reviewer who’s running out of ideas.

Relatable! Print out a Bingo card before reading.

3 months ago | View Shared by kos

|

The Worry Police

#software-practice

1 year ago | View Shared by kos

Writing Is Magic - Marc's Blog

#life #software-practice | Nearly every time I need to drive a difficult, subtle, or contentious decision, I write a document. Sometimes that’s half a page, sometimes its six pages. Sometimes much longer, although brevity is valuable. I see a few benefits to this approach that keep me coming back it it again and again.

As someone who mostly thinks through writing: Seconded!

1 year ago | View Shared by kos

|

KPIs, Velocity, and Other Destructive Metrics | Allen Holub

#software-practice

2 years ago | View Shared by kos

How to present to executives. | Irrational Exuberance

#software-practice | Everyone has worked with a terrible executive at some point in their career, but most executives aren’t awful. Almost all executives are outstanding at something; it’s just that often that something isn’t the topic you’re communicating about with them. When you combine that lack of familiarity with your domain with limited time for the topic at hand, communication is a challenge.

2 years ago | View Shared by kos

Why Devs (Should) Like Estimates

#software-practice | It’s clear there are many legitimate reasons why you will be asked for an estimate. And due to a number of reasons (guilt, good intentions, pressure from the estimate requestor) you might even give a best-guess estimate. However, as many of us have learned, while it is easy to give someone a number, it is much harder to give a number that is in any way accurate. And due to the dependencies that others put on the provided number, a bad estimate can sometimes do more damage than no estimate at all.

Fast forward 5 years since I bookmarked this, I still consider estimating difficult! But I especially like the tip about being dilligent about estimating a particular spec (rather than just requirements).

5 years ago | View Shared by kos

|

Status meetings are the scourge – Signal v. Noise – Medium

#software-practice #teamwork | [(Archived version)](https://archive.is/xgT85) Status meetings are about updating people right now. But most status updates have nothing to do with right now. Does everyone really need to hear this information at the exact same time? I’d bet not.

I'd add that, besides moving things to async, standups can be easily improved by encouraging people to have a meaningful discussion about their updates. If the discussion isn't relevant to most of the people in the room, then chances are the standup is too big too.

5 years ago | View Shared by kos

|

LINKDING

Shared bookmarks

User

Tags