Search: tidyfirst.substack.com | Heykuki News

HK

Heykuki News

Top New Best Ask Show Jobs

Top New Best Ask Show Jobs

151.

Game over Absorbs Future Winnings

tidyfirst.substack.com

2 years ago

1 points

152.

Standups: Individual → Teammate – By Kent Beck

tidyfirst.substack.com

2 years ago

1 points

153.

Coupling and Cohesion

tidyfirst.substack.com

2 years ago

1 points

154.

Why Accelerate Deployment? – Kent Beck

tidyfirst.substack.com

2 years ago

1 points

155.

Sales Happen When Buyers Fear Missing Out – By Kent Beck

tidyfirst.substack.com

2 years ago

1 points

156.

The Saff Squeeze – By Kent Beck

tidyfirst.substack.com

2 years ago

1 points

157.

To Test or Not to Test? That's a Good Question

tidyfirst.substack.com

2 years ago

1 points

158.

TDD's Missing Skill: Behavioral Composition – By Kent Beck

tidyfirst.substack.com

2 years ago

1 points

159.

Design Is an Island – By Kent Beck

tidyfirst.substack.com

2 years ago

1 points

160.

The Pleasure of Pattern

tidyfirst.substack.com

2 years ago

1 points

161.

The Pleasure of Pattern – By Kent Beck (2010)

tidyfirst.substack.com

2 years ago

1 points

162.

tidyfirst.substack.com

3 years ago

1 points

163.

tidyfirst.substack.com

3 years ago

1 points

164.

Timing software design: “Later, if that's responsible”

tidyfirst.substack.com

3 years ago

1 points

165.

Envy Brings a Lesson

tidyfirst.substack.com

3 years ago

1 points

166.

Thinking About Code Review – Kent Beck

tidyfirst.substack.com

3 years ago

1 points

167.

Thinking About Code Review

tidyfirst.substack.com

3 years ago

1 points

168.

Abstract vs. Concrete Parameters (2008)

tidyfirst.substack.com

3 years ago

1 points

169.

Why “Empirical” (In empirical software design)? – by Kent Beck

tidyfirst.substack.com

3 years ago

1 points

170.

I chose “empirical” to describe my style of software design

tidyfirst.substack.com

3 years ago

1 points

171.

Thinking About Code Review

tidyfirst.substack.com

3 years ago

1 points

172.

Software design also saves money by discouraging errors

tidyfirst.substack.com

3 years ago

1 points

173.

Accountability is not blame (but easily becomes blame)

tidyfirst.substack.com

3 years ago

1 points

174.

Beyond Extreme Programming: Scaling to 1000s by reducing team dependencies

tidyfirst.substack.com

3 years ago

1 points

175.

Self, Team, Product

tidyfirst.substack.com

4 years ago

1 points