The Journey of devops and continuous delivery in a Large Financial InstitutionKris Buytaert
The Journey of devops and continuous deliverey in a Large Financial Institution,
as presented by @markheistek and myselve at Velocity Conf 2013, Longon
The Journey of devops and continuous delivery in a Large Financial InstitutionKris Buytaert
The Journey of devops and continuous deliverey in a Large Financial Institution,
as presented by @markheistek and myselve at Velocity Conf 2013, Longon
Minimum Viable Architecture -- Good Enough is Good Enough in a StartupRandy Shoup
I have spent the last decade building large-scale systems at eBay and Google -- and talking publicly about it -- and this presentation is about why a startup should completely ignore what I said! In an early-stage startup, it is not only not worth architecting for a future of massive scale; it is actively counterproductive. This presentation from the SF Startup CTO Summit outlines the common architectural evolution of a startup through the search, execution, and scaling phases, and discusses the appropriate technologies and disciplines at each phase. It ends with some real-world examples from eBay, Twitter, and Amazon to illustrate the point.
Introductory slides to a collaborative usability observation & issue prioritisation session. A training and service promotion workshop for the University of Edinburgh Website Programme.
WTF: Where To Focus when you take over a Drupal projectSymetris
Jumping into pre-built Drupal projects sometimes requires a leap of faith as much for clients as for developers. The client is usually coming out of a bad previous business relationship and the code is not always structured according to your standards.
During this talk, Symetris will share its experience and provide tips on how to navigate these often uncharted waters. Our goal is to help you convert an uncertain client into a long term partner and have a checklist of what to look out for as developers.
Velocity Conference NYC 2014 - Real World DevOpsRodrigo Campos
In a world where agility has become a requirement, business and engineering demands have decreed the death of the “Department of No”. This talk will cover the journey of an IT Operations department from a single DevOps team to a business-wide cultural shift that has affected the way people interact and work with each other.
In order to make sure that our DevOps initiative would be successful, we needed to make changes to the corporate organization, rearrange teams and roles in several areas, and make sure that everyone fully understand where we were being headed to.
All these steps will be covered in this talk that will demonstrate some common pitfalls and misconceptions that jeopardize the DevOps adoption, particularly in large enterprises with several compliancy requirements and some outdated bureaucracy.
The Importance of Culture: Building and Sustaining Effective Engineering Org...Randy Shoup
Randy is a 25-year veteran of Silicon Valley, having led engineering organizations at eBay, Google, Oracle, and a number of other companies. Through the lens of his personal experience from hands-on engineer to architect to CTO, at organizations ranging from tiny startups to global giants, Randy will discuss several important aspects of engineering cultures, which both support and hinder the ability to innovate: hiring and retention, ownership and collaboration, quality and discipline, and learning and experimentation.
Randy will suggest some learnings about what has worked well -- and what has not -- in creating and sustaining an effective engineering culture. He will further offer some concrete suggestions on how other organizations -- both large and small -- can evolve their cultures as well.
The Fundamentals of Continuous Software DesignJeremy Miller
Here's my talk from CouchCon on the fundamental ideas and thinking behind doing software design in an Agile Software project
See the whole talk at https://www.youtube.com/watch?v=v9icxKMJ9PA
How contributing to Open-source made me a better DevOpsAhmed AbouZaid
How participating in Open-source made me a better DevOps
And that actually started not just as a professional system engineer, but much earlier as a normal end-user also as a power user.
DevOps is far more about culture and organization than it is about technology and tooling. This talk will discuss the speaker's experiences leading high-performing engineering teams at Google, eBay, and Stitch Fix, and will offer suggestions for other organizations to level up their DevOps game.
https://www.meetup.com/SV-ELC/events/240087808/
Modern software-service models take advantage of the great benefits in having the same team both build the software as well as operate it in production -- "You Build It; You Run It" is the Amazon mantra. What does this mean in practice?
Organizationally, it means small teams with well-defined areas of responsibility, directly aligned with the business. The teams are cross-functional, meaning that each team has all the skill sets it requires to do its job, while at the same time relying on other teams for supporting services, tools, and libraries.
Process-wise, it means doubling down on practices like test-driven development and continuous delivery. Using continuous delivery practices, high-performing teams can and do release their applications and services multiple times a day. This enables them to iterate rapidly, experiment courageously, and fail more quickly.
Culturally, it means end-to-end ownership. Each team owns its software end-to-end, from design to development to deployment to retirement. The same engineers who are responsible for the features are responsible for quality, performance, operations, and maintenance. This ownership puts incentives in the right place to encourage building maintainable, observable, and operable systems from the start.
All these techniques and approaches are available to everyone, and practical examples in this talk will help other organizations on their journey.
DOES15 - Randy Shoup - Ten (Hard-Won) Lessons of the DevOps TransitionGene Kim
Randy Shoup, Consulting CTO
DevOps is no longer just for Internet unicorns any more. Today many large enterprises are transitioning from the slow and siloed traditional IT approach to modern DevOps practices, and getting substantial improvements in agility, velocity, scalability, and efficiency. But this transition is not without its challenges and pitfalls, and those of us who have led this journey have the scar tissue to prove it.
A successful transition to DevOps practices ultimately involves changes to organization, to culture, and to architecture. Organizationally, we want to create multi-skilled teams with end-to-end ownership and shared on-call responsibilities. Culturally, we want to prioritize solving problems and improving the product over closing tickets. Architecturally, we want to move to an infrastructure with independently testable and deployable components.
The ten practical lessons outlined in this session synthesize the speaker’s experiences leading teams at eBay, Google, and KIXEYE, as well as from his current consulting practice.
Don't forget the people - DevOps Manchester 10th Oct 2015James Heggs
DevOps Manchester 10th Oct 2015
Stories from previous experiences of attempting to move towards a DevOps culture based around the people aspects of decision.
Minimum Viable Architecture -- Good Enough is Good Enough in a StartupRandy Shoup
I have spent the last decade building large-scale systems at eBay and Google -- and talking publicly about it -- and this presentation is about why a startup should completely ignore what I said! In an early-stage startup, it is not only not worth architecting for a future of massive scale; it is actively counterproductive. This presentation from the SF Startup CTO Summit outlines the common architectural evolution of a startup through the search, execution, and scaling phases, and discusses the appropriate technologies and disciplines at each phase. It ends with some real-world examples from eBay, Twitter, and Amazon to illustrate the point.
Introductory slides to a collaborative usability observation & issue prioritisation session. A training and service promotion workshop for the University of Edinburgh Website Programme.
WTF: Where To Focus when you take over a Drupal projectSymetris
Jumping into pre-built Drupal projects sometimes requires a leap of faith as much for clients as for developers. The client is usually coming out of a bad previous business relationship and the code is not always structured according to your standards.
During this talk, Symetris will share its experience and provide tips on how to navigate these often uncharted waters. Our goal is to help you convert an uncertain client into a long term partner and have a checklist of what to look out for as developers.
Velocity Conference NYC 2014 - Real World DevOpsRodrigo Campos
In a world where agility has become a requirement, business and engineering demands have decreed the death of the “Department of No”. This talk will cover the journey of an IT Operations department from a single DevOps team to a business-wide cultural shift that has affected the way people interact and work with each other.
In order to make sure that our DevOps initiative would be successful, we needed to make changes to the corporate organization, rearrange teams and roles in several areas, and make sure that everyone fully understand where we were being headed to.
All these steps will be covered in this talk that will demonstrate some common pitfalls and misconceptions that jeopardize the DevOps adoption, particularly in large enterprises with several compliancy requirements and some outdated bureaucracy.
The Importance of Culture: Building and Sustaining Effective Engineering Org...Randy Shoup
Randy is a 25-year veteran of Silicon Valley, having led engineering organizations at eBay, Google, Oracle, and a number of other companies. Through the lens of his personal experience from hands-on engineer to architect to CTO, at organizations ranging from tiny startups to global giants, Randy will discuss several important aspects of engineering cultures, which both support and hinder the ability to innovate: hiring and retention, ownership and collaboration, quality and discipline, and learning and experimentation.
Randy will suggest some learnings about what has worked well -- and what has not -- in creating and sustaining an effective engineering culture. He will further offer some concrete suggestions on how other organizations -- both large and small -- can evolve their cultures as well.
The Fundamentals of Continuous Software DesignJeremy Miller
Here's my talk from CouchCon on the fundamental ideas and thinking behind doing software design in an Agile Software project
See the whole talk at https://www.youtube.com/watch?v=v9icxKMJ9PA
How contributing to Open-source made me a better DevOpsAhmed AbouZaid
How participating in Open-source made me a better DevOps
And that actually started not just as a professional system engineer, but much earlier as a normal end-user also as a power user.
DevOps is far more about culture and organization than it is about technology and tooling. This talk will discuss the speaker's experiences leading high-performing engineering teams at Google, eBay, and Stitch Fix, and will offer suggestions for other organizations to level up their DevOps game.
https://www.meetup.com/SV-ELC/events/240087808/
Modern software-service models take advantage of the great benefits in having the same team both build the software as well as operate it in production -- "You Build It; You Run It" is the Amazon mantra. What does this mean in practice?
Organizationally, it means small teams with well-defined areas of responsibility, directly aligned with the business. The teams are cross-functional, meaning that each team has all the skill sets it requires to do its job, while at the same time relying on other teams for supporting services, tools, and libraries.
Process-wise, it means doubling down on practices like test-driven development and continuous delivery. Using continuous delivery practices, high-performing teams can and do release their applications and services multiple times a day. This enables them to iterate rapidly, experiment courageously, and fail more quickly.
Culturally, it means end-to-end ownership. Each team owns its software end-to-end, from design to development to deployment to retirement. The same engineers who are responsible for the features are responsible for quality, performance, operations, and maintenance. This ownership puts incentives in the right place to encourage building maintainable, observable, and operable systems from the start.
All these techniques and approaches are available to everyone, and practical examples in this talk will help other organizations on their journey.
DOES15 - Randy Shoup - Ten (Hard-Won) Lessons of the DevOps TransitionGene Kim
Randy Shoup, Consulting CTO
DevOps is no longer just for Internet unicorns any more. Today many large enterprises are transitioning from the slow and siloed traditional IT approach to modern DevOps practices, and getting substantial improvements in agility, velocity, scalability, and efficiency. But this transition is not without its challenges and pitfalls, and those of us who have led this journey have the scar tissue to prove it.
A successful transition to DevOps practices ultimately involves changes to organization, to culture, and to architecture. Organizationally, we want to create multi-skilled teams with end-to-end ownership and shared on-call responsibilities. Culturally, we want to prioritize solving problems and improving the product over closing tickets. Architecturally, we want to move to an infrastructure with independently testable and deployable components.
The ten practical lessons outlined in this session synthesize the speaker’s experiences leading teams at eBay, Google, and KIXEYE, as well as from his current consulting practice.
Don't forget the people - DevOps Manchester 10th Oct 2015James Heggs
DevOps Manchester 10th Oct 2015
Stories from previous experiences of attempting to move towards a DevOps culture based around the people aspects of decision.
A short introduction to the more advanced python and programming in general. Intended for users that has already learned the basic coding skills but want to have a rapid tour of more in-depth capacities offered by Python and some general programming background.
Execrices are available at: https://github.com/chiffa/Intermediate_Python_programming
Graph databases in computational bioloby: case of neo4j and TitanDBAndrei KUCHARAVY
Code used for demos is available from: https://github.com/chiffa/neo4jDemo repositry
Code used for IO over the reactome is available from: https://github.com/chiffa/PolyPharma
A talk about how I combine puppet puppetdb and ansible all working together to deploy software from a git repo through jenkins on the development and production environments within minutes.
Dakwah kreatif , 24 Februari 2013 kemarin bertempat di garasi identitas muslim jalan perumnas no 20 . Sekitar 15 brand clothing muslim jogja bergabung menjadi satu dan sepakat membentuk paguyuban pengusaha distro muslim jogja.
Tujuan nya paguyuban ini di buat adalah sebagai wadah silaturahim dan jaringan antar pengusaha distri & clothing muslim jogja dan juga bisa menjalin hubungan dengan distro – distro yang ada daerah lain di luar jogja .
Semangat berdakwah lewat media kaos ini yang menjadikan kita punya visi yang sama yaitu berjuang demi tegaknya Islam kembali.
Harapan dari paguyuban ini adalah kita bebarengan berjamaah untuk membangun jogja sebagai pusat distro muslim jogja , sehingga orang indonesia kalo ingat distro muslim ya ingatnya di jogja .
Kaos adalah termasuk media yang cukup efektif untuk membuat life style dan juga memberikan pesan . Fashion juga termasuk dalam salah satu sub sektor Industri kreatif karena terus berkembang dan selalu ada saja inovatif ide yang keluar.
Akhirnya setelah saling berkenalan dan bercerita tentang konsep clothing muslim masing- masing terpilihlah ketua jaringan yaitu Abidin dari id garasi muslim dan nama paguyuban ID MUSLIM (INDONESIA DISTRO MUSLIM).
Semua anggota ID Muslim yakin dan percaya jogja sebagai pusat distro muslim Indonesia bukanlah mimpi karena kita semua punya niatan iklas membantu Agama Allah jadi kita pasti ditolong Allah bila kita berjamaah .
Deploying your Drupal site, Upgrading your Drupal Site, Scaling, Clustering and Monitoring it ... all topics Developers are often not involved with ...
Devops For Drupal explains the Devops problem, to a Drupal audience .
This was a presentation given at San Diego Python's Django Day:
http://www.meetup.com/pythonsd/events/95751792/
https://github.com/pythonsd/learning-django
There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster.
Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.
Yetizen (https://www.linkedin.com/company/yetizen/about/) was a gaming incubator that existed in San Francisco, roughly between 2011 and 2015. I thought it was an interesting experiment, and was happy to give a series of talks there, and advise the portfolio companies.
This talk, from 2013, is about what's involved in being a platform vendor-- a third party whose service is relied up by applications. From the fact that your customers (application companies) don't really trust you to the fact that they make unreasonable demands to the fact that platforms and services are architected differently from applications; it's all in here.
SaltConf14 - Justin Carmony, Deseret Digital Media - Teaching Devs About DevOpsSaltStack
Let's set aside the buzzwords for a moment and have an honest discussion about DevOps. There is the idea of putting more Dev into Ops, but just as crucial (if not more crucial) is getting your Devs to think more like Ops. Most developers have little to no experience dealing with production environments, and helping them add value to DevOps efforts can be difficult. This talk will cover practical ways of mentoring Devs into more DevOps skills and responsibilities. Ultimately, the goal is to help your Devs gain the skills leading to better production health, application performance and uptime. Of course, we'll also consider how SaltStack can help.
We’re all doing Agile nowadays, aren’t we? We’ll all delivering software in an Agile way. But what does that mean? Does it mean sprints and stand-ups? Kanban even? But what about Extreme Programming? If as a development team we’re not using pair programming, test driven development, continuous integration, and other XP practices, then we’re not really doing Agile software development and we may be on a march to frustration, or even failure.
I’m going to look at why the current trend of companies and projects adopting Scrum, calling themselves Agile, but not transitioning their development to XP, is a recipe for disaster. I’d like to cover the main practices of XP as well as other good practices that can really help a team deliver quality software, whether they’re doing two-week sprints, Kanban, or even Waterfall.
https://www.youtube.com/watch?v=aZgnY9fAHOA
DevOpsGuys - Getting Started with DevOps - Github/Azure WebinarDevOpsGroup
DevOpsGuys - Getting Started with DevOps - Github/Azure Webinar in April 2017 that talks about the 5 key ingredients you need to kick start your DevOps Transformation
Similar to Devops in with the old, in with the new (20)
Welcome to the Program Your Destiny course. In this course, we will be learning the technology of personal transformation, neuroassociative conditioning (NAC) as pioneered by Tony Robbins. NAC is used to deprogram negative neuroassociations that are causing approach avoidance and instead reprogram yourself with positive neuroassociations that lead to being approach automatic. In doing so, you change your destiny, moving towards unlocking the hypersocial self within, the true self free from fear and operating from a place of personal power and love.
4. One day before release
●
“Put this code live, here's a tarball, kthxbye!”
“What dependencies has it?
Where do I put it?
What database?
Does it need to be highly available?
What traffic are you expecting?”
●
“Not much, just install it..”
“Okay :-/”
5. 10 days into operation
●
“The servers are slow!”
Why is our load so high? Why is all the memory
used?
Where does this thing write its logs?
Why is that web page generating 100 queries?
Debugging is still enabled?
Who wrote this $#!* ?!
9. It is
•
A human problem
•
A corporate culture problem
“You can’t directly change culture. But you can change
behavior, and behavior becomes culture” – Lloyd Taylor
VP Infrastructure, Ngmoco
12. Talk about goals
Stable Platform
●
New releases
No Downtime
●
New Features
Scalable Platform
●
New platforms
Non Functional Req
●
New architectures
●
Functional Req
15. Listen, analyse
●
What are devs nagging about
•
•
●
Slow builds ?
No enviroments ?
What are ops nagging about
•
•
●
Deployement proces ?
No logs ?
What is mgmt nagging about
•
Quality / Feedback ?
16. Crossfunctional Team
●
Build a project team with skills from all over
•
Development
•
Continuous Integration
•
Testing
•
Infrastructure (HA/ Scale/ Performance)
•
Deployment
•
Measurement
●
Seat them together !
●
Goal = Help improve the business
18. Improve Communication
●
Chatrooms (being online = being available)
•
Topic
•
Virtual watercooler
•
ChatOps
●
Virtual and physical standups (hangout / jabber)
●
Transfer knowledge
●
Not only inside the team
