Forem: Ethan Carter

Not Everyone Gets Into FAANG — and That’s Okay

Ethan Carter — Fri, 18 Jul 2025 14:51:02 +0000

When I first started learning how to code, I knew very little about the tech industry.

All I knew was that “FAANG” — Facebook, Amazon, Apple, Netflix, and Google — was where the best engineers ended up. They were the dream. The goal. The finish line.

I saw the job titles, the salaries, the stories of engineers who made it there at 19 or 20.
It felt impossible and inspiring at the same time.
And slowly, without realizing it, I began tying my own worth to that destination.

“If I don’t get into FAANG, am I even good enough?”
“If others can do it, why can’t I?”
“What’s wrong with me?”

I never said these questions out loud. But they were always there, quietly eating away at my confidence.

The Hidden Pressure We Don’t Talk About

Let’s be honest: FAANG has become more than just a collection of companies.

In our industry, it’s almost a status symbol.
Like a badge of honor, you wear to prove you’ve “made it.”

And because of that, we rarely question it. We just chase it.

We spend months grinding Leetcode, memorizing system design patterns, and reading interview guides.
We spend so much time trying to fit into the mold that we forget to ask ourselves:

“Do I even want this for the right reasons?”
“Or am I just afraid of falling behind?”

Yes, and that is my case.

My FAANG Story (Or... Lack of One)

I applied to multiple FAANG companies, more than once.
Sometimes I got ignored. Sometimes I made it to the final round, only to be told “no.”

Each rejection hit harder than the last.
Not because I lost the opportunity, but because I felt like I had lost my identity as a capable developer.

“If I’m not good enough for FAANG, maybe I’m just not good enough, period.”

It sounds irrational now. But back then, it felt real.
That’s the problem with one-size-fits-all success stories — they leave no room for people who are still figuring things out or for people who choose to take a different route entirely.

What I Learned From Not Getting In

In the beginning, I saw FAANG as the only path to validation.
But being rejected forced me to ask a harder question:

“If not FAANG, then what?”
“What else is out there — and could that also be meaningful?”

I started working on side projects on things that I love.
I made new friends.
I helped build tools that real people used, even if it wasn't at scale.

And slowly, something changed.

I realized that the joy of being a developer doesn’t come from where you work.
It comes from what you build.
From who you build it for.
From the tiny wins, the deep learnings, the hard lessons, and the late nights where something finally “clicks.”

The Truth About FAANG (That We Rarely Say Out Loud)

FAANG is not evil.
It’s full of talented engineers, incredible projects, and big opportunities.
If you get in — congratulations, you deserve it.

But we need to stop pretending that it’s the only path worth celebrating.
Because here’s the truth that I learned from a lot of people around me:

Not everyone gets into FAANG.
Many brilliant people don’t.
Some never apply. Some never get past the first round.
And some realize… they don’t even want it anymore.

And that’s okay.

Redefining What “Making It” Means

In the end, we all have to decide for ourselves what success looks like.

Is it a job title?
A company name?
A six-figure salary?

Or is it something quieter?

Waking up excited to work on a problem you care about
Sitting down for dinner with your family after a long day of work
Laughing with friends on a Friday night, not thinking about code for once

None of these show up on LinkedIn headlines.
But they matter.
Sometimes more than you think.

If You’re Still Trying To “Make It” — Read This

Maybe you’re applying. Maybe you’ve been rejected.
Maybe you’re burnt out from the grind.
Or maybe you’ve already decided that you’re done chasing FAANG.

Wherever you are, you’re not alone.
And you are not less than anyone.

You don’t need a big name behind you to do meaningful work.
You don’t need a fancy offer to call yourself a real developer.
You don’t need validation from a company to believe in your craft.

You’re already enough.
And your story is just beginning.

Final Words

Not everyone gets into FAANG — and that’s okay.
What matters isn’t where you work.
It’s what you’re building, who you’re becoming, and how you choose to grow.

JavaScript vs TypeScript in 2025: What You Should Learn

Ethan Carter — Fri, 06 Jun 2025 00:02:34 +0000

If you're stepping into the world of web development in 2025, there's a high chance you've been torn between learning JavaScript or TypeScript. This debate isn’t new, but the context around it has evolved significantly in recent years.

In this article, we’ll break down the key differences, current trends, and practical advice to help you decide which language to invest your time in this year.

🔍 The Basics: What Are JavaScript and TypeScript?

JavaScript (JS)

JavaScript is the most widely-used language for web development. It runs in every browser, powers nearly every interactive website, and is supported by an ocean of libraries, frameworks, and tools.

TypeScript (TS)

TypeScript is a superset of JavaScript developed by Microsoft. It adds static typing, interfaces, and compile-time error checking—all while eventually compiling back into JavaScript.

All TypeScript is JavaScript, but not all JavaScript is TypeScript.

🌐 2025 Trends: What's Changed?

In 2025, the landscape of frontend and backend development will continue to shift:

TypeScript adoption has become mainstream.
Tooling and framework support is TypeScript-first.
AI-assisted coding (like Copilot and ChatGPT plugins) works smoother with TypeScript.
More jobs demand TypeScript.

⚖️ JavaScript vs TypeScript: Key Comparisons

Feature	JavaScript	TypeScript
Typing	Dynamically typed	Statically typed
Learning Curve	Easier for beginners	Slightly steeper
Error Handling	Runtime errors only	Compile-time + runtime errors
Tooling	Good	Excellent
Maintainability	Medium	High
Framework Support	Full	Full (often better DX)
Community Size	Huge	Large and growing fast
Performance	Same	Same (compiles to JS)

🧠 When Should You Learn JavaScript?

JavaScript is still essential knowledge. You should start with JavaScript if:

You're just starting out and want to understand the fundamentals.
You're building small projects or scripts.
You want to dive into frontend frameworks like React or Vue.
You’re into creative coding (p5.js, Three.js, etc.)

✅ Recommendation: Learn the core concepts of JavaScript first — variables, functions, async/await, scope, etc.

🚀 When Should You Learn TypeScript?

TypeScript shines when:

You're working on larger codebases.
You want scalability and fewer bugs.
You’re building apps with Next.js, Deno, or Node.js.
You're aiming to be a professional developer.

✅ Recommendation: Once you're comfortable with JavaScript, learn TypeScript early. The benefits grow fast.

🔄 Learning Path in 2025: A Smart Roadmap

Start with Vanilla JavaScript: Learn syntax, ES6+, DOM, fetch, async/await.
Build Projects: Start with some simple projects first.
Refactor with TypeScript: Add TS to one of your JS projects.
Use TS in Frameworks: Built with Next.js (TypeScript) or SvelteKit.
Join a Team or OSS: Collaborate on real-world TypeScript codebases.

💼 What Do Employers Want in 2025?

Startups: JavaScript is often enough if you're fast.
Companies: Mid-large companies prefer TypeScript for scale.
Open Source / Tech Leads: Favor TypeScript for long-term maintenance.

🧩 Final Verdict: JavaScript or TypeScript?

Don’t choose one over the other—embrace both.

Learn JavaScript first to build your foundation.
Learn TypeScript next to build your future.

In 2025, TypeScript isn’t replacing JavaScript. It’s enhancing it.

💬 Let's Discuss

Are you team JS or TS in 2025?

What’s your biggest struggle while learning either?

Drop your thoughts or questions below—let’s grow together. 🚀

🧠 Extra Resources

If you found this article helpful, give it a ❤️ or share it with someone starting their dev journey in 2025!