Found in 5 comments
guiambros · 2018-09-08 · Original thread
As soon as you start hiring people, strongly recommend reading "Radical Candor" [1].

[1] https://www.amazon.com/Radical-Candor-Kim-Scott/dp/B01KTIEFE...

guiambros · 2018-07-28 · Original thread
If the person delivering feedback doesn't "care" about the person receiving it, you'll never get the tone right, and will never create the emotional connection that is so necessary for the feedback to be internalized. The receiving end will hear the words, but much harder to act on it.

Kim Scott wrote extensively about this in her book "Radical Candor" [1]. Do yourself a favor and skip the video snippets and TED talks, and go straight to the book (so you don't get caught up on the click-baity "radical candor quadrant"). This is particularly true if you manage teams - or ever aspire to.

The author is a former Googler and used to report to Sheryl Sandberg during the early days, before going to Apple and working with Jobs and Tim Cook, and more recently with Dick Costolo on Twitter.

This is one of those books I wish I had read when I started my career. It would have saved me from so much pain and mistakes learned the hard way.

[1] https://www.amazon.com/Radical-Candor-Kick-Ass-Without-Human...

glorithm · 2018-07-13 · Original thread
The Subtle Art of Not Giving a F*ck, by Mark Manson

https://www.amazon.ca/Subtle-Art-Not-Giving-Counterintuitive...

Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity, by Kim Scott

https://www.amazon.ca/Radical-Candor-Kick-Ass-Without-Humani...

kolinko · 2018-05-02 · Original thread
> - beware of premature optimization. Spend that time on defensive code, comments and tests. Optimize based on measurements, not feelings

In some contexts - rapid development and prototyping especially - defensive coding is not much different than premature optimisation. I fired a developer once, because he couldn't let go of his defensiveness whereas what the project needed was a buggy, proof of concept, version.

Also, offensive programming is a thing, and possibly less bug-prone in some situations:

http://johannesbrodwall.com/2013/09/25/offensive-programming...

> - be nice and never argumentative

This too depends on context and a team. Personally, I prefer argumentative people (within reason) to nice ones - the last thing I want is for a developer to do something he believes is stupid, and not tell me about it.

Having said that, being too argumentative is not good either - some devs seem to build their self esteem based on the number of arguments they won. No no no.

> - take notes when getting tasks and make sure you don’t miss anything

This is super-true. Also - read a tutorial on active listening. I had a team of developers once who literally made zero notes from the meetings.

> - be humble when getting criticism and be merciful when giving one

Just not too merciful :) A good book on managing people, including giving feedback: https://www.amazon.com/Radical-Candor-Kim-Scott/dp/B01KTIEFE...

As for being humble when getting feedback - I'd add "don't afraid to ask as many questions as needed for understanding". There is a difference between being humble, and non-confrontational. The former acknowledges they may be wrong, the latter hides the fact that they think they are right.

> - count to ten before sending an angry / escalation email

Or just call instead.

> - don’t work yourself to death, have limits

But acknowledge that crunching - within reason - can be fun :)

Loved Radical Candor (https://www.amazon.com/Radical-Candor-Kick-Ass-Without-Human...). I thought it was going to be stupid and glitzy, but it was well written and funny and very insightful
View this Book on Amazon