Tim Bozarth

Traveling the path of Developer Infrastructure @Microsoft and negotiating with a youngling. #exGoogle #exNetflix #exBox

[Tim Bozarth @timbozarth]

@SJFD Thank you @SJFD all for your incredible bravery. You make us safe and proud as a community.

[Tim Bozarth @timbozarth]

@UniversalQandA Do events that happen right before the formation of the singularity (where the event horizon lines and singularity line emerge from a single point) have the ability to impact events inside the singularity as well as events outside of it?

[Tim Bozarth @timbozarth]

Interested in doing amazing work around Networking in the container orchestration space? #Titus is doing some impressive stuff to push the boundaries. #NetflixOSS

[Tim Bozarth @timbozarth]

After 3 years of investment by an amazing team of engineers, we're finally able to share our container management platform (Titus) with the world. Congratulations to everyone involved, and I hope many others can find value from this OSS contribution! https://t.co/mn2mc0dWS8

[Tim Bozarth @timbozarth]

@aspyker @danveloper @icco Great question! I hope to have a fairly detailed writeup about our transition to gRPC, our enhancements (that I hope we can OSS at the same time), and details on how much improved this new approach has been for us in the past couple years.

[Tim Bozarth @timbozarth]

Take a look at our most recent OSS library (creatively named "concurrency-limits") that uses adaptive concurrency limits to prevent cascading failures and application death-spirals. https://t.co/iKphdpbgPE

[supermassive backlog @FakeRyanGosling]

I will not look at average latencies
I will not look at average latencies
I will not look at average latencies
I will not look at average latencies
I will not look at average latencies
I will not look at average latencies
I will not look at average latencies

[ACM Queue @ACMQueue]

Titus: Introducing Containers to the Netflix Cloud:
Approaching #container adoption in an already cloud-native infrastructure
https://t.co/MxULmkemGG

@anwleung
@aspyker
@timbozarth

[InfoQ @InfoQ]

It is possible to go from "zero" to "production ready" in minutes. Learn how @Netflix is doing this w/ @timbozarth. https://t.co/Exmnx25GmC

[Tim Bozarth @timbozarth]

Wanna learn how we're doing container orchestration at Netflix? Check out the latest issue of @ACMQueue for the story of Titus!

[QCon Software Development Conferences @QCon]

“Zero to Production-Ready in Minutes” w/ @timbozarth live on @infoq
https://t.co/fg5zccAQbp

[ɹǝʞʎds ʍǝɹpuɐ @aspyker]

Great job #Netflix @bdpsecurity @nora_js and @timbozarth speakers - top three speakers #qconnyc day 2. Security, Chaos, and Cloud Runtimes.

[QCon New York Software Development Conference @qconnewyork]

Director of Engineering @timbozarth on how Netflix is enables engineers to go from "zero" to "production ready" in minutes #qconnyc

[ɹǝʞʎds ʍǝɹpuɐ @aspyker]

#Netflix @timbozarth talking challenges we're focusing on in cloud runtime platform. Focus returning to engineering productivity #qconnyc

[Tim Bozarth @timbozarth]

@shanehastie Thank you for the great tweets and coverage of the talk! Hope you found it relevant to your own situation!

[QCon New York Software Development Conference @qconnewyork]

The " Developer Experience: Level up Your Engineering Effectiveness" track at #qconnyc hosted by @sangeetan is ready https://t.co/mVE04rFsOU

[Tim Bozarth @timbozarth]

100m oysters at #netflix100mparty!!!

[Tim Bozarth @timbozarth]

It feels like a SV-coming-of-age event for someone to register a domain dedicated to OSSing your team's product https://t.co/x5XyAsJfAV

[Tim Bozarth @timbozarth]

A million+ containers scheduled last week. Containers are opening doors for our developers at scale. https://t.co/3uvBSRjK43

[Tim Bozarth @timbozarth]

@phinandphebes I'm guessing that freezer burn and ice crystals weren't the flavor mix-in you were intending? Bummer.