Angehefteter Tweet
mrt_mcfly
1.4K posts

mrt_mcfly retweetet
mrt_mcfly retweetet

#OnThisDay 6 April 1990
The Australian comedy drama ROUND THE TWIST was broadcast in the UK as part of Children's BBC for the first time. Following the supernatural adventures of the lighthouse dwelling Twist family, 52 episodes were made across four series and eleven years.
English
mrt_mcfly retweetet
mrt_mcfly retweetet
mrt_mcfly retweetet

INSTEAD OF WATCHING NETFLIX TONIGHT.
Spend 1 hour with this.
Claude AI FULL COURSE that teaches you how to BUILD and AUTOMATE anything.
The people who watch this tonight will wake up tomorrow with a skill that most people will not have in 2 years.
The people who skip it will still be watching Netflix next year wondering why nothing in their life has changed.
Your call.
English

Angine de Poitrine - Vol. II (Official Full Album Audio) youtu.be/OqVj4TJHpQI?si… via @YouTube

YouTube
Français

angine de poitrine - sarniezz (modular synth cover) youtu.be/EF-B5GQNqEw?si… via @YouTube

YouTube
Français
mrt_mcfly retweetet

Most APIs don't fail because of bad code. They fail because of unpredictable traffic.
If you’re building a backend meant to scale, "working" isn't enough. It has to be resilient.
Here are 5 patterns every Senior Backend Engineer uses:
1. Rate Limiting (The Shield): Don't let one rogue client or a bot scrape your entire DB. Use Token Bucket or Leaky Bucket algorithms to protect your resources.
2. Circuit Breakers (The Fuse): If a downstream service is hanging, don't keep calling it. Stop the "cascading failure" by failing fast and giving the service time to recover.
3. Idempotency Keys (The Safety Net): Network requests fail. If a client retries a "Payment" request, your system should know it already processed it. Use UUIDs for critical mutations.
4. Dead Letter Queues (The Trash Bin): Don't just discard failed background jobs. Move them to a DLQ so you can inspect, debug, and replay them later without losing data.
5. Timeout Policies (The Timer): Never let a request hang indefinitely. Every outgoing call needs a strict timeout. A hung thread is a wasted resource.
The Golden Rule: Design for the 1% of the time when things go wrong, not just the 99% when they go right.
English
mrt_mcfly retweetet
mrt_mcfly retweetet
mrt_mcfly retweetet

@DickoJa @Capt_Fishpaste 🤣🤣🤣
Using 'F*rage' and 'articulate' in the same context lmao
The guy is dense as ferk.. he only fools people who fall for him *sounding* like he knows what he's talking about
GIF
English

Piss off you muppet. They are professional footballers being paid great wages to perform a task. Articulate how that is remotely the same as importing millions of third worlders who do not contribute to our society and actively harm our way of living.
Guarantee you won’t be able to even articulate what Farage preaches. Just some buzz words like hate, division and racism. Utter tosh
English

For me, #SAFC are a beacon for what cultural, racial, and religious diversity can achieve and inspire.
A white devout Muslim partnering with a black devout Christian to produce the best midfield partnership we've seen at the club in generations ❤️🤍❤️
The very antithesis of what Farage preaches.

English
mrt_mcfly retweetet
mrt_mcfly retweetet
mrt_mcfly retweetet

As a backend engineer.
Please learn:
- System Design (scalability, microservices)
-APIs (REST, GraphQL, gRPC)
-Database Systems (SQL, NoSQL)
-Distributed Systems (consistency, replication)
-Caching (Redis, Memcached)
-Security (OAuth2, JWT, encryption)
-DevOps (CI/CD, Docker, Kubernetes)
-Performance Optimization (profiling, load balancing)
-Cloud Services (AWS, GCP, Azure)
-Monitoring (Prometheus, Grafana)
Pick up a language..
Stop jumping from one language to the other
English
mrt_mcfly retweetet

20 things that make your VIBE CODED app a SINKING SHIP :
1/ no rate limiting on API routes
> anyone can spam your backend into a $500 bill overnight
2/ auth tokens stored in localStorage
> one XSS attack = every single user account compromised
3/ no input sanitisation on forms
> SQL injection still works in 2026. your AI didnt tell you that.
4/ hardcoded API keys in the frontend
> someone WILL find them within 48 hours of launch
5/ stripe webhooks with no signature verification
> anyone can fake a successful payment event
6/ no database indexing on queried fields
> works fine at 100 users. completely dies at 1,000.
7/ no error boundaries in the UI
> one crash = white screen = user never comes back
8/ sessions that never expire
> stolen token = permanent access to that account. forever.
9/ no pagination on database queries
> one fetch loads your entire database into memory
10/ password reset links that dont expire
> old email in someones inbox = instant account takeover
11/ no environment variable validation at startup
> app silently breaks in production with zero error message
12/ images uploaded directly to your server
> no CDN = 8 second load times + massive hosting bill
13/ no CORS policy
> any website on the internet can make requests to your API
14/ emails sent synchronously in request handlers
> one slow SMTP server = your entire app hangs
15/ no database connection pooling
> first traffic spike = database crashes
16/ admin routes with no role checks
> any logged in user can access your admin panel
17/ no health check endpoint
> your app goes down silently. you find out from a client.
18/ no logging in production
> when something breaks you have zero idea where or why
19/ no backup strategy on your database
> one bad migration = all your user data. gone.
20/ no TypeScript on AI generated code
> AI writes confident, wrong, untyped code and you ship it anyway
English
mrt_mcfly retweetet











