Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
KentBeck
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
I chose “empirical” to describe my style of software design
(tidyfirst.substack.com)
1 points
by
KentBeck
3y ago
|
0 comments
32.
▲
How I came to write “Tidy First?” tl;dr it took 18 years
(tidyfirst.substack.com)
173 points
by
KentBeck
4y ago
|
36 comments
33.
▲
Software design also saves money by discouraging errors
(tidyfirst.substack.com)
1 points
by
KentBeck
4y ago
|
0 comments
34.
▲
Accountability is not blame (but easily becomes blame)
(tidyfirst.substack.com)
1 points
by
KentBeck
4y ago
|
0 comments
35.
▲
Beyond Extreme Programming: Scaling to 1000s by reducing team dependencies
(tidyfirst.substack.com)
1 points
by
KentBeck
4y ago
|
0 comments
36.
▲
by
KentBeck
4y ago
I agree about the importance of alignment. The recent evolution in my thinking is to take into account the power differentials between the folks who need to be aligned. As The Boss it's easy to say, "Everyone should be aligned,&qu
37.
▲
Boss' Dilemma: Taking Responsibility Signals Cooperation
(tidyfirst.substack.com)
54 points
by
KentBeck
4y ago
|
30 comments
38.
▲
Responsibility: Consequences Flow Towards Power
(tidyfirst.substack.com)
13 points
by
KentBeck
4y ago
|
11 comments
39.
▲
The Pie Problem: A performance assessment parable
(geekincentives.substack.com)
35 points
by
KentBeck
4y ago
|
2 comments
40.
▲
Programmers Underpaid? Labor vs. Capital
(geekincentives.substack.com)
5 points
by
KentBeck
4y ago
|
0 comments
41.
▲
by
KentBeck
4y ago
JUnit
42.
▲
Cloud development environments tame complexity by reducing state
(medium.com)
57 points
by
KentBeck
4y ago
|
39 comments
43.
▲
by
KentBeck
4y ago
This is a 40-year-old mystery for me--why is it so very hard to get agreement about when & how much to design. Moving too much of the design too soon doesn't work. Moving it too late doesn't work, not in the long run. But why
44.
▲
Software design decisions are (mostly) reversible
(tidyfirst.substack.com)
2 points
by
KentBeck
4y ago
|
1 comments
45.
▲
Tune Software Development for Rate of Change, Not Rate of Progress
(medium.com)
2 points
by
KentBeck
4y ago
|
0 comments
46.
▲
Work/life balance should be difficult
(medium.com)
102 points
by
KentBeck
5y ago
|
183 comments
47.
▲
Fixed equity grants become toxic to hard work in later growth
(geekincentives.substack.com)
1 points
by
KentBeck
5y ago
|
0 comments
48.
▲
Background Work: Establishing credibility by indulging engineering curiosity
(medium.com)
41 points
by
KentBeck
5y ago
|
2 comments
49.
▲
by
KentBeck
5y ago
They're convex--small investment, small chance of a large return. Also, I've been curious what mechanism will fund creators creating & NFTs seem like a contender.
50.
▲
A Death-Aware Career Plan
(medium.com)
75 points
by
KentBeck
5y ago
|
64 comments
51.
▲
How Meditation Works for Me
(medium.com)
1 points
by
KentBeck
5y ago
|
0 comments
52.
▲
Meta-meta-cognition: reflecting on mind-mapping my thinking habits
(medium.com)
7 points
by
KentBeck
6y ago
|
0 comments
53.
▲
Meta-meta-cognition: reflecting on mind-mapping my thinking habits
(mindmappinggetsmoreofmybraininvolvedwheni'mtryingtoseethestructureimpliedbyparticularexamples.here'sanexample.https)
1 points
by
KentBeck
6y ago
|
0 comments
54.
▲
Does Pay-for-Performance Perform?
(medium.com)
1 points
by
KentBeck
6y ago
|
0 comments
55.
▲
by
KentBeck
6y ago
BadCookie, you and I have different constraints. The way you're thinking about accumulating assets makes sense given a child who will need assets and can't accumulate them themselves. The way I'm thinking makes sense given th
56.
▲
Tech compensation is biased toward the long-term. Fine if you have a long term
(medium.com)
16 points
by
KentBeck
6y ago
|
7 comments
57.
▲
by
KentBeck
6y ago
I recommend mouthwash. Something minty fresh.
58.
▲
We aren’t owed an audience for our “feedback”
(medium.com)
2 points
by
KentBeck
6y ago
|
2 comments
59.
▲
Monolith -> Services: A Sketchy Approach
(medium.com)
59 points
by
KentBeck
6y ago
|
12 comments
60.
▲
by
KentBeck
6y ago
That would be the "belligerent asshole" interpretation, one that I applied for the first 10 years of my career. As an engineer, I often have intuitions about what I should work on. I'm saying those intuitions are valuable. Ex
More ›