{loading: true}

Evolution of programming languages: 1940s → Machine Code (0s 1s) 1949 → Assembly 1957 → FORTRAN 1959 → COBOL 1964 → BASIC 1970 → Pascal 1972 → C 1983 → C++ 1991 → Python 1993 → Ruby 1995 → Java 1995 → JavaScript 1995 → PHP 2000 → C# 2009 → Go 2010 → Rust 2011 → Kotlin 2011 → Elixir 2012 → TypeScript 2014 → Swift 2015 → Solidity 2026 → English

it was bound to happen one day, Nick Ball was always overrated #BallFigueroa

If you are a graphic designer and have experience with mobile ui, dm me

🤣🤣

Your app is slow. Your users are waiting 3, 4, maybe 5 seconds for a page to load. You check your logs. The problem isn't your code. It's your database. It's on fire. It's spending all its time running the same complex 'SELECT' queries with 'JOINs' and 'ORDER BY' clauses, over and over, just to fetch a user's profile and their 10 most recent posts from a slow, spinning disk. You've heard of Redis. You think 'cache'. You also think, 'it's in-memory, so if my server reboots, all my data is gone'. You think it's just a temporary, volatile speed boost, a fragile layer you can't really depend on for anything important. That's not the full story. I was digging into it, I was expecting a simple cache. What I got was a Swiss Army Knife for my data. Here was my journey from slow app to superpower. Step 1: The 'Hello World' (The Obvious Cache) This is what everyone does, and it's brilliant. - My Problem: That slow 3-second SQL query. - My New Workflow: I fetch the data 'once', 'SET' it in Redis (which lives in blazing-fast RAM), and set an expiration of 5 minutes. - For the next 5 minutes, 10,000 requests for that profile are served in 'sub-milliseconds'. - My database load just dropped 99%. My app is fast. But the real magic begins when you stop treating it like a dumb string store. Step 2: The Click Moment (Data Structures) The real power is that Redis is a high-speed data 'structure' server. - My Problem: I need a real-time leaderboard. My 'ORDER BY score' query is killing my 10-million-row 'users' table. - My New Workflow: I use a Redis 'Sorted Set'. When a user's score changes, I 'ZADD leaderboard-main 19850 'user:123''. Redis handles the sorting 'instantly' on insertion. Fetching the top 10 is near-instant. Step 3: The 'Wait, what?' Features - My Problem: I need a list of recent notifications. 'SELECT ... LIMIT 20' is still a waste. - My New Workflow: I use a Redis 'List'. When a new notification comes in, I 'LPUSH' it. Then I 'LTRIM' the list to keep it at 20 items. It's a perfect, high-speed stack. - My Problem: I need a background job queue to send welcome emails. - My New Workflow: I don't install RabbitMQ. I just 'LPUSH' a job to a 'List', and my worker 'BRPOP's (blocking pop) to wait for the next job. It's simple and reliable. - My Problem: I need a real-time chat app. - My New Workflow: I don't build a complex WebSocket server. I just use 'Pub/Sub'. It's a high-speed, lightweight message broker built-in. Step 4: The "Pro Escape Hatch" (Debunking the Myth) This is what sold me. - My Fear: 'But if it reboots, my data is gone!' - The Reality: Redis has 'persistence'. It's not on by default (for speed), but it's there. - It can take 'snapshots' (RDB) of your dataset. Or, it can keep an 'Append-Only File' (AOF) log of every single write command. - It's not a replacement for Postgres as your 'source of truth', but it's far from a 'throwaway' cache. It's your cache, your message queue, your session store, your leaderboard, and your real-time engine, all in one. I thought Redis was a 'nice-to-have' performance boost. It's not. It's the high-speed multi-tool for your entire application.

what consistency actually is:

she should be lucky to get a third fight after losing twice

building in sf with your best friend >

@rockyaliboxing all brilliant fights 🥊

5 of the fights in boxing I'd like to see the most... AJ vs Fury Yarde vs Buatsi Beterbiev vs Benavidez Boots vs Ortiz Inoue vs Nakatani

@t3dotchat has become something I use daily. It’s fast, cheap and does everything you need it to do. Worrying how big companies couldn’t do this and it took 2 devs (I think) a few days to get this done

*chefs kiss*

⚛️ If you are using fetch() in a useEffect, you probably want to watch this short video ↓

how is this even a question 🤣🤣

‼️ If I was A fighter I would love my promoter to show love like that instead like Oscar snorting it up!!! @EddieHearn Best promoter out there!! #Faxxx 😤😤😤 #Boxing 🥊 🥊 🥊

so he leaves Matchroom, to do nothing with Boxxer, to then move back to Matchroom So much time wasted for nothing

‼️ Canelo Alvarez meeting with Turki Alalshikh in London today…

Fury losing was brilliant for boxing. Tired of fighters trying to protect their 0’s like fans really care. Get the best fights made and make the sport great again. The fighters get the money they deserve and the fans get the fights they deserve to see.

A special gift for all boxing fans directly from the Gypsy King!!! Happy new year to all 🙏🏽 #HappyNewYear #tysonfury