docs: talks.json
This commit is contained in:
parent
eb953d0992
commit
5f82af616a
1 changed files with 16 additions and 4 deletions
|
@ -1423,7 +1423,7 @@
|
||||||
"duration": "PT30M",
|
"duration": "PT30M",
|
||||||
"description": "In a world where data intersects with everything around us, trading card games like Yu-Gi-Oh! are not exempt from crossing paths with advanced data science techniques where the potential for innovation is immense. This talk at PyData focuses on the intersection of web-obtained data and NumPy to create an interesting approach for Yu-Gi-Oh! card recommendations." ,
|
"description": "In a world where data intersects with everything around us, trading card games like Yu-Gi-Oh! are not exempt from crossing paths with advanced data science techniques where the potential for innovation is immense. This talk at PyData focuses on the intersection of web-obtained data and NumPy to create an interesting approach for Yu-Gi-Oh! card recommendations." ,
|
||||||
"liked": true,
|
"liked": true,
|
||||||
"attended": true
|
"attended": false
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"title": "Disenshittify or die! How hackers can seize the means of computation",
|
"title": "Disenshittify or die! How hackers can seize the means of computation",
|
||||||
|
@ -1435,7 +1435,7 @@
|
||||||
"duration": "PT45M",
|
"duration": "PT45M",
|
||||||
"description": "The enshittification of the internet wasn't inevitable. The old, good internet gave way to the enshitternet because we let our bosses enshittify it. We took away the constraints of competition, regulation, interop and tech worker power, and so when our bosses yanked on the big enshittification lever in the c-suite, it started to budge further and further, toward total enshittification. A new, good internet is possible - and necessary - and it needs you." ,
|
"description": "The enshittification of the internet wasn't inevitable. The old, good internet gave way to the enshitternet because we let our bosses enshittify it. We took away the constraints of competition, regulation, interop and tech worker power, and so when our bosses yanked on the big enshittification lever in the c-suite, it started to budge further and further, toward total enshittification. A new, good internet is possible - and necessary - and it needs you." ,
|
||||||
"liked": true,
|
"liked": true,
|
||||||
"attended": true
|
"attended": false
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"title": "Kubernetes Deconstructed: Understanding Kubernetes by Breaking It Down",
|
"title": "Kubernetes Deconstructed: Understanding Kubernetes by Breaking It Down",
|
||||||
|
@ -1447,7 +1447,7 @@
|
||||||
"duration": "PT30M",
|
"duration": "PT30M",
|
||||||
"description": "Understanding Kubernetes as a whole can be daunting. With so many different components working together it can be hard to know how the pieces work together or where new products and features fit in. I will start at the highest level and then peel off the layers one at time to explain how some of the \"magic\" happens. Over the course of the presentation I will break Kubernetes into layers" ,
|
"description": "Understanding Kubernetes as a whole can be daunting. With so many different components working together it can be hard to know how the pieces work together or where new products and features fit in. I will start at the highest level and then peel off the layers one at time to explain how some of the \"magic\" happens. Over the course of the presentation I will break Kubernetes into layers" ,
|
||||||
"liked": true,
|
"liked": true,
|
||||||
"attended": true
|
"attended": false
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"title": "Life of a Packet",
|
"title": "Life of a Packet",
|
||||||
|
@ -1459,7 +1459,19 @@
|
||||||
"duration": "PT35M",
|
"duration": "PT35M",
|
||||||
"description": "Tracing the path of network traffic in the kubernetes system. Clarifying which API objects map to implementation and how Google deploys this in GKE today. Attendees will learn about topics from how networking packets are processed when the cluster is working as designed and what are common problems when the cluster is being creative and surprising." ,
|
"description": "Tracing the path of network traffic in the kubernetes system. Clarifying which API objects map to implementation and how Google deploys this in GKE today. Attendees will learn about topics from how networking packets are processed when the cluster is working as designed and what are common problems when the cluster is being creative and surprising." ,
|
||||||
"liked": true,
|
"liked": true,
|
||||||
"attended": true
|
"attended": false
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"title": "Kubernetes Design Principles: Understand the Why",
|
||||||
|
"speakers": ["Saad Ali"],
|
||||||
|
"date": "2018-12-12T14:35:00",
|
||||||
|
"location": "KubeCon/CloudNativeCon",
|
||||||
|
"tags": ["kubernetes"],
|
||||||
|
"url": "https://www.youtube.com/watch?v=ZuIQurh_kDk",
|
||||||
|
"duration": "PT35M",
|
||||||
|
"description": "Kubernetes is quickly becoming indispensable for managing and deploying workloads on distributed systems across both cloud and on-prem environments. While most people are now familiar with how to use Kubernetes, few are aware of the “why” behind it? Why does the Kubernetes API look the way it does? Why do Kubernetes components only interact with each other through the Kubernetes API? Why is there a PersistentVolumeClaim object when you could easily reference a volume directly from a pod? To answer these questions and help you develop a deeper understanding of Kubernetes, this talk exposes the principles underpinning the design of Kubernetes. " ,
|
||||||
|
"liked": true,
|
||||||
|
"attended": false
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue