Hide

Sign Up

Get our monthly newsletter in your inbox.

Oops! Something went wrong while submitting the form.
see all feed
see all Podcasts
see all Elements
{feed}

How To Avoid Observability MELTdown

October 17, 2022
Written By
October 17, 2022
Written By

o11y - What is it? Why is it important? What are the tools you need? More importantly - how can you adopt an observability mindset? Habu Software Architect Siddharth Sharma reports from his session at super{summit} 2022.

By Siddharth Sharma

This post recaps a session I co-presented, alongside Peter Han and Tyler Bonilla, at the super{summit} conference in August 2022.

It’s amusing to see how our industry flocks around the latest tech buzzword. It’s cool, hip and trending, so why not get on the bandwagon?

The new buzzword kid on the blocks is o11y - a.k.a. Observability!

Actually, observability is a topic very near and dear to my heart over the last 15 years of my software development journey. In this post, I'll discuss what observability is, why it is important, a few challenges, and how to overcome them using Metrics, Events, Logs, and Traces.

Reading along should get you abreast with some of the concepts, patterns, tools and cultural aspects of embracing observability to the best of my knowledge. All references to open source and vendor tools are for illustration purposes only to guide you on the path of embracing observability. Depending on the cost and maintenance overhead tradeoffs you could evaluate the right tool that suits your business needs.

^ Me and CTO of Habu Roopak Gupta avoiding MELTdown at super{summit} 2022

What is Observability?

In control theory, Observability lets us understand a system from the outside, by letting us ask questions, without knowing the inner workings of that system. Observability lets us deal with unknown unknowns.

In software parlance, Observability is the ability to ask new questions of the health of your running services without deploying new code

Why is Observability Important?

In a world of cloud-native loosely coupled services, polyglot persistence, and dynamic infrastructure, traditional metrics-based monitoring approaches are woefully inadequate when it comes to understanding system state, and triaging and diagnosing behavioural and performance issues.

Over the years, Kubernetes has become a developer’s choice for designing and deploying scalable and distributed applications. However, Kubernetes is unaware of the internal state of an application. However, its dynamic nature also gave rise to an increased number of problems for platform engineers who needed to keep track of its performance despite the pace.

Observability vs. Monitoring

These two are often used interchangeably; however, they are different in their application. By monitoring, you can verify if the infrastructure and applications are functioning as expected. On the other hand, observability provides you with comprehensive actionable insights to take steps towards improving performance and making the applications and the entire infrastructure more stable and resilient.

Observability Challenges

Managing networking in a monolithic architecture is a relatively simple task: the path between the client to the server is generally through a finite collection of points.

In a distributed microservice architecture, the network becomes much more critical and complex: the path between client and application got much more winding and harder to reason about due to the

  • The complexity of dynamic multi-cloud environments
  • Dynamic microservices and containers in Kubernetes on Spot Nodes in real-time (Pets vs Cattle)
  • The volume, velocity, and variety of data and alerts
  • Siloed Dev and Ops Teams

It makes root cause analysis and incident resolution potentially a lot harder, yet the same questions still need answering:

  • What is the overall health of my solution?
  • What is the root cause of errors and defects?
  • What are the performance bottlenecks?
  • Which of these problems could impact the user experience?

Observability Pillars

In the past few years, much has been talked about and written about the “three pillars of observability”: metrics, logs, and traces.

Traces

A Trace records the paths taken by requests as they propagate through microservices.
A Span represents a unit of work or operation. It tracks specific operations that a request makes, painting a picture of what happened during the time in which that operation was executed.

Metrics

Metrics are aggregations over a period of time of numeric data about your infrastructure or application

Logs

Log is a record of events that happened over time: a screenshot of something with an associated timestamp.

However, as pointed out by Charity Majors, these 3 pillars are not finite and can be complemented with other pillars viz. Events and Profiles

Events

Though pretty much all signals are events, Events in specific are external to the observed system that cause some changes in that system. The most common examples are: deployments of application code, configuration changes, experiments, auto-scaling events, etc

Events can be analogous to structured logs, however, they differ from logs due to the below traits

  • Zero data loss — As each event can indicate an important signal for incident troubleshooting.
  • High Precision — Accuracy in finding the right event
  • Low Volume —Events are usually produced in much fewer volumes than logs.

Profiling

Profiling is the act of measuring a program’s behavior using data we gather as our code executes (for example, frequency and duration of function calls, CPU time or memory usage, and more).

Profiling is a new addition to the Observability stack and the profiling SIG (special interest group) has just kickstarted. I will be keeping a close eye on it as this evolves and gets supported by various open source and vendor tools.

Best Practices

Below are some of the best practices for implementing Observability in your stack. They can be used to build common shim layers or shared libraries for crosscutting concerns. Developing such generic layers in your programming language of choice will avoid code duplication and help in applying standard conventions across the stack and simplify maintenance and upgrades.

Logs

  • Centralized

Ingest, index and visualize all the logs from various sources in a centralized store using either open source (FluentBit, Loki, ELK..) or vendor tools (DataDog, Honeycomb, NewRelic)

  • Structured (JSON)

Use JSON structured logging as an alternative to traditional logging. Logs written in JSON are easily readable by both humans and machines, and structured JSON logs are easily tabularized to enable filtering and queries.

  • Contextual (Baggage)

Include meaningful information about the event that triggered the log, as well as the additional context that can help understand what happened, find correlations with other events, and diagnose potential issues that require further investigation. A few examples of fields are

— User Request Identifiers (X-Request-Id)

— Unique Identifiers (X-User-Id, X-Tenant-Id)

  • Redact PII or Sensitive Data

Avoid logging sensitive data and personally identifiable information (PII) that may be covered by data privacy and security regulations or standards like the European GDPR, HIPAA, or PCI DSS.

  • Common Interceptors

Use interceptors wherever applicable for logging gRPC/REST requests/responses and prefer using language constructs (MDC in Java or Go Context) to inject context across all logs that are part of the same request/response lifecycle.

  • Levels

Use appropriate log levels (INFO, WARN, ERROR) to avoid logging non-essential information that doesn’t help with diagnostics or root cause analysis resulting in increased time-to-insights, data volumes, and higher costs.

  • Hot vs Cold Persistence

Set different retention policies (S3 IA, Glacier) for different types of logs, depending on the cost and compliance needs.

Metrics

  • Infrastructure Metrics

More metrics are always better if you have the right tools. Hence, gather all the infrastructure golden signals using either open source (Prometheus with Thanos or Cortex) or vendor tools (DataDog, Honeycomb..).

  • Custom Application Metrics

Build language-specific libraries (Micrometer, Prometheus) to instrument application code to emit key business metrics that need alerting (count of custom jobs failed, count of in-flight messages in the queue).

  • Types

Depending on the use case, use the appropriate metric type to capture data points which can then be aggregated to build Sums, Gauges, Histograms

  • Common Interceptors

Like logging, use interceptors wherever applicable to capture gRPC/REST request/response metrics and prefer using language constructs (MDC in Java or Go Context) to inject context across all metrics that are part of the same request/response lifecycle.

  • Methods to collect Golden Signals

RED (Rate, Error, Duration)

Request-scoped — For every request, check utilization, saturation, and errors.

  • Rate: Request Throughput, in requests per second
  • Errors: Request Error Rate, as either a throughput metric or a fraction of overall throughput
  • Duration: Request Latency, Duration, or Response Time

USE (Utilization, Saturation, Error)

Resource-scoped — For every resource, check utilization, saturation, and errors.

  • Utilization: the average time the resource was busy servicing work
  • Saturation: the degree to which the resource has extra work which it can’t service, often queued
  • Errors: the count of error events

Once the golden signals are collected, they can be used collectively for alerting, troubleshooting or tuning and capacity planning.

  • Cardinality

Cardinality is the number of unique combinations of metric names and dimension values. Choose which dimensions you want to attach to your metrics based on what meaningful information you want to extract from your telemetry data. Immutable infrastructures on Kubernetes and Containers lead to cardinality explosion as once a resource is created, it is never updated.

Traces

  • Context

In addition to the default W3C Span Context, code can be instrumented to use custom key-value attributes to annotate a Span to carry information about the operation it is tracking.

For example, if a span tracks an operation that adds an item to a user’s shopping cart in an eCommerce system, you can capture the user’s ID, the ID of the item to add to the cart, and the cart ID.

  • Implicit vs Explicit Propagation

An application can be instrumented for emitting traces either automatically or manually.

  • With automatic instrumentation, the API and SDK take the configuration provided (through code or environment variables) and do most of the work automatically (for example, starting and ending spans).
  • Manual instrumentation, while requiring more work on the user/developer side, enables far more options for customization, from naming various components within OpenTelemetry (for example, spans and the tracer) to adding your own attributes, specific exception handling, and more.

Tools, Tools, Tools….

The monitoring market used to be dominated by proprietary vendors. Each vendor had its own share of pros and cons related to cost and feature support. In response, various free and open-source software projects started or were spun out of tech companies. Early examples include Prometheus for metrics and Zipkin and Jaeger for tracing. In the logging space, the “ELK stack” (Elasticsearch, Logstash, and Kibana) gained market share and became popular.

The market has hit an inflection point, and cloud-native architectures are much larger in scale, more distributed and too interdependent. Developers need the flexibility to choose and control the data they collect and analyze.

OpenTelemetry to the rescue

One key milestone was the merger of the OpenTracing and OpenCensus projects to form OpenTelemetry, a major project within CNCF.

  • OpenTelemetry is a collection of tools, APIs, and SDKs.
  • It provides a vendor-agnostic standard for observability as it aims to standardise the generation of traces.
  • This is good because that means that we are not tied to any tool (or vendor). Not only can we use any programming language we want, but we can also pick and choose the storage backend, thus avoiding a potential buy-in from commercial vendors.
  • It also means that developers can instrument their applications without having to know where the data will be stored.
  • It isn’t a data ingest, storage, backend, or visualization component. Such components will be provided either by other open-source projects or by vendors.

Sample OpenTelemetry Collector Config

The configuration below should help you get started locally by running Docker containers of Prometheus, Jaeger and OpenTelemetry Collector.

You can then instrument your applications either automatically by using the OpenTelemetry Agents or by manually instrumenting them using OpenTelemetry SDK.

In both approaches, metrics and traces from your applications will be sent to the OpenTelemetry collector either using gRPC or HTTP. OpenTelemetry collector can then be configured to build pipelines for filtering or enriching telemetry data before emitting them to the tools like Jaeger, Prometheus, DataDog or NewRelic.

This multiplexing gateway approach avoids first having to select the tool and then instrument your application using the selected tool’s SDKs or Agents. You can seamlessly swap out tools without changing your application code.

Observability is more than Logs, Metrics, Events & Traces

Similar to DevOps, one cannot buy observability off the shelf. Tooling is part of the equation — you’ll need a platform that can ingest, correlate and analyze data — but tools alone aren’t the key to observability. It’s more than deploying certain tools or adopting certain workflows since it has to be embraced in your engineering culture. The culture has to be supported and backed by the engineering leadership and applied to all aspects of the software development lifecycle.

Across the board, super{set} companies are embracing observability by leveraging some of the above patterns and tools as part of their engineering culture and using it to improve the developer and customer experience.

Are you passionate about Platform Engineering, or interested in working in the fast pace of a startup? Check out careers.superset.com for roles across the super{set] portfolio.

Transcript

Hide

Get our monthly newsletter in your inbox.

Oops! Something went wrong while submitting the form.
Written By
Written By
Read next

Introduction

In the first episode of The Closed Session, meet Tom Chavez and Vivek Vaidya, serial entrepreneurs and podcast hosts.

read more

Starting From Scratch

In the second episode of The Closed Session, Tom and Vivek discuss the framework for starting your own company from scratch, and the three dimensions that should be taken into account.

read more

The Business Plan

You’ve decided to launch a business, but before you hurtle blindly into the breach, you need a bulletproof plan and a perfect pitch deck to persuade your co-founders, investors, partners, and employees to follow you into the unknown.

read more

Early-Stage Funding Do’s and Dont’s

In this episode of The Closed Session, Tom and Vivek talk about dilution, methods, mindset, benchmarks and best practices for raising investment capital for a new tech startup.

read more

Early Team Formation

Now that you've written the business plan and raised money, it's time to recruit your early team. In this episode, Tom and Vivek cover the do's and dont's of building a high-output team - who to hire, how to build chemistry and throughput, how to think about talent when your company is a toddler versus when it's an adolescent.

read more

Creating a Winning Culture: Must-Haves, Memes, and Tips

read more

Building a Kickass Product & Technology Engine

read more

Women in Tech

read more

How to Interview for a Startup

read more

Is Tech Stingy? The Case for Doing Well *and* Doing Good

read more

And, we’re live at super{set}!

Welcome to Season 2 of The Closed Session! In this first episode of 2020, Tom and Vivek talk about the five companies super{set} launched in 2019 and the lessons they’re learning as they go.

read more

Equity and Inclusion

Tom and Vivek talk about inclusion and reflect on their personal experiences as brown guys in tech. Inclusion feels like a moral imperative, but does it really make for stronger, better companies? Are there unintended consequences of acting on good intentions to 'fix' an inclusion problem at a company? Why is tech so lacking in diversity, and what can we do to get it right?

read more

super{set}’s Spectrum Detoxifies The Online Space

We are living in a time of extraordinary concern about the negative consequences of online platforms and social media. We worry about the damage interactive technologies cause to society; about the impact to our mental health; and about the way that these platforms and their practices play to our most destructive impulses. Too often, the experiences we have online serve only to polarize, divide, and amplify the worst of human nature.

read more

From Watsonville To The Moon

This post was written by Habu software engineer, Martín Vargas-Vega, as part of our new #PassTheMic series.

read more

Not Just On Veterans Day

This post was written by Ketch Developer Advocate, Ryan Overton, as part of our #PassTheMic series.

read more

Thick Skin, Tech and Black History Month

This post was written by Ketch Data Privacy & Compliance Specialist, Jocelyn Brunson, as part of our #PassTheMic series.

read more

The Balancing Act For Women in Tech

This post was written by Ketch Sales Director, Sheridan Rice, as part of our #PassTheMic series.

read more

The Studio Model

What’s a startup studio? Is it just “venture capital” with another name?

read more

We don’t critique, we found and build.

The super{set} studio model for early-stage venture It is still early days for the startup studio model. We know this because at super{set} we still get questions from experienced operators and investors. One investor that we’ve known for years recently asked us: “you have a fund — aren’t you just a venture capital firm with a different label?”

read more

Silicon Valley’s Greatest Untapped Resource: Moms

This post was written by MarkovML Co-Founder, Lindsey Meyl, as part of our #PassTheMic series.

read more

New Venture Ideation

Where do the ideas come from? How do we build companies from scratch at super{set}?

read more

Good Ideas, Good Luck

Coming up with new company ideas is easy: we take the day off, go to the park, and let the thoughts arrive like butterflies. Maybe we grab a coconut from that guy for a little buzz. While this describes a pleasant day in San Francisco, it couldn’t be further from the truth of what we do at super{set}. If only we could pull great ideas out of thin air. Unfortunately, it just doesn’t work that way.

read more

Data Eats the World

The wheel. Electricity. The automobile. These are technologies that had a disproportionate impact on the merits of their first practical use-case; but beyond that, because they enabled so much in terms of subsequent innovation, economic historians call them “general-purpose technologies” or GPTs...

read more

The Four Types of Startup Opportunities

In our last post, we discussed how data is the new general-purpose technology and that is why at super{set} we form data-driven companies from scratch. But new technologies are a promise, not a sudden phase change.

read more

VCs Write Investment Memos, We Write Solution Memos

When a VC decides to invest in a company, they write up a document called the “Investment Memo” to convince their partners that the decision is sound. This document is a thorough analysis of the startup...

read more

Lessons of Grit from my Immigrant Parents

This post was written by Ketch Solutions Engineer, Sahiti Surapaneni, as part of our #PassTheMic series.

read more

People, First

What does it mean to be a super{set} co-founder and who do we look for? Why is the Head of Product the first co-founder we bring on board?

read more

Navigating Juneteenth

Considered by some to be “America’s Second Independence Day,” Juneteenth has only recently entered the national zeitgeist. Celebrated on the third Saturday in June, it became a federal holiday just last year under President Joe Biden. Many companies are left wondering how to acknowledge the holiday. We sat down with Eskalera’s co-founder Dr. Tolonda Tolbert to get her take.

read more

The super{set} Entrepreneurial Guild

Has someone looking to make a key hire ever told you that they are after “coachability”? Take a look at the Google ngram for “coachability” — off like a rocket ship since the Dot Com bubble, and it’s not even a real word! Coaching is everywhere in Silicon Valley...

read more

Why Head of Product is Our First Co-Founder

At super{set}, we stand side-by-side and pick up the shovel with our co-founders. Our first outside co-founder at a super{set} company is usually a Head of Product. Let’s unpack each portion of that title....

read more

Why I'm Co-founding @ super{set}

Pankaj Rajan, co-founder at MarkovML, describes his Big Tech and startup experience and his journey to starting a company at super{set}.

read more

Too Dumb to Quit

The decision to start a company – or to join an early stage one – is an act of the gut. On good days, I see it as a quasi-spiritual commitment. On bad days, I see it as sheer irrationality. Whichever it is, you’ll be happier if you acknowledge and calmly accept the lunacy of it all...

read more

The Product Heist

Tom and Vivek describe how building the best product is like planning the perfect heist: just like Danny Ocean, spend the time upfront to blueprint and stage, get into the casino with the insertion product, then drill into the safe and make your escape with the perfect product roadmap.

read more

Founder and Father: A Balancing Act

Making It Work With Young Kids & Young Companies

read more

Early Stage Customers

Tom and Vivek discuss what the very first customers of a startup must look and act like, the staging and sequencing of setting up a sales operation with a feedback loop to product, and end with special guest Matt Kilmartin, CEO of Habu and former Chief Revenue Officer (CRO) of Krux, for his advice on effective entrepreneurial selling.

read more

Overheard @ super{summit}

Vivek Vaidya's takeaways from the inaugural super{summit}

read more

How I Learned to Stop Optimizing and Love the Startup Ride

Reflections after a summer as an engineering intern at super{set}

read more

Why I Left Google To Co-found with super{set}

Gal Vered of Checksum explains his rationale for leaving Google to co-found a super{set} company.

read more

The Era of Easy $ Is Over

The era of easy money - or at least, easy returns for VCs - is over. Tom Chavez is calling for VCs to show up in-person at August board meetings, get off the sidelines, and start adding real value and hands-on support for founders.

read more

The super{set} CEO

Tom and Vivek describe what the ideal CEO looks like in the early stage, why great product people aren’t necessarily going to make great CEOs, and what the division of labor looks like between the CEO and the rest of the early team. They then bring on special guest Dane E. Holmes from super{set} company Eskalera to hear about his decision to join a super{set} company and his lessons for early-stage leadership.

read more

How To Avoid Observability MELTdown

o11y - What is it? Why is it important? What are the tools you need? More importantly - how can you adopt an observability mindset? Habu Software Architect Siddharth Sharma reports from his session at super{summit} 2022.

read more

When Inference Meets Engineering

Othmane Rifki, Principal Applied Scientist at super{set} company Spectrum Labs, reports from the session he led at super{summit} 2022: "When Inference Meets Engineering." Using super{set} companies as examples, Othmane reveals the 3 ways that data science can benefit from engineering workflows to deliver business value.

read more

Infrastructure Headaches - Where’s the Tylenol?

Head of Infrastructure at Ketch, and Kapstan Advisor, Anton Winter explains a few of the infrastructure and DevOps headaches he encounters every day.

read more

Calling BULLSHIT

Tom and Vivek jump on the pod for a special bonus episode to call BULLSHIT on VCs, CEOs, the “categorical shit,” and more. So strap yourselves in because the takes are HOT.

read more

Former Salesforce SVP of Marketing Strategy and Innovation Jon Suarez-Davis “JSD” Appointed Chief Commercial Officer at super{set}

The Move Accelerates the Rapidly Growing Startup Studio’s Mission to Lead the Next Generation of AI and Data-Driven Market Innovation and Success

read more

Why I'm Joining super{set} as Chief Commercial Officer

Announcing Jon Suarez-Davis (jsd) as super{set}’s Chief Commercial Officer: jsd tells us in his own words why he's joining super{set}

read more

When and Why to Bring on VCs

Tom and Vivek describe the lessons learned from fundraising at Rapt in 1999 - the height of the first internet bubble - through their experience at Krux - amid the most recent tech bubble. After sharing war stories, they describe how super{set} melds funding with hands-on entrepreneurship to set the soil conditions for long-term success.

read more

Startup Boards 101

Tom and Vivek have come full circle: in this episode they’re talking about closed session board meetings in The {Closed} Session. They discuss their experience in board meetings - even some tense ones - as serial founders and how they approach board meetings today as both co-founders and seed investors of the companies coming out of the super{set} startup studio.

read more

Q&A with Accel Founder Arthur Patterson

Arthur Patterson, founder of venture capital firm Accel, sits down for a fireside chat with super{set} founding partner Tom Chavez as part of our biweekly super{set} Community Call. Arthur and Tom cover venture investing, company-building, and even some personal stories from their history together.

read more

Infrastructure Headaches - Where’s the Tylenol?

Head of Infrastructure at Ketch, and Kapstan Advisor, Anton Winter explains a few of the infrastructure and DevOps headaches he encounters every day.

read more

How I Learned to Stop Optimizing and Love the Startup Ride

Reflections after a summer as an engineering intern at super{set}

read more

Former Salesforce SVP of Marketing Strategy and Innovation Jon Suarez-Davis “JSD” Appointed Chief Commercial Officer at super{set}

The Move Accelerates the Rapidly Growing Startup Studio’s Mission to Lead the Next Generation of AI and Data-Driven Market Innovation and Success

read more

Data Eats the World

The wheel. Electricity. The automobile. These are technologies that had a disproportionate impact on the merits of their first practical use-case; but beyond that, because they enabled so much in terms of subsequent innovation, economic historians call them “general-purpose technologies” or GPTs...

read more

The Era of Easy $ Is Over

The era of easy money - or at least, easy returns for VCs - is over. Tom Chavez is calling for VCs to show up in-person at August board meetings, get off the sidelines, and start adding real value and hands-on support for founders.

read more

Founder and Father: A Balancing Act

Making It Work With Young Kids & Young Companies

read more

Good Ideas, Good Luck

Coming up with new company ideas is easy: we take the day off, go to the park, and let the thoughts arrive like butterflies. Maybe we grab a coconut from that guy for a little buzz. While this describes a pleasant day in San Francisco, it couldn’t be further from the truth of what we do at super{set}. If only we could pull great ideas out of thin air. Unfortunately, it just doesn’t work that way.

read more

Q&A with Accel Founder Arthur Patterson

Arthur Patterson, founder of venture capital firm Accel, sits down for a fireside chat with super{set} founding partner Tom Chavez as part of our biweekly super{set} Community Call. Arthur and Tom cover venture investing, company-building, and even some personal stories from their history together.

read more

The Four Types of Startup Opportunities

In our last post, we discussed how data is the new general-purpose technology and that is why at super{set} we form data-driven companies from scratch. But new technologies are a promise, not a sudden phase change.

read more

Too Dumb to Quit

The decision to start a company – or to join an early stage one – is an act of the gut. On good days, I see it as a quasi-spiritual commitment. On bad days, I see it as sheer irrationality. Whichever it is, you’ll be happier if you acknowledge and calmly accept the lunacy of it all...

read more

Lessons of Grit from my Immigrant Parents

This post was written by Ketch Solutions Engineer, Sahiti Surapaneni, as part of our #PassTheMic series.

read more

Why I'm Co-founding @ super{set}

Pankaj Rajan, co-founder at MarkovML, describes his Big Tech and startup experience and his journey to starting a company at super{set}.

read more

Thick Skin, Tech and Black History Month

This post was written by Ketch Data Privacy & Compliance Specialist, Jocelyn Brunson, as part of our #PassTheMic series.

read more

The super{set} Entrepreneurial Guild

Has someone looking to make a key hire ever told you that they are after “coachability”? Take a look at the Google ngram for “coachability” — off like a rocket ship since the Dot Com bubble, and it’s not even a real word! Coaching is everywhere in Silicon Valley...

read more

When Inference Meets Engineering

Othmane Rifki, Principal Applied Scientist at super{set} company Spectrum Labs, reports from the session he led at super{summit} 2022: "When Inference Meets Engineering." Using super{set} companies as examples, Othmane reveals the 3 ways that data science can benefit from engineering workflows to deliver business value.

read more

From Watsonville To The Moon

This post was written by Habu software engineer, Martín Vargas-Vega, as part of our new #PassTheMic series.

read more

Overheard @ super{summit}

Vivek Vaidya's takeaways from the inaugural super{summit}

read more

Not Just On Veterans Day

This post was written by Ketch Developer Advocate, Ryan Overton, as part of our #PassTheMic series.

read more

Why I'm Joining super{set} as Chief Commercial Officer

Announcing Jon Suarez-Davis (jsd) as super{set}’s Chief Commercial Officer: jsd tells us in his own words why he's joining super{set}

read more

VCs Write Investment Memos, We Write Solution Memos

When a VC decides to invest in a company, they write up a document called the “Investment Memo” to convince their partners that the decision is sound. This document is a thorough analysis of the startup...

read more

Why I Left Google To Co-found with super{set}

Gal Vered of Checksum explains his rationale for leaving Google to co-found a super{set} company.

read more

Navigating Juneteenth

Considered by some to be “America’s Second Independence Day,” Juneteenth has only recently entered the national zeitgeist. Celebrated on the third Saturday in June, it became a federal holiday just last year under President Joe Biden. Many companies are left wondering how to acknowledge the holiday. We sat down with Eskalera’s co-founder Dr. Tolonda Tolbert to get her take.

read more

Why Head of Product is Our First Co-Founder

At super{set}, we stand side-by-side and pick up the shovel with our co-founders. Our first outside co-founder at a super{set} company is usually a Head of Product. Let’s unpack each portion of that title....

read more

We don’t critique, we found and build.

The super{set} studio model for early-stage venture It is still early days for the startup studio model. We know this because at super{set} we still get questions from experienced operators and investors. One investor that we’ve known for years recently asked us: “you have a fund — aren’t you just a venture capital firm with a different label?”

read more

How To Avoid Observability MELTdown

o11y - What is it? Why is it important? What are the tools you need? More importantly - how can you adopt an observability mindset? Habu Software Architect Siddharth Sharma reports from his session at super{summit} 2022.

read more

The Balancing Act For Women in Tech

This post was written by Ketch Sales Director, Sheridan Rice, as part of our #PassTheMic series.

read more

Silicon Valley’s Greatest Untapped Resource: Moms

This post was written by MarkovML Co-Founder, Lindsey Meyl, as part of our #PassTheMic series.

read more

super{set}’s Spectrum Detoxifies The Online Space

We are living in a time of extraordinary concern about the negative consequences of online platforms and social media. We worry about the damage interactive technologies cause to society; about the impact to our mental health; and about the way that these platforms and their practices play to our most destructive impulses. Too often, the experiences we have online serve only to polarize, divide, and amplify the worst of human nature.

read more