Mazzy

[Formula 1 @F1]

Seamless 🤩

#F1 #SingaporeGP

[gündemio @gundemio]

Assetto Corsa oyununda, gerçeğe yakın bir deneyim sunan oyun modu yapıldı.

[Bagrescore Brazil @BagrescoreBr]

é a edit do ano https://t.co/lz8Dng80tz

[NiK @Oye_Nik]

All men want is s@x and money"
The average man's dream:

[Lucas 🦇 @vlucasrocha]

utilidade pública! a Barbra já trabalhou como recrutadora e deu dicas de como se sair bem numa entrevista de emprego

[Nett0 @nett0eth]

A Anthropic liberou um workshop de 26 minutos ensinando como fazer prompts pro Claude de verdade.

Saber escrever prompts é o que separa quem usa IA de quem aproveita IA de verdade.

Quem fez o vídeo:
o time que construiu o Claude.

Legendei em português. Aproveitem.

[REAL MIL GRAU @realmilgrauu]

Simplesmente, Bad Bunny, Timothée Chalamet, Bellingham, Lamine Yamal, Dembele, Raphinha, Pedri e Lionel Messi juntos.

A Adidas lançou um comercial especial da Copa do Mundo.

Isso aqui é papo de cinema.

[Celio 💻 @devcelio]

Como treinar para entrevistas com ajuda de IA?

[Augusto Galego @RealGalego]

CURSO COMPLETO DE ESTRUTURAS DE DADOS E ALGORITMOS

[F1 TROLL @f1trollofficial]

We lost the T-Pose but got the 🤙 pose

[YourCloudDude | AWS & Python @yourclouddude]

AWS isn’t hard - you’ve just been learning it backwards.

Start with these first:
• EC2 → run apps
• S3 → store files
• IAM → control access
• Lambda → run code
• RDS → databases
• VPC → networking
• CloudWatch → monitoring

Learn these.
Build 2–3 projects.
Connect the dots.

That’s when AWS finally clicks.

[Shikhar @shekhu04]

Low-key websites I quietly rely on

1) https://t.co/FDnurfhwge
Gives you a brutally clear learning path for roles like frontend, backend, DevOps, etc
No fluff, just “learn this → then this → then this”.

2) https://t.co/1xhB1Us0oz
An online playground to quickly test HTML, CSS, JS without setting up anything locally
Perfect for quick experiments and debugging ideas

3) https://t.co/d80zVxq6TY
A collection of reusable React hooks with real use cases
Saves time and helps you avoid rewriting the same logic again and again

4) https://t.co/UgqeLiqese
Concise cheat sheets for languages, frameworks, and tools. Ideal when you forget syntax and don’t want to read a 20-minute blog

5) https://t.co/OehnjnfVix
Turns messy JSON into a clean visual tree
Makes understanding large APIs and configs way easier than staring at raw text

6) https://t.co/mcMPeqEFWJ
Lets you generate and preview color palettes instantly
Useful when you want decent UI colors without guessing or copying blindly

7) https://t.co/9yEsuJrWCB
Build, test, and debug regex step by step with explanations Honestly, the fastest way to stop hating regex

8) https://t.co/7eM95WZ8cJ
Shows how big an npm package really is before you install it
Helps you avoid bloating your app with “tiny” libraries

9) https://t.co/Za87baZsBk
Tells you which CSS/JS features actually work across browsers Essential before using shiny new features in production

10) https://t.co/YeYh94AX4R
Google’s own diagnostics tools for DNS, email, headers, and network issues
Surprisingly useful for debugging real-world problems

👉 Which one of these do you already use and which one did you not know existed?

[✪ Felippe @FelippeRegazio]

Isso é uma fase pesada, e não é só desânimo: nos sentimos desimportantes. Como se fôssemos engrenagens idênticas para IA, sem valor ou personalidade na profissão. Minha dica: estude AI e os gaps dela do ponto de vista da engenharia e vc encontrará um mundo de oportunidades +

[Abhishek Singh @0xlelouch_]

As a senior backend engineer, please learn:

1. SOLID design principles

2. Multithreading and concurrency models

3. Immutability and safe state management

4. Streaming and messaging systems (Kafka, queues, pub/sub)

5. Caching strategies (in-memory, distributed, eviction policies)

6. Security fundamentals (TLS/SSL, JWT, OAuth2, authentication vs authorization)

7. Core design patterns (factory, decorator, singleton, observer)

8. Test-Driven Development (TDD) and testability

9. API design and versioning (REST, gRPC, backward compatibility)

10. Database fundamentals (schema design, indexing, transactions)

11. Distributed systems basics (consistency, retries, idempotency, failure modes)

12. Observability (logging, metrics, tracing)

13. Performance tuning (profiling, memory, latency vs throughput trade-offs)

14. Deployment and runtime basics (Docker, CI/CD, config management)

15. Reading and debugging production systems

These aren’t optional. Period.

Feel free to add anything that I missed.

[Sam @samsantosb]

Como arrumar aqui:

- Troca por package by feature
- Para de dar re-throw no controller
- Não sobe console em prod
- Tenha uma layer pra regras de negocio caso o app va escalar

[CSGOBig @csgobigBR]

Passam os meses, passam os anos… e esse continua sendo o melhor clipe de todos os tempos 🤣

https://t.co/IN0EiKBfFU

[Augusto Galego @RealGalego]

O vídeo em questão, só 9 minutos:

https://t.co/1NQNPU5Kqq

[sankit @sankitdev]

Backend isn’t just APIs and CRUD.

This is the roadmap companies like Google, Meta, Amazon expect you to know.

DSA
> Companies like Google don’t care about your projects if you fail here.
> This is the real filter.
> Conquer this, and every door in tech opens.
> Struggle here, and those doors stay shut.

0. Ground Setup

Before going crazy with topics, you need:

> One main backend language (JavaScript/TypeScript, Go, Java, Rust — pick one and master it)
> Git + GitHub: branching, PRs, rebases, conflict resolution
> Linux basics: ls, cd, cat, grep, find, permissions, SSH
> Editor mastery: VS Code or any solid setup

First principles here:
> What is a program? How does source code become a running process?
> What is an OS process vs thread?
> What does it mean to run a server on a port?

You should be able to:
> SSH into a Linux box, pull a repo, install deps, run a server on a port, view it via browser

---

1. Core Backend Fundamentals

1.1 Networking and HTTP

You cannot be a strong backend engineer if HTTP is just “that thing Express uses”.

Understand:
> DNS → IP → TCP → HTTP
> Difference between IP / TCP / UDP / HTTP / HTTPS
> HTTP methods, status codes, headers, idempotency, safe methods
> REST vs RPC vs GraphQL

Practice:
> Build a backend without any framework using native http
> Parse JSON body manually
> Implement basic rate limiting
> Add API versioning (/v1, /v2)

---

1.2 API Design and Backend Architecture Basics

First principles:
> Resource modeling
> Stateless vs stateful
> Consistent naming, validation, clear errors
> Pagination, filtering, sorting

Layered architecture:
> Controller → Service → Repository (DAO)

You should be able to:
> Design APIs for Task Manager or Expense Tracker
> Keep error and response structure consistent everywhere

---

2. Databases and Data Modeling

Big companies will grill you here.

2.1 Relational Databases

SQL is non-negotiable.

Understand:
> Table, row, column, primary key, foreign key
> Normalization: 1NF, 2NF, 3NF basics
> Joins: inner, left, right, full
> Transactions and ACID
> Indexes and their impact

You should be able to:
> Instagram schema: users, posts, likes, comments, followers
> Query top posts, mutual followers
> Use migrations, not manual DB edits

---

2.2 NoSQL and When to Use It

Understand:
> Document DB vs relational DB
> Denormalization
> Event logs and analytics needs
> CAP theorem basics
> Collections, documents, indexes, aggregation pipeline

Be able to decide:
> When a feature needs SQL vs NoSQL

---

3. Authentication, Authorization and Security

3.1 Auth Basics

Understand:
> Authentication vs authorization
> State vs stateless auth
> Password hashing (bcrypt/argon2)
> Cookies: HttpOnly, Secure, SameSite
> Access vs refresh tokens
> Token revocation and rotation
> Basics of OAuth2 / OpenID Connect

You should be able to:
> Implement email/password auth with verification and forgot password
> Explain cookies vs localStorage
> Explain token invalidation strategies

---

3.2 Web Security Core

Understand:
> SQL injection, XSS, CSRF, IDOR (OWASP Top 10)
> Input validation and output encoding
> CORS and preflight

You should be able to:
> Identify common vulnerabilities in APIs
> Configure CORS correctly

---

4. Concurrency, Performance and Scalability

4.1 Concurrency and Asynchrony

Understand:
> Event loop, callback queue, microtasks
> Blocking vs non-blocking I/O
> CPU-heavy work blocks Node

You should be able to:
> Explain when to use worker threads and offloading

---

4.2 Caching

Concepts:
> In-memory vs Redis caches
> TTL, LRU, invalidation
> HTTP caching: ETag, Last-Modified, Cache-Control

You should be able to:
> Use Redis to cache DB queries and rate limit
> Plan cache keys well

---

4.3 Scaling and Architecture Patterns

Understand:
> Vertical vs horizontal scaling
> Stateless services for scale-out
> Load balancers
> Monolith vs microservices
> Sync vs async flows (queues)

Patterns:
> Circuit breaker
> Retry with backoff
> Idempotency keys for POST

You should be able to:
> Split a monolith into services and make them communicate

---

5. Messaging, Queues and Async Systems

Understand:
> RabbitMQ, Kafka, Redis streams
> Producers, consumers, delivery semantics

Use cases:
> Emails, uploads, payment pipelines, logs

You should be able to:
> Offload heavy jobs to background workers
> Build async workflows

6. Testing and Quality

Understand:
> Unit, integration, E2E tests
> Test pyramid
> Deterministic vs flaky tests

You should be able to:
> Test auth flows and business logic
> Run tests in CI (GitHub Actions or similar)

7. DevOps Basics for Backend Engineers

7.1 Containers and Deployment

Understand:
> Dockerfile basics (FROM, COPY, RUN…)
> Docker Compose for app + DB
> Environment variables and config

You should be able to:
> Containerize backend and DB
> Deploy to any cloud provider

7.2 CI/CD and Observability

Understand:
> CI pipelines: tests, lint, build
> Auto deploy workflows
> Logging and metrics

You should be able to:
> Add logging middleware with request IDs
> Monitor latency, error rate, throughput

8. System Design

This becomes crucial for big tech interviews.

Understand:
> Load balancer, app server, DB, cache, queue, file storage
> Consistency models
> API Gateway and BFF patterns
> Unique ID generation (UUID, Snowflake)

Practice on paper:
> URL shortener
> Instagram feed
> E-commerce checkout
> Notification systems

Consider:
> DB schema, caching, queue usage, failure handling

9. Domain-Specific Knowledge

Depending on role and product:

> Fintech: strong consistency, audit logs, idempotency
> E-commerce: carts, pricing, orders, inventory
> Real-time: WebSockets, SSE, backpressure

Choose what aligns with your career direction and keep grinding.

[yuri.tsx @rxmosdev]

pra ajudar os amigos devs! os assuntos em si não achei difícil mas falar muito e durante muito tempo sobre eles foi o que me gargalou e me fez hesitar em alguns pontos

o que cobraram de mim em uma entrevista pleno/sênior:

segue o fio (+)