---
title: "Discussion on \"No, Big O notation is not equivalent  to saying \"worst case scenario\"\" | Hashnode"
description: "Discussion on \"No, Big O notation is not equivalent  to saying \"worst case scenario\"\". Each type of analysis (worst case, or best case) can have its own upper bound (Big O), lower bound (Big Omega), and tight bound (Big Theta)."
url: "https://hashnode.com/posts/no-big-o-notation-is-not-equivalent-to-saying-worst-case-scenario/632b2192c63fa0e8e95a7a88"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [No, Big O notation is not equivalent to saying "worst case scenario"](https://hazemkh.hashnode.dev/no-big-o-notation-is-not-equivalent-to-saying-worst-case-scenario?utm_source=hashnode&utm_medium=feed)

Each type of analysis (worst case, or best case) can have its own upper bound (Big O), lower bound (Big Omega), and tight bound (Big Theta).

Sep 21, 2022 · 3 min read · hazemkh.hashnode.dev  
Updated Apr 10  
Read the article

-   [#algorithms](https://hashnode.com/tag/algorithms)
-   [#big-o](https://hashnode.com/tag/big-o)

## Written by

[Hazem Khairy](https://hashnode.com/@hazem0h)

@hazem0h

  
[View profile](https://hashnode.com/@hazem0h)

DevOps Engineer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
