Artwork: DevOps Patterns and Antipatterns

-



Great artwork of my DevOpsDays NYC talk last month, explaining DevOps patterns and anti-patterns; and some great feedback (from some well-respected folks):   "The topic from @KishoreJalleda is one of the best I’ve heard brought up in a long time. We need to progress closer to the customer and it’s a topic I’ve been fascinated by for a while now." "Availability is everyone’s job, not just ops!💯 @KishoreJalleda"  "YES! Uptime 9s don’t matter if users are unhappy! Hearing how much uptime is good enough makes me happy"  "Your customers don't care how many times a day you ship code, @KishoreJalleda on focusing on end users, not engineering velocity"  "It’s really important to know true empathy, live like your customers; embrace their experiences"  "Ops Engineering isn’t dead or going anywhere, but it’s time to take responsibility for our destiny."  "DevOps is table stakes. Everyone is moving toward that. The real difference will be in how concerned you are with customer experience." "Anything that pushes developers away from customers is an antipattern. Too much insulation means devs don’t “get” customer pain." "Shift to infrastructure as a strategic differentiator rather than business logic. Are you as an infra eng delivering the right value?" 

 Link to the video:





Comments

  1. My rather long internet look up has at the end of the day been compensated with pleasant insight to talk about with my family and friends.
    Devops Training in Bangalore

    ReplyDelete

  2. Good informations It mayt be Helpfull for me thanks alot for sharing, Know how Development and operations will work in one platform
    Best DevOps Training

    ReplyDelete

  4. Thanks for giving a great information about DevOps Good Explination nice Article
    anyone want to learn advance devops tools or devops online training
    DevOps Online Training DevOps Online Training hyderabadcontact Us: 9704455959

    ReplyDelete

  5. My spouse and I love your blog and find almost all of your post’s to be just what I’m looking for. Can you offer guest writers to write content for you? I wouldn’t mind producing a post or elaborating on some the subjects you write concerning here. Again, awesome weblog!
    Online training in USA

    ReplyDelete

Post a Comment

Popular posts from this blog

Want to Solve Over-Monitoring and Alert Fatigue? Create the Right Incentives!

-
Image
Note— I have been giving talks around the world on this topic (SREcon, Velocity, etc). Figured, I can reach more people through an article. Any/all feedback is highly appreciated! "Research has shown that 72%–99% of ECG monitor alarms are false or clinically insignificant."Quite a staggering number and quite scary given that lives are at stake. If you have ever been to an ICU, you cannot help but notice the telemetry monitors and their constant beeping (they are such a common sight). In fact, I had the first-hand experience with these monitors in the NICU where my twin boys were being cared for after being born prematurely. I still remember vividly how my wife and I used to freak out every time one of these started to go off. Being an ops guy, I could not help but relate this to being paged while on call. Because I was curious, I did a bit of a research on this topic and found that some Ph.D. students had actually published a paper on this topic in 2013. It talks about how wh…
Read more

Difference between Junior and Senior Engineers/Managers/Leaders

-
Qualities of junior engineers/managers/leaders or just about anyone in general:  1. Struggle with brevity; struggle with coming to the point.  2. Use hyperbole to get their point across.  3. Complain about not being invited to that important meeting. 4. Jump to broadcasting a problem w/o thinking through consequences-- just to be the first one.  5. Worry more about looking smart. 6. Only state problems. 7. Love status quo or don't know how to get out.  8. Have a myopic view. Don't understand the root cause; don't ensure production defects remain fixed.   How to become senior?   1. Come straight to the point; provide details later (or, if asked).  2. Avoid hyperbole like "single-handed", "must read" (may be OK in some cultures). 3. Ask that you are invited. Simple. Don't complain; act. Be a leader.   4. Think through the problem; craft your message, and only then deliver.  5. Worry less about looking smart; put more energy into learnin…
Read more