KentBeck

17 ms·

151.
Taming Complexity with Reversibility(facebook.com)
66 points by KentBeck 11y ago|2 comments
152.
Patterns Enhance Craft Step 3: A Few Good Solutions(facebook.com)
2 points by KentBeck 12y ago|0 comments
153.
by KentBeck 13y ago
I'm about to turn 53. I spend most of my day coaching younger programmers at Facebook (because they're almost all younger). We pair program and talk. I work on speculative projects, some consumer-oriented, some programming tools a
154.
Prefer intrinsic state in JavaScript(facebook.com)
1 points by KentBeck 13y ago|0 comments
155.
A Ranty and Dogmatic Troll Masquerading as Coding Guidelines(blog.rocketpoweredjetpants.com)
5 points by KentBeck 13y ago|1 comments
156.
Entropy as Understood by a Programmer. Part 1: Program Structure(facebook.com)
1 points by KentBeck 13y ago|0 comments
157.
Power Laws: So What? Optimization, For One(facebook.com)
3 points by KentBeck 13y ago|0 comments
158.
Short's Not Always Sweet: The Case for Long Test Names(facebook.com)
1 points by KentBeck 13y ago|0 comments
159.
by KentBeck 13y ago
That's an interesting reversal of the logic in the paper. I assumed that the programmers looking for the next cool languages were doing so in pursuit of novelty and not doing it for economic reasons. I wonder how you could empirically suppo
160.
Decompose Run-on Tests(facebook.com)
1 points by KentBeck 14y ago|0 comments
161.
by KentBeck 14y ago
I coach full-time at Facebook, and I coached for various clients part-time for a decade before that. We work a bit on technical stuff like how to design, test, or refactor, but honestly the technical work is mostly to establish trust so we
162.
by KentBeck 14y ago
I think a real artist is required for the authentic effect. I asked for the original and was firmly told that it goes into their archives.
163.
by KentBeck 14y ago
Yep. Fulfillment of a childhood dream, that. I'm just sad Ward didn't get his picture in there too. He doesn't get his (large) share of the credit.
164.
by KentBeck 14y ago
Yes, that was me. I get stuck sometimes. In this case the key insight is that the recursive algorithm is much easier to get to work than the iterative one. There was also the added complexity of two mammoth egos attempting to collaborate.
165.
by KentBeck 14y ago
There are lots of good points made here, but I'll add one: write the environment in itself. The original vision for Smalltalk is that you would be using some application, get curious about how it worked (or want to change it), press ctrl-C
166.
by KentBeck 15y ago
I'm a geezer (50) at Facebook. It's not the hours, as Indiana Jones might have said had he been a programmer, it's the lines. (I don't know what that means--it's just too good a line to pass up.) There are ways I provide leadership and ways
167.
by KentBeck 16y ago
We are in the very early days for finding the profit-maximizing prices for ebooks. If publishers stand in the way of experimentation, someone else will find the sweet spots (I don't expect there to be just one). I read of a mystery author r
168.
by KentBeck 16y ago
I think you have it right. Latency-oriented engineering is a style of development that minimizes the time through the entire loop from idea to learning to feedback from real users to learning based on that feedback to the next idea. What yo
169.
by KentBeck 16y ago
In a startup, you need to engineer to minimize the latency of validating features. Sometimes tests help with that (like when you're dealing with a complicated algorithm), sometimes they don't. I wrote a poker engine recently and I had many
170.
TDD is Kanban for Code(threeriversinstitute.org)
3 points by KentBeck 16y ago|0 comments
171.
Freedom and TDD: How many ways can you implement Stack?(threeriversinstitute.org)
4 points by KentBeck 16y ago|0 comments
172.
Capital-efficient UI design(threeriversinstitute.org)
2 points by KentBeck 16y ago|0 comments
173.
Learn/Measure/Build--we've had the cycle backwards(threeriversinstitute.org)
3 points by KentBeck 17y ago|0 comments
174.
We may be stuck with "NoSQL" for a while(threeriversinstitute.org)
3 points by KentBeck 17y ago|0 comments
175.
Annotations on fields are surprisingly powerful(threeriversinstitute.org)
2 points by KentBeck 17y ago|0 comments
176.
Progress on the Responsive Design Project: long list of terse recommendations(threeriversinstitute.org)
2 points by KentBeck 17y ago|0 comments
177.
The NoSQL explosion comes down to the cost of electicity(threeriversinstitute.org)
23 points by KentBeck 17y ago|11 comments
178.
Having trouble communicating your vision? Write yourself a fan letter(threeriversinstitute.org)
2 points by KentBeck 17y ago|0 comments
179.
by KentBeck 17y ago
You're right that frequent commits greatly simplifies the particular problem of undetected errors in big refactorings. However, people being people, the sunk cost fallacy is still an issue in development.
180.
Wrestling with the sunk cost fallacy: Lessons from Poker 4(threeriversinstitute.org)
2 points by KentBeck 17y ago|2 comments

More ›