---
title: "💭 Post | LinkedIn"
description: "!https://www.linkedin.com/posts/anton-martyniuk_source=share&utm_desktop&rcm=ACoAACM7I2cBosNBb12iAVlY0IZbLYYHgFOyIg4"
date: 2025-11-11
published: true
tags:
  - catalytic
  - thought
template: link
---


<div class="embed-card embed-card-external">
  <a href="https://www.linkedin.com/posts/anton-martyniuk_mark-zuckerberg-scaled-facebook-in-2005-activity-7393550498584371201-iqDA/?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAACM7I2cBosNBb12iAVlY0IZbLYYHgFOyIg4" class="embed-card-link" target="_blank" rel="noopener noreferrer">
    <div class="embed-card-image">
      <img src="https://media.licdn.com/dms/image/v2/D4E22AQFEJ1tbZxs6oQ/feedshare-shrink_2048_1536/B4EZpsq0GuKcAw-/0/1762759756836?e=2147483647&amp;v=beta&amp;t=CXkiq2DeYEFB2pt_zf5-0U9ekCJ2Vc1O4umxI5IC5lo" alt="Mark Zuckerberg scaled Facebook in 2005 - without Kubernetes, Serverless Functions, Redis, Managed Auth, Rust, or Kafka.

No fancy orchestration.
No distributed event streams.
No cloud-native… | Anton Martyniuk | 270 comments — Mark Zuckerberg scaled Facebook in 2005 - without Kubernetes, Serverless Functions, Redis, Managed Auth, Rust, or Kafka.

No fancy orchestration.
No distributed event streams.
No cloud-native anything.

Modern devs love to over-engineer.
We build as if our projects will scale to 1 million users tomorrow.

But here" loading="lazy">
    </div>
    <div class="embed-card-content">
      <div class="embed-card-title">Mark Zuckerberg scaled Facebook in 2005 - without Kubernetes, Serverless Functions, Redis, Managed Auth, Rust, or Kafka.

No fancy orchestration.
No distributed event streams.
No cloud-native… | Anton Martyniuk | 270 comments</div>
      <div class="embed-card-description">Mark Zuckerberg scaled Facebook in 2005 - without Kubernetes, Serverless Functions, Redis, Managed Auth, Rust, or Kafka.

No fancy orchestration.
No distributed event streams.
No cloud-native anyth...</div>
      <div class="embed-card-meta">LinkedIn &middot; linkedin.com</div>
    </div>
  </a>
</div>


Lean on your skills and your goals. If your goals are to have fun, use whatever you want. If you are looking for a job, Lean on tech that bridges the gap between your resume and the job you want. If you want to build a good product use the tech you are best at. No one in their right mind would throw away 20 years of tech progression because Zuck built facebook ftping php to a server.

The sentiment in this post is fine at best the picture feels triggering and oversimplies  way too much.  If you like kubernetes <a href="/just-fucking-use-kubernetes/" class="wikilink" data-title="just fucking use kubernetes" data-description="You want to run containers?" data-date="2025-07-01">just fucking use kubernetes</a>.

This topic deserves a full on post, maybe later.

!!! note

    This post is a <a href="/thoughts/" class="wikilink" data-title="Thoughts" data-description="These are generally my thoughts on a web page or some sort of url, except a rare few don&#39;t have a link. These are dual published off of my..." data-date="2024-04-01">thought</a>. It's a short note that I make
    about someone else's content online <a href="/tags/thoughts/" class="hashtag-tag" data-tag="thoughts" data-count=2 data-reading-time=3 data-reading-time-text="3 minutes">#thoughts</a>
