Posts

Artwork: DevOps Patterns and Antipatterns

Image
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…

My (personal) definition of "DevOps" quoted in an article on Forbes.

Image
Happy to see my (personal) definition of "DevOps" quoted in a recent article on Forbes. The slide is from my talk at the DevOps Enterprise Summit in SF (2017).

https://lnkd.in/gyfnhp5
"Kishore Jalleda, Sr. Director of Production Engineering at Yahoo, describes DevOps best in this slide" 


Customers don't care about five-nines reliability; they care about five-nines customer service.

Abridged version of my longer article "DevOps is more about customer feedback and quick learning than Culture/Process/Tools":
Your customers don't really care if you are a DevOps shop/factory; they care about how your products add value to their lives. Common misconceptions about DevOps:  #1: We are a team of developers doing operations - we are DevOps! 
#2:We are a Dev team continually deploying to production - we are DevOps! #3: We are a team of Ops wrtiing code - we are DevOps!

Customer-focused software engineers - the missing piece of the DevOps puzzle:  
#1: They are intrapranuers
#2: They don't indulge in mindless tasks
#3: They strive to get customer feedback quickly
DevOps Patterns - from a customer's perspective:  #1: Uptime is overrated. Customers don't care about five-nines reliability; they care about five-nines customer service.
#2: Velocity is overrated; customer feedback is underrated. Your customers don't care about how many times a day you…

Want to be successful in life? Develop an Asynchronous Mindset.

Want to be successful in life? Develop --what I call is-- an Asynchronous Mindset.   BTW, success isn't just more money; success is having those moments when you feel good about your actions & the impact they have on the society, family, friends & co-workers. So, what are the traits of people w/this mindset? #1: Giving back. Most people are takers; very few givers. It's never too late to give back. Give more; take way less. #2: Taking risks; most love status-quo. Most aren't even aware that there is life beyond day-to-day (or they don't know how to step out) #3: You can't win every battle. Sometimes, shut up & just listen. #4: Let go of things that don't matter. Most have a hard time letting go of what's in front of them. #5: Everyone fails; it's what makes us human. Not everyone uses it as a learning opportunity. Be a dreamer; be an optimist. Develop resilience. #6: Inner peace. It helps you stay focused on the problem as opposed to…

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…

Leading a transformational change at scale? Follow these ten rules!

Want to lead a successful transformational change at scale? Follow these simple rules (abridged version of one of my recent talks) Rule #1:
Find your allies. They don’t come to you, you must find them and explain your vision and get feedback & alignment.
Rule #2:
Have a strong vision; rally people around your vision. Communicate your vision widely.  Rule #3:
Make sure yourboss is aligned with you. Emphasize what a dramatic change you are making. Get alignment. Rule #4:
Not just your boss, but get alignment with your boss’s bosses and all the way up Rule #5:
Leverage outages. Ask thought-provoking questions; stir emotions; provoke action. Don't be a jerk though.  Rule #6: 
If you are serious about transformational changes at scale, half-assed approaches won’t work. You have to be willing to take a stand Rule #7:
Don't miss the boat. Most go/no-go decisions usually come down to a meeting (or two). Make sure you are prepared. Drive alignment prior to the meeting; not duri…

Leadership: first 30-90 days of inheriting a mess

You are a leader; you got that dream job or given more responsibilities. The problem is you are inheriting (a bit of) a mess; you are inheriting (a bit of) a dysfunctional org. Follow these rules to have a greater chance of success in your new role: Rule #1: 
Don't make any major decisions for a while (1-3 months). You will be so tempted to act; don't. Have your boss remind you this constantly. Rule #2:
Don't talk about your successes, strategies & wins from previous roles/jobs. Just don't. You are going to come across very poorly. You are already the boss; you already have the job. There is nothing left to prove. Rule #3:
Build credibility by being on the front lines. Be on call for a product; use the product; listen to customer feedback; sit in on CS calls. Rule #4:
Listen more; question less. Never ask why the f*** is something done a certain way (yes, I know, things will drive you nuts; be patient). Rule #5:
Be empathetic to the needs of the team. Don't…