Architecture Code Data Engineering Innovation 
The Netflix TechBlog
JUNE 1, 2021
Data Engineers of Netflix?—?Interview Interview with Samuel Setegne Samuel Setegne This post is part of our “Data Engineers of Netflix” interview series, where our very own data engineers talk about their journeys to Data Engineering @ Netflix. What drew you to Netflix?
Abhishek Tiwari
FEBRUARY 26, 2020
The evolution of your technology architecture should depend on the size, culture, and skill set of your engineering organization. There are no hard-and-fast rules to figure out interdependency between technology architecture and engineering organization but below is what I think can really work well for product startup.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Dynatrace
JULY 6, 2022
IT automation is the practice of using coded instructions to carry out IT tasks without human intervention. At its most basic, automating IT processes works by executing scripts or procedures either on a schedule or in response to particular events, such as checking a file into a code repository. What is IT automation?
The Netflix TechBlog
MARCH 5, 2019
Netflix’s engineering culture is predicated on Freedom & Responsibility, the idea that everyone (and every team) at Netflix is entrusted with a core responsibility and they are free to operate with freedom to satisfy their mission. All these micro-services are currently operated in AWS cloud infrastructure.
Adrian Cockcroft
FEBRUARY 13, 2023
SUS209 — there was no talk with this code. STP213 Scaling global carbon footprint management — Blake Blackwell Persefoni Manager Data Engineering and Michael Floyd AWS Head of Sustainability Solutions. SUS302 Optimizing architectures for sustainability — Katja Philipp AWS SA and Szymon Kochanski AWS SA.
O'Reilly
FEBRUARY 2, 2020
First, the behavior of an AI application depends on a model , which is built from source code and training data. A model isn’t source code, and it isn’t data; it’s an artifact built from the two. This means that, to have a history of how an application was developed, you have to look at more than the source code.
Abhishek Tiwari
JULY 20, 2019
The engineering organisation described may not work for you because of a team of 8-10 people is still a very big overhead. In this model, software architecture and code ownership is a reflection of the organisational model. I also have a strong feeling that long-lived teams are not good for innovation and disruption.
Expert insights. Personalized for you.
130 
Let's personalize your content