Twitter | Search | |
Clayton Coleman
Developer - Kubernetes and OpenShift
95
Tweets
6
Following
854
Followers
Tweets
Clayton Coleman Apr 10
Kubernetes right now! Ask everything!
Reply Retweet Like
Clayton Coleman Mar 28
Replying to @JamesMunnelly @thockin
Or we switch to octal!
Reply Retweet Like
Clayton Coleman Mar 28
Replying to @thockin
Although our numbering scheme is clearly undesigned and happenstance. Should have been Kubernetes 1.A.0
Reply Retweet Like
Clayton Coleman Mar 28
Replying to @solomonstre
Without you none of this would have been possible - thank you for inspiring us to look at things in a different way!
Reply Retweet Like
Clayton Coleman Jan 30
OpenShift + Tectonic together will be better than either could be individually. CoreOS folks know what’s important in operating real software.
Reply Retweet Like
Clayton Coleman Dec 10
Replying to @thockin
Swear *and* sweat
Reply Retweet Like
Clayton Coleman Dec 10
Replying to @thockin
Everyone who has altered those has done: 1. Cargo cult Tim’s original 2. Sweat repeatedly at make, bash, tim, and make 3. Learn something about make 4. Considered a different career 5. Achieved partial enlightenment 6. Resolved to never need to add to it I think 6 is win
Reply Retweet Like
Clayton Coleman Dec 10
Replying to @jessfraz
You win the meta this round
Reply Retweet Like
Clayton Coleman Dec 10
Replying to @jessfraz
Actually, I was deliberately trying not to laugh, because I *did* see you. I had to keep looking off to the side.
Reply Retweet Like
Clayton Coleman Dec 10
Replying to @thockin
I had to have rigid self control not to list cool projects for 20 minutes with 9pt font lists on the slides. That was my “don’t scare people, don’t scare people” reminder...
Reply Retweet Like
Clayton Coleman Dec 10
Replying to @brendandburns @thockin
It was phenomenal - better ever year, and it’s already great!
Reply Retweet Like
Clayton Coleman Dec 10
Pretty sure we used kube-c-t-l when explaining it to new users/devs in the early days. Shame we didn’t do many recordings back then.
Reply Retweet Like
Clayton Coleman Dec 8
The glasses, they do nothing!
Reply Retweet Like
Clayton Coleman Dec 4
Replying to @thockin
Gonna steal your goatee and pretend to be you.
Reply Retweet Like
Clayton Coleman Nov 23
The only place I’ve missed generics (writing that stuff) is cache.DeletionFinalStateUnknown which breaks everyone at least once. In general we generate code for performance, not for type safety. I’d kill for a better serialization framework in go though.
Reply Retweet Like
Clayton Coleman Nov 15
Replying to @mfojtik @jpetazzo and 4 others
Leading edge kube is pretty good, but on a 3 month cadence there's a lot of room for additional soaking to catch everything. That's mostly what we do and why we don't ship right away.
Reply Retweet Like
Clayton Coleman Nov 15
Replying to @mfojtik @jpetazzo and 4 others
Yeah - I'd say it takes us about 2-3 weeks to review and audit everything that changed in the kube release (since we depend on shared code), and then 3-8 weeks to soak bugs. I think in 1.6 we identified between 50-150 bugs that would impact one or more user before we shipped.
Reply Retweet Like
Clayton Coleman Nov 14
Replying to @thockin @jbeda and 5 others
Pretty sure that’s called “engineering”
Reply Retweet Like
Clayton Coleman Nov 14
Replying to @thockin @jbeda and 5 others
I still think back fondly to that first f2f in Seattle - being in the Distillery with you and Joe drinking whiskey and explaining terrible Borg decisions. Good times.
Reply Retweet Like
Clayton Coleman Nov 14
Given you a mission and a purpose
Reply Retweet Like