Act 1 - Influence

Act 2 - Sales

"If your story describes their problem better than they can describe it themselves, they will automatically assume you have the best solution." - Chris Orlob

Selling is a process of connecting people with a problem with your solution. Your goal is to make them feel confident that you, your company, and your product are the best solution to their problem. Chris Orlob calls out Alcoholics Anonymous as the best of connecting the problem to the solution. It started with a few drinks on the weekend...

Disconnect the "cost" of the solution from the understanding of value. “Does the idea make sense to you? Do you like the idea?”

Use tones to short circuit people's decision-making so they know when to listen or when to agree or disagree. People on the sales journey will have objections. It is your job as a salesperson to handle objections and educate the buyer as an expert on their problem.

Act 3 - Negotiation

Mike Montiero says, "A designer solves problems within a set of constraints".

What is API Design?

The goal of API design is to try and get the defined API interface as right as possible at the beginning because the consequences are severe and lasting when you don't get them right. The reason it is severe is because people can build on top of the API and you cannot change it easily after that.

The goal of API design is to try and get the defined API interface as right as possible at the beginning because the consequences are severe and lasting when you don't get them right. The reason it is severe is because people can build on top of the API and you cannot change it easily after that.

API design is a cultural change in how people apply a process to doing their work. Microservices, domain driven design, cloud native, project to product, and inner sourcing are types of cultural transformations companies go on.

The Goal of Design

You are responsible for the work you put into the world based on Mike Montiero's summary of Victor Papanek's Design for the Real World.

API-First Design versus Code-First?

According to Kevin Sookocheff, this might be a false dichotomy with api development existing on a continuum.

Implementation First suffers from two problems that other practices do not. A lack of forethought in API design and the risk of the API description becoming out of synchronization with the API description.

Good APIs according to JJ Geewax.

API Creation Process according to Kirsten Hunter

As designers of software it is our job to frame for others the decisions they are making.

Publishing an API is a consequential and irreversible decision. By adding friction to this activity we can create compounding leverage by developing a foundation of proven API design patterns to start with instead of starting from scratch each time. We can create better software products by removing the friction that makes doing work hard for no good reason. We can also improve what we make by adding friction that results in better quality experiences.

Poor designs cause real problems in the world like the Amazon s3 cli that cause an outage and the Citibank $500,000,000 UI problem.

Wardley Maps are a technique to visualize business strategy on a dual-axis of value from invisible to visible and another axis to illustrate the evolution. From genesis to commodity.

Cheatsheet and reference material. In progress refer to learn Wardley mapping if digital garden not working.

Learn Wardley Mapping

A digital garden is a website featuring personal notes you share. The purpose is to curate, grow, and prune the thoughts you are developing. The benefit is that you can share your ideas with a wide community without the overhead of a full blog post.

Linkerd certificates expired this week so learning how to deal with rare incidents like architecture is a gift to learn from.

Credibility is core. Never sacrifice it. You might win deals because of your credibility and reputation where others wouldn't.

Presentations - Some in person, Some recorded with presenter on hand in slack or the platform. Some given virtually. Wide spectrum of quality and content.

API Clarity - Tooling to detect shadow and zombie APIs. Depends on Istio.

How NOT to Start with Kubernetes - Christian Heckelmann, Dynatrace

Improving Dev Experience: How We Built a Cloud Native Dev Stack At Scale - Srinidhi S & Venkatesan Vaidyanathan, Razorpay

Jasmine James Keynote

Change is Hard - Securing the Future Today- Andrew Clay Shafer, Red Hat

Developer Experience - Platforms as a Service - Thursday

Vendors that I liked

Kubernetes, Platforms, Networking!

Make content generously.

Act 1 - Local

Act 2 - National

Act 3 - Global

Act 1 - Alignment

Act 2 - Product Thinking

Act 3 - Agile is not enough

Practice and find opportunities to give talks

Use pauses for effect

Connect with your audience

Tell stories

Use your tone

Be you and tell your stories

Prepare for uncertainty and let hiccups wash past you

Use words like imagine and call out names of people in the audience

Every talk cannot be perfect if virtual ask for people to use reactions. If in public practice in the venue.

Take the feedback and apply what makes sense for the next time.