@ConsciousRide Avatar @ConsciousRide Akshay Shinde

Akshay Shinde posts on X about redis, ai, realtime, if you the most. They currently have [-----] followers and [---] posts still getting attention that total [------] engagements in the last [--] hours.

Engagements: [------] #

Engagements Line Chart

Mentions: [--] #

Mentions Line Chart

Followers: [-----] #

Followers Line Chart

CreatorRank: [-------] #

CreatorRank Line Chart

Social Influence

Social category influence technology brands 19.27% stocks 12.84% finance 6.42% countries 3.67% social networks 2.75% celebrities 0.92% financial services 0.92%

Social topic influence redis #4, ai #6028, realtime #221, if you 7.34%, app #2130, strong 4.59%, $uber 4.59%, engineering #2594, status #1745, data 3.67%

Top accounts mentioned or mentioned by @0xlelouch_ @0xlelouch @sgm6912 @dhanpalraj1998 @soroushp4 @ryancooper8311 @codelune259 @shivemnn @helderbuilds @asolovichh @vibecoderofek @mainakmukh47974 @avrldotdev @varletint @nextbundleanalyzer @sidjain80 @tawakkalah1310 @ashtwtz @codesagar @siddcodes1

Top assets mentioned Uber Technologies, Inc. (UBER) Alphabet Inc Class A (GOOGL) Cloudflare, Inc. (NET)

Top Social Posts

Top posts by engagements in the last [--] hours

"As an Engineer do you know if ChatGPT uses WebSockets/sockets for live chat streaming or just normal HTTP API calls with SSE #OpenAI #Engineering https://twitter.com/i/web/status/2019833244330684871 https://twitter.com/i/web/status/2019833244330684871"
X Link 2026-02-06T17:59Z [----] followers, 96.4K engagements

"Going for a Next.js Interview Be ready to discuss performance. Here are [--] points worth talking about when performance questions come up: [--]. Choose right rendering strategy: SSG for static content ISR for semi-dynamic pages SSR only when data changes per request [--]. Use next/image everywhere: automatic optimization lazy loading modern formats responsive sizes without extra config [--]. Dynamic imports + next/dynamic: split heavy components or client-only code load them only when needed [--]. Leverage Partial Prerendering (PPR): static shell fast dynamic holes filled later good middle ground 5."
X Link 2026-02-13T14:58Z [----] followers, [----] engagements

"Top [--] DevOps & Cloud Concepts Every Developer Should Know (2026 edition) Foundations [--]. Infrastructure as Code (Terraform/Pulumi) [--]. Containers (Docker) vs Orchestration (Kubernetes) [--]. CI/CD Pipelines [--]. GitOps [--]. 12-Factor App Principles Cloud Building Blocks [--]. Virtual Private Cloud (VPC) & Subnets [--]. IAM & Least Privilege [--]. Serverless (FaaS + BaaS) [--]. Managed Databases vs Self-hosted [--]. Object Storage (S3-style) Reliability & Scaling [--]. Auto Scaling Groups [--]. Blue-Green / Canary Deployments [--]. Circuit Breakers & Retries [--]. Chaos Engineering Basics [--]. Multi-region / Multi-cloud"
X Link 2026-02-15T21:07Z [----] followers, [----] engagements

"ngl comforts addictive. the real glow-up starts when you say yes to uncomfortable things - eyes closed"
X Link 2025-10-20T07:01Z [----] followers, [---] engagements

"Your $3000 bed asking AWS for permission to change temperature is the perfect metaphor for how far we've strayed from building resilient products. I think AWS outages should happen more often So people realise the true value of decentralised internet and local offline modes. I think AWS outages should happen more often So people realise the true value of decentralised internet and local offline modes"
X Link 2025-10-21T10:07Z [----] followers, [----] engagements

"The next internet wont be websites: itll be agents talking to each other. HTTP was for humans. A2A (Agent-to-Agent) is for machines. Soon agents will: Negotiate API access Exchange structured data Authenticate + transact autonomously OpenAIs AgentKit Googles AP2 and the Model Context Protocol (MCP) are the early signs. Next app wont have an API route. Itll have an Agent Interface"
X Link 2025-11-15T17:18Z [----] followers, [---] engagements

"As a frontend engineer please learn: - component composition over prop drilling - state management that doesn't turn into spaghetti - accessibility isn't optional (ARIA keyboard nav) - performance (lazy loading code splitting memoization) - security (XSS CSP sanitization) - async patterns and error boundaries - responsive design without media query hell - testing that actually catches bugs As a backend engineer. Please learn: - SOLID design principles - Multithreading - Immutability - Streaming messaging - Caching - Security - SSL JWT OAuth - factory decorator singleton obeservable design"
X Link 2026-01-25T04:36Z [----] followers, 111.8K engagements

"Frontend Roadmap Beyond React/Vue/Svelte Basics (2026 Edition) If you skip these you'll ship pretty UIs but not fast resilient accessible experiences that survive real traffic and angry users: [--]. Browser internals: event loop rendering pipeline critical rendering path layout/reflow/repaint triggers compositor vs main-thread work [--]. Performance reality: Core Web Vitals (p75/p95 LCP INP CLS) code splitting + prefetch lazy hydration virtualization (react-window / virtuoso) bundle analysis + treeshaking wins [--]. Accessibility (a11y) as engineering: semantic HTML + ARIA patterns focus traps &"
X Link 2026-01-27T01:42Z [----] followers, [----] engagements

"A billion users sending messages every second means billions of read receipts firing constantly. One boolean column sounds simple until your database melts from write load. Here's how messaging platforms actually build this feature at scale == Why the naive approach fails Adding an is_read boolean to your messages table seems obvious. When someone reads a message flip it from false to true. But at scale this creates a write for every single message read. If a group chat has [---] members and one person sends a message that's [---] writes when everyone reads it. Multiply that across billions of"
X Link 2026-01-29T11:16Z [----] followers, 61.5K engagements

"Frontend Security [---] I wrote a complete frontend security hardening guide covering: [--]. Always use HTTPS (enforce HSTS + upgrade insecure requests) [--]. Set strong security headers (CSP X-Content-Type-Options X-Frame-Options Permissions-Policy Referrer-Policy) [--]. Sanitize & validate ALL user input before rendering (never trust client-side only) [--]. Prevent XSS properly (use DOMPurify / sanitize-html avoid dangerouslySetInnerHTML) [--]. Store tokens securely (HttpOnly + Secure + SameSite=Strict cookies over localStorage when possible) [--]. Implement CSRF protection (tokens for state-changing actions"
X Link 2026-01-29T15:48Z [----] followers, 27.9K engagements

"Cloudflare dealing with 12h backups on 50TB ClickHouse here's how to cut that time hard without fancy tricks: Full backup every time is consuming the [--] hours. Switch to weekly full snapshot & daily incremental using clickhouse-backup. For append-only OLAP workload like this incremental only grabs new or changed partitions so backup time drops a lot often to couple hours or less. On restore side bring up recent data first; say last 7-30 days partitions to make the service live again quickly. Then let older data backfill async in background. Partition-level restore is what actually saves time"
X Link 2026-01-31T16:48Z [----] followers, [---] engagements

"8 things fullstack devs should know in [----] (not another Next.js tutorial list) [--]. SSR vs CSR hydration tradeoffs: Controls first paint SEO interactivity timing. Know streaming and selective hydration rules. [--]. State that survives refresh and scale: Client state with Zustand or Jotai. Server state via tRPC or React Query. Avoid context soup. [--]. Database indexing when load hits: Compound indexes covering queries reading EXPLAIN. [---] ms to [--] ms matters at scale. [--]. API paradigm tradeoffs: REST versus GraphQL versus tRPC versus RSC. Understand over-fetching N+1 mobile battery impact. [--]. Auth"
X Link 2026-02-02T16:44Z [----] followers, [----] engagements

"As a frontend developer Building real-time chat apps how do you handle the messages list Do you re-render the whole conversation component on every new msg Or use virtualized lists (react-window) memoized bubbles immutable state updates + auto-scroll logic Best practices for sender/receiver bubbles & performance #webdev #react #frontend https://twitter.com/i/web/status/2018468736018284864 https://twitter.com/i/web/status/2018468736018284864"
X Link 2026-02-02T23:37Z [----] followers, 17.6K engagements

"most chat uis start lagging badly once you cross [---] [----] messages. every new text forces the whole list to re-render and it feels choppy fast. this is how you actually build one that stays smooth even at 10k+ messages and rapid incoming msgs. - use virtualization right from the start. react-virtuoso is the cleanest choice for chats because it supports inverted scrolling natively and handles resize + new items without jitter. react-window works too if you flip the list yourself. - store messages in reversed order inside state. newest message lives at index [--]. this matches how most chat uis"
X Link 2026-02-04T17:45Z [----] followers, [---] engagements

"Compute the running balance when you write each transaction. Just add or subtract to previous balance and store it right there in the row. Index properly on user_id plus created_at or id. Reads become range scans instead of full table nonsense. Always paginate hard. Cursor based. Limit [--] or [---] rows max per call. Client asks for next page when needed. Never try to compute SUM over 1M rows on read. That kills postgres or any db under load. If you ever need to fix historical balances which is rare run a background job with window function on chunks not the whole table at once. Thats how ledger"
X Link 2026-02-04T18:43Z [----] followers, [----] engagements

"You're designing Twitter/X-style rate limiting for posting tweets / API calls (both per-user and global abuse prevention). How do you implement something that survives sudden viral spikes without over-limiting good users"
X Link 2026-02-05T12:11Z [----] followers, [----] engagements

"@DhanpalRaj1998 Its not really just those three things. Theres certificate validation against the chain key agreement (not just exchange) and the finished messages to confirm nobody tampered midway"
X Link 2026-02-06T15:41Z [----] followers, [--] engagements

"@SidJain_80 100% that's how they do it they dont use sockets and they stream via https + sse for simplicity streaming chunks and it is unidirectional do you know how Server Sent Events actually work under the hood"
X Link 2026-02-06T18:10Z [----] followers, [----] engagements

"Redis for increments no question. Just bump the count there for every view. Super fast no locking mess. Then a simple worker pulls the delta every few seconds or minute and adds it to the posts table in batches. One write instead of a million. CPU drops immediately. For the really viral ones you can shard the counter across a few keys so no single hot spot forms. Eventual consistency works perfectly here nobody cares if the number is exact to the second. Thats the practical fix Ive seen work at this scale. https://twitter.com/i/web/status/2020078632178467125"
X Link 2026-02-07T10:14Z [----] followers, [----] engagements

"The bug is usually inconsistent routing to different backend instances that aren't in sync. One pod/server has fresh data or healthy db connection so returns [---]. Another has stale cache / delayed replication / missing record so gives [---]. Third one might be having connection pool exhaustion or disk full or deployment half-rolled so throws [---]. Retries hit random instances again so things get worse instead of better. You see this pattern a lot when autoscaling kicks in or during rolling updates or when read replicas lag. Tracing the request to see which pod/ip answered each time usually shows"
X Link 2026-02-07T14:28Z [----] followers, [----] engagements

"A very popular post gets millions of likes/comments in minutes (hot key problem). Remember when Virat Kohli dropped that T20 World Cup victory post and it got like 20+ million likes in no time How do you stop your like-counter service (or database) from completely dying under that insane traffic spike What tricks do you use to handle these 'hot key' moments without everything crashing"
X Link 2026-02-07T18:28Z [----] followers, [----] engagements

"This happens because the API trusts the user_id from the URL instead of checking who actually owns the resource. The right way is to pull the user id straight from the auth token (jwt/session) and compare it with the resource owner on the server side. If they dont match just return [---]. Never trust anything coming from the client in these cases"
X Link 2026-02-08T08:10Z [----] followers, [----] engagements

"Full-Stack [--] Projects List Advanced Task Manager (Kanban + Drag & Drop + PWA) Personal Finance Tracker + Visual Dashboard Multi-Author Blog / CMS with Markdown Editor Real-time Collaborative Notes / Whiteboard URL Shortener with Analytics + QR Codes Recipe Finder + Meal Planner Event Management + RSVP + Maps Integration Job Board / Freelance Marketplace Full E-commerce Store (Cart + Payments + Admin) Mini Social Media (Posts + Likes + Threads + Feed) Learning Platform / Mini LMS (Courses + Quizzes) Appointment Booking System + Calendar Sync Habit Tracker with Social Streaks & Leaderboard"
X Link 2026-02-08T08:13Z [----] followers, 13K engagements

"@0xlelouch_ shipping something every month even tiny keeps you finishing instead of polishing forever writing weekly posts forces clearer thinking even when its simple start with one small thing today waiting for perfect moment usually turns into nothing at all"
X Link 2026-02-08T14:32Z [----] followers, [----] engagements

"Sliding window counters on Redis usually win here. Token bucket allows more bursts but sliding gives better fairness across the minute. For per-user and global you run two keys: one per user id and one shared global counter. Lua script does the increment and check atomically so no race between pods. If redis is single point then add replicas with eventual sync or go gossip style like envoy does but most places stick to redis and lua. For dynamic tiers just fetch limit from config service per request or cache it. Multi region add redis cluster per region and accept slight over limiting during"
X Link 2026-02-08T17:57Z [----] followers, [----] engagements

"This happens because name got cached somewhere even after DB update finished. Cache can sit in these places usually - browser local state or http cache headers - cdn edge layer - api gateway or proxy - backend redis/memcache - frontend query library like react query / apollo - sometimes read replica delay if read goes to secondary To make sure it shows correct name right away for the person who just changed it - after successful update call clear or update the exact cache entry - for that user force read from primary db or skip cache once - use optimistic update in ui set new name immediately"
X Link 2026-02-08T18:08Z [----] followers, [---] engagements

"Backend is dumping entire table or massive join without any limit. First thing I do is talk to backend guy saying that please fix the API add proper pagination or filters. No frontend magic fixes 100MB properly. If they cant change it right now: - Stream the response if possible (fetch with ReadableStream) - Parse only chunks I actually need - Use virtualization so UI doesnt try to render everything But honestly most of these cases fail on network and parse time before UI even starts. Actual fix is always smaller payload from server. That is it"
X Link 2026-02-08T18:15Z [----] followers, 10.2K engagements

"Graceful shutdown catches SIGTERM stops accepting new ws connections on old pods but keeps existing ones alive till they close naturally or timeout. Rolling update in k8s with readiness probes does the rest new pods come up healthy first traffic shifts slowly old ones drain before termination. State in redis so reconnect just works client retries handle the rare drops without user noticing anything. That's how you avoid the mass disconnect storm at 100k"
X Link 2026-02-09T05:11Z [----] followers, [----] engagements

"First check slowlog to see which command and value size is actually consuming CPU. Then pull that 1M qps read path out of Redis completely short ttl local cache in the app or shrink the payload if possible. If Redis has to stay in the loop just copy the hot key to a few instances and balance the gets across them. https://twitter.com/i/web/status/2020769965591445741 https://twitter.com/i/web/status/2020769965591445741"
X Link 2026-02-09T08:01Z [----] followers, [---] engagements

"Docker stays useful even for small projects. Kubernetes only when traffic gets serious or you run many services. Add Redis somewhere for caching it changes speed a lot. Postman works but Bruno or Insomnia feel lighter these days. Jira can consume time if the team is small. good list we can use these tools based on project size. https://twitter.com/i/web/status/2020806207741845703 https://twitter.com/i/web/status/2020806207741845703"
X Link 2026-02-09T10:25Z [----] followers, [---] engagements

"That viral spike overloads systems quick. Twenty million likes in a few minutes will break your basic counters if you havent set things up smart. Breakdown of what works at scale: - Redis grabs every like increment upfront. It uses atomic INCR operations to avoid any locking issues or race conditions during the flood. This keeps things moving without bottlenecks. - The app pulls the count from Redis for display. Users get the up-to-date number without waiting even under heavy load. - A background process batches the changes and writes them to a persistent store like Postgres or Cassandra"
X Link 2026-02-09T10:31Z [----] followers, [---] engagements

"@Tawakkalah13_10 nginx as load balancer is common but it can become single point of failure itself if not setup in active-passive or active-active mode with keepalived or similar"
X Link 2026-02-09T10:38Z [----] followers, [--] engagements

"The only backend concepts you need to know API paradigms REST GraphQL tRPC/gRPC trade-offs Authentication JWT vs Sessions OAuth2 flows Refresh tokens Authorization RBAC vs ABAC Middleware guards Databases SQL (Postgres default) vs NoSQL (when to choose) Caching Redis patterns (TTL cache-aside write-through) Rate limiting Token bucket Leaky bucket Sliding window Async processing Queues (RabbitMQ / Kafka) Background jobs Error handling Global exceptions Custom error classes Logging & Monitoring Structured logs Metrics (Prometheus) Tracing Scaling basics Horizontal vs Vertical Load balancers"
X Link 2026-02-09T15:59Z [----] followers, 30.7K engagements

"@0xlelouch_ Netflix case showed this: app logs commit before the actual durable write happens. Transaction rolls back after. Or replication lag hits reads go to stale replica. Lesson stays simple. Never trust logs alone. Always check data at rest"
X Link 2026-02-10T01:20Z [----] followers, [---] engagements

"UUIDs as PK make joins slow because they are [--] bytes and random. Indexes get fragmented cache misses happen more comparisons take extra time. Integers stay compact and sequential so everything stays faster. Common fix is use UUID only for external / API exposure. Keep bigint surrogate key inside the service for joins. Or switch to UUIDv7 if you need ordered values without losing uniqueness. We did this in one project that bigint for internal relations UUID just for public refs. Queries became way quicker on large tables. https://twitter.com/i/web/status/2021032330853482857"
X Link 2026-02-10T01:23Z [----] followers, [---] engagements

"As an Engineer As you know ChatGPT uses the HTTP + SSE combo for user interactions / streaming replies. Do you know how to actually implement it And how it works under the hood"
X Link 2026-02-10T02:09Z [----] followers, [----] engagements

"@ash_twtz this list is gives good start as a beginner in js"
X Link 2026-02-10T06:26Z [----] followers, [---] engagements

"@code_sagar principles of building reliable systems havent changed"
X Link 2026-02-10T09:39Z [----] followers, [---] engagements

"grpc is heavily used but almost always for internal service to service communication in microservices architectures not usually for public/client facing APIs. big production orgs like netflix uber dropbox square spotify tictok robinhoood airnb slack cisco etsy and list goes on. https://twitter.com/i/web/status/2021184197407474155 https://twitter.com/i/web/status/2021184197407474155"
X Link 2026-02-10T11:27Z [----] followers, [---] engagements

"50k payments per second with zero double charges is one of the hardest problems in backend engineering. One bug here means real money disappearing or charging customers twice. Idempotency first Client creates a UUID as idempotency key and puts it in the header of every payment request. Server checks key in redis or db table before processing. If it exists return stored response. If missing process payment once then store key and result. Retries just execute once. Write key first with unique constraint. Concurrent duplicates mean one processes and others return the existing outcome. Latency"
X Link 2026-02-10T12:08Z [----] followers, 18.5K engagements

"The only frontend concepts you need to know (2026 edition) Component composition Props drilling vs Context vs Composition Hooks rules useState useEffect useRef useTransition useOptimistic useActionState custom hooks State management Zustand / Jotai (simple) vs Redux Toolkit (complex) Data fetching TanStack Query / SWR Suspense + loading states Server Components React Server Components Server Actions Streaming UI Suspense boundaries incremental rendering progressive hydration Performance Memo useMemo/useCallback lazy + Suspense Accessibility Semantic HTML ARIA roles keyboard nav screen reader"
X Link 2026-02-10T12:28Z [----] followers, [----] engagements

"You're implementing real-time notifications (not just polling) for a chat and social app. WebSockets vs SSE vs push notifications vs long-polling what mix do you actually pick at different scales and how do you handle reconnections and duplicates gracefully https://twitter.com/i/web/status/2021230675500609659 https://twitter.com/i/web/status/2021230675500609659"
X Link 2026-02-10T14:32Z [----] followers, [---] engagements

"@RyanCooper8311 Great points. Hourly recon and timestamp validation on idempotency keys makes a lot of sense"
X Link 2026-02-10T18:00Z [----] followers, [--] engagements

"@Siddcodes1 Namecheap hands down better renewal prices free privacy forever and way less upsell nonsense than GoDaddy. Porkbun is also good if you want super transparent pricing"
X Link 2026-02-11T08:49Z [----] followers, [---] engagements

"To fix it put a CDN like Cloudflare or Fastly or AWS CloudFront with points in India Mumbai region. Cache responses at edge so Indian requests never reach origin most times. If API allows edge compute or regional replication do that too. That drops time close to what Australia sees without touching code. Simple geography fix not code fix. https://twitter.com/i/web/status/2021543800154562710 https://twitter.com/i/web/status/2021543800154562710"
X Link 2026-02-11T11:16Z [----] followers, [----] engagements

"@0xlelouch_ always better to look at actual responsibilities take home after tax and what cost of living"
X Link 2026-02-11T11:20Z [----] followers, [---] engagements

"People are pointing at the spacex merger as a possible trigger for some internal shakeup but the posts from Ba and Wu stay pretty calm talking about next chapters and staying friends with the team. No public drama or direct shots at leadership. Compute still being the big limiter makes the timing feel off especially when Elon says its handled. Talent walking away at this stage could slow things down even if the mission stays the same. Curious to see if more names surface soon or if they start backfilling fast. What do you think is really behind the wave"
X Link 2026-02-11T14:03Z [----] followers, [----] engagements

"Check locks first. [--] seconds for single row update almost always means blocked by another transaction. Run pg_locks or show engine innodb status (depending on db) find who is holding the lock on that row or table. Kill if needed then see why that other transaction is taking so long. If no lock then explain analyze the query see if index on where column is missing or not used. https://twitter.com/i/web/status/2021589477018448156 https://twitter.com/i/web/status/2021589477018448156"
X Link 2026-02-11T14:17Z [----] followers, [----] engagements

"these days for core AI engineering skills (LLM APIs RAG agents evals deployment patterns) the amount of high-quality free/very-low-cost material is massive: - Official docs + cookbooks from OpenAI/Anthropic/Cohere - YouTube (Andrej Karpathy lectures gkcs old free videos full paper walkthrus) - GitHub repos with production-grade examples -Cheap Udemy/Zero-to-Mastery style courses during sales the $1500 premium is mostly buying: - time compression (200 h claim) - live debugging & personalized feedback - cohort peer group & accountability If you are already disciplined can build side projects"
X Link 2026-02-11T14:41Z [----] followers, [----] engagements

"@rauchg Yeah Id say use AI aggressively or maybe smartly/wisely but never let it become a full-time brain outsourcer. Stay aware"
X Link 2026-02-11T16:41Z [----] followers, [---] engagements

"@brave Maybe a better UX experience and more UI customization. I use [--] browsers mostly [--] along with Brave"
X Link 2026-02-11T17:56Z [----] followers, [---] engagements

"Just queue the email task right after creating the user record. Push it to Redis list or SQS or any simple queue you already run. Return [---] to the frontend instantly with check your inbox message. Worker picks it up later and sends. User never waits those [--] seconds flow remains fast. That is the standard move for this. https://twitter.com/i/web/status/2021723058650964041 https://twitter.com/i/web/status/2021723058650964041"
X Link 2026-02-11T23:08Z [----] followers, [----] engagements

"You're building a complex dashboard with 1000+ rows that update in real-time. What is your go-to combo right now - TanStack Table + Virtualizer - AG Grid (and pray the license fits) - Just react-window + custom everything - "I gave up and went full server components" Drop your stack & why #react #frontend"
X Link 2026-02-11T23:22Z [----] followers, [----] engagements

"Yeah exactly that is the mature architectural answer. FE should almost never be doing heavy aggregation / filtering / grouping over 10k100k+ raw rows in real-time. the great pattern now rn architecturally as you mentioned - - Backend / analytics DB (clickhouse pinot rockset starrocks duckdb+wasm in some newer cases or even TimescaleDB / QuestDB for time-series) pre-aggregates / rolls up the data - Returns compact materialized views / aggregated buckets (e.g. [--] min [--] min hourly depending on zoom level) - Frontend gets [--] kb json payloads instead of [--] to [--] MB for which can use TanStack Table +"
X Link 2026-02-12T01:21Z [----] followers, [---] engagements

"We built something similar for one of the client and honestly tier upgrades were the thing that kept causing problems. Token bucket in Redis with Lua scripts This combo handled around 100k requests per second for us without issues. Lua scripts let you check tokens and decrement in one atomic operation so you don't get race conditions. Tier upgrades have to happen instantly Someone upgrades their plan and they expect higher limits right away. Making them wait [--] minutes for cache to expire felt terrible. We ended up invalidating cache immediately whenever subscriptions changed. Adaptive"
X Link 2026-02-12T02:27Z [----] followers, [---] engagements

"I will rank all the four options by strongest to weakest in order. [--]. SDE [--] @ Uber: strongest overall pick for most strong engineers [--]. SDE [--] @ Atlassian: very close second if you want significantly better work-life balance [--]. EM @ VMware: reasonable only if you are already excited about people management and don't mind a slower technical trajectory [--]. VP @ Goldman Sachs: usually the weakest real choice for a core software engineer unless you genuinely want to pivot into finance / trading systems long-term https://twitter.com/i/web/status/2021790082328670467"
X Link 2026-02-12T03:34Z [----] followers, 11.6K engagements

"@naval American AI labs push open access and sharing tech widely. Yet the top open models right now are mostly from China: Kimi K2.5 DeepSeek V3.2 Qwen [--] GLM-4.7 sitting high on public leaderboards for reasoning coding math. The difference stands out"
X Link 2026-02-12T04:07Z [----] followers, [----] engagements

"Yeah this is the correct way. Upload file first give back [---] Accepted straight away. Then push the task to a queue or event. Worker picks it up does resize compress thumbnail updates status in redis or db. Frontend either polls the status endpoint every few seconds or gets push via websocket/socket. No blocking the http request for [--] seconds user sees upload done instantly progress shows later. Sync processing in api path kills response time and feels slow always. Async keeps it snappy. https://twitter.com/i/web/status/2021884046314467695 https://twitter.com/i/web/status/2021884046314467695"
X Link 2026-02-12T09:48Z [----] followers, [---] engagements

"Design user blocking at scale (Twitter/Instagram level). A user can be blocked by millions of people; blocked users shouldn't see their content or interactions. How do you enforce this efficiently across feeds search recommendations"
X Link 2026-02-12T11:09Z [----] followers, [----] engagements

"Most replies here says FE and they are partially correct AI handles UI components layouts and styling fast because the patterns repeat a lot and training data for JS/HTML/CSS is huge. Backend still needs more careful logic around data flow auth scaling; AI messes up there more often so people review heavier. Albeit when it comes to architectural things flow of the application tradeoff decisions and complex logic again AI fails on FE too. So FE wins on volume of use right now but neither side lets you fully trust AI on the hard stuff yet. https://twitter.com/i/web/status/2021934524670574797"
X Link 2026-02-12T13:08Z [----] followers, [----] engagements

"@RahulBagal__ love this stack how is clickhouse query perf when you are doing aggregations on 1000+ updating rows in real time"
X Link 2026-02-12T18:10Z [----] followers, [--] engagements

"Redis per-user block sets are fine for the average case most block [---]. But scale breaks when a high-follower account gets blocked by millions in that case fan-out cost on read becomes insane. Xs algo applies blocks/mutes super early in the pipeline (before heavy ranking) accurately to avoid per-request lookups at that volume. See their [----] open source write up on visibility filtering. https://twitter.com/i/web/status/2022011234212782503 https://twitter.com/i/web/status/2022011234212782503"
X Link 2026-02-12T18:13Z [----] followers, [--] engagements

"We ran into this puzzle at one of the product based companies and the honest answer is the mix really depends on the feature and scale. WebSockets for active chat If someone has the chat open and typing WebSockets make sense. Bidirectional so you can send typing indicators both ways. Connection stays alive as long as they're in the app. SSE for feed updates For things like notifications bell or activity feed SSE works fine. Server pushes updates to the client over regular HTTP. Way simpler than WebSockets when you only need one direction. Push notifications when app is closed If the app isn't"
X Link 2026-02-12T18:33Z [----] followers, [---] engagements

"@SoroushP4 Bloom filters are perfect for this tiny memory superfast checks and the tiny false positive risk is usually acceptable for block enforcement nice idea"
X Link 2026-02-12T19:07Z [----] followers, [--] engagements

"Uber loves throwing variants like minimum/maximum value that satisfies X condition where you binary search over the possible range instead of the array itself. Examples: aggessive cows book allocation ship packages within D days split array largest sum capacity to ship packages. https://twitter.com/i/web/status/2022207688566886838 https://twitter.com/i/web/status/2022207688566886838"
X Link 2026-02-13T07:14Z [----] followers, [----] engagements

"Imagine building the future at Google and then waking up to an email that basically says: [----] was great. Now its AI or the exit door." This isnt a thought experiment. Its happening. Google is offering voluntary exit packages to parts of its U.S. business teams. Not layoffs. Not officially. Theyre calling it a 'voluntary exit program.' Translation: 'You can leave. Well pay you.' Last year similar packages reportedly included: [--] weeks base pay + [--] extra week for every year of service So if you have been there [--] years Thats approx [--] weeks of pay. Not terrible. But heres whats interesting"
X Link 2026-02-13T09:46Z [----] followers, [---] engagements

"@0xlelouch_ ai is convenient story to tell instead of admitting growth slowing and costs biting focus stays same that build real skills sharpen fundamentals ans ignore the loud narratives"
X Link 2026-02-13T10:19Z [----] followers, [--] engagements

"You run a high-write counter system (views likes upvotes) that increments millions of times per minute. One day you realize a 64-bit unsigned int will overflow in 500+ years. Do you care What would make you add overflow protection anyway"
X Link 2026-02-13T10:25Z [----] followers, [----] engagements

"@0xlelouch_ Pick something real from Uber or Netflix pull out the key decisions and where they admitted things went wrong then build a small version yourself even if its just stubs and fake traffic. That one implementation teaches way more than saving twenty links you never revisit"
X Link 2026-02-13T12:33Z [----] followers, [---] engagements

"For devs the message is clear. Pick one area that actually moves the business number payments infra security pipelines whatever it is and get really sharp there. General skill still matters but owning one metric people can point to cuts through faster in interviews. Use AI to move quicker on the boring parts dont make it the whole identity. Debugging system design and handling live incidents remain human edges for now. Build some real runway if you can. Six to twelve months breathing room changes how you think about offers and moves. Markets tighten selectivity goes up fundamentals win again."
X Link 2026-02-13T14:26Z [----] followers, [---] engagements

"@CodeLune259 official flutter docs are the best starting point - for adv topics: net ninja flutter playlist on YT https://codelabs.developers.google.com/cat=Flutter https://docs.flutter.dev/ https://codelabs.developers.google.com/cat=Flutter https://docs.flutter.dev/"
X Link 2026-02-14T19:18Z [----] followers, [--] engagements

"@shivemnn yes without strong math you are just memorizing architectures not understanding why they work. id say if you are on more of ML side then maths is must if you are just building agentic workflows llm integrations and all those stuffs then you can skip maths"
X Link 2026-02-15T04:43Z [----] followers, [---] engagements

"@helderbuilds digital ocean clear win coz its way simpler & cheaper for early stage. aws will burn time and money until you have scale. switch to aws once you actually need the extra services"
X Link 2026-02-15T05:13Z [----] followers, [--] engagements

"No I dont care about overflow that [---] years away. At millions of increments per minute a uint64 still takes insane time to wrap. Way beyond any system lifetime we can imagine right now. I'd rather spend energy on code that is easy to read change and debug years later than add checks nobody will ever hit. Only thing that would push me to add protection is if the counter actually meant something critical past that point like money totals or irreversible IDs where wrap breaks logic hard. For plain metrics views/likes/upvotes Nope ignore it. https://twitter.com/i/web/status/2022716419079860371"
X Link 2026-02-14T16:55Z [----] followers, [--] engagements

"@ASolovichh thanks for the nudge lets keep it strict containers & DBs next time"
X Link 2026-02-15T19:19Z [----] followers, [--] engagements

"@VibeCoderOfek Yesss overlooked huge point. Token budgeting basically became the new scaling constraint"
X Link 2026-02-16T07:09Z [----] followers, [--] engagements

"This makes complete sense right now. Traditional full stack or app dev paths are packed already freshers struggle to break in without experience. But agent side still has room because not every senior engineer jumps on it fast. Starting with small POCs in RAG or multi-agent setups gives actual proof you can build something useful. Startups grab people who show they can ship agent stuff early. Later big tech will chase the same talent when they shift hiring by then you already have real work to show. This is the direction for anyone in college today."
X Link 2026-02-15T05:34Z [----] followers, [---] engagements

"Single load balancer going down means nothing works anymore. Put them across different AZs so one AZ failure doesn't destroy everything. AWS ELB already spreads nodes automatically no single box controls it. Add Route53 health checks on top if you want extra failover layer. That's the basic fix they expect in AWS interviews. https://twitter.com/i/web/status/2022991110579409196 https://twitter.com/i/web/status/2022991110579409196"
X Link 2026-02-15T11:07Z [----] followers, [----] engagements

"@MainakMukh47974 yes bandwidth congestion during big matches and the encoding step usually adds those extra [---] seconds. annoying but hard to avoid completely"
X Link 2026-02-15T14:28Z [----] followers, [---] engagements

"Popular JavaScript Frameworks / Frontend Libraries (20252026 trends) - React: United States - Vue: China (created by Evan You) - Angular: United States - Svelte: United States (New Zealand creator) - Next.js: United States - Nuxt: France - Astro: United States / Canada - Solid: United States AI / LLM-origin heavy hitters (publicly known base models 2025) - GPT series: United States - Llama series: United States - Claude: United States - Gemini: United States - Mistral: France - Grok: United States - DeepSeek: China - Qwen: AI / LLM-origin heavy hitters (publicly known base models 2025) - GPT"
X Link 2026-02-15T15:01Z [----] followers, [---] engagements

"Top [--] Frontend / Web Development Concepts Every Developer Should Know Foundations [--]. DOM vs Virtual DOM [--]. HTML Semantics & Accessibility (a11y) [--]. CSS Box Model & Flexbox/Grid [--]. Responsive Design & Media Queries [--]. Mobile-First Approach Rendering & Performance [--]. Critical Rendering Path [--]. Lazy Loading & Code Splitting [--]. Web Vitals (LCP FID/INP CLS) [--]. Tree Shaking & Bundling [--]. Image Optimization (WebP AVIF srcset) JavaScript & Reactivity [--]. Event Loop & Async (Promises/Async-Await) [--]. Closures & Scope [--]. Hooks vs Class Components [--]. State Management (Context vs Redux/Zustand) 15."
X Link 2026-02-16T10:16Z [----] followers, [----] engagements

"great now this can be done without any jailbreak. just one time mac setup and same wifi for both devices. it is slow now i was watching a demo the other day and its slow because of all the ui round trips but still pretty wild seeing the phone screen change from a chat message. Android version already there too. Might get useful once latency drops or it starts doing chained stuff like open app then find setting then toggle something deeper. https://twitter.com/i/web/status/2023435988325011881 https://twitter.com/i/web/status/2023435988325011881"
X Link 2026-02-16T16:35Z [----] followers, [---] engagements

"You are building real-time collaborative editing (Google Docs style) for 100k+ simultaneous users on the same document. OT vs CRDT - which one do you actually pick in 2025/2026 and why Walk through conflict resolution horror stories you have seen or expect"
X Link 2026-02-14T19:23Z [----] followers, [---] engagements

"we need to get smarter about this and bridge the gap instead of fearing it. soft skills system/architecture thinking infra/ cloud depth scaling agentic aistandardising ai protocols; these are next ai proof things until ai reaches that level the move is always pick the next thing faster than it picks is. imo as longs as we keep evolving nothing can potentially replace us. https://twitter.com/i/web/status/2022905646656716860 https://twitter.com/i/web/status/2022905646656716860"
X Link 2026-02-15T05:27Z [----] followers, [--] engagements

"As a frontend engineer Please master these fundamentals instead of chasing every new shiny library or framework every few months. Focus on going deep in - JavaScript and TypeScript core mechanics (event loop closures prototypes this keyword async patterns microtask queue) - Modern CSS (Flexbox and Grid mastery container queries cascade layers logical properties :has selector scroll-driven animations) - Responsive and adaptive design (mobile-first approach fluid typography with clamp smart breakpoints without media-query overload) - Browser rendering and performance (Critical Rendering Path"
X Link 2026-02-15T15:34Z [----] followers, 42.3K engagements

"Top [--] Backend / API Development Concepts Every Developer Should Know Foundations [--]. REST vs GraphQL vs gRPC [--]. HTTP Methods & Status Codes [--]. Authentication (JWT vs Sessions vs OAuth) [--]. Authorization (RBAC vs ABAC) [--]. API Versioning Data & Persistence [--]. ORM vs Raw SQL [--]. Migrations & Schema Evolution [--]. Transactions (ACID) [--]. Connection Pooling [--]. N+1 Problem & Eager/Lazy Loading Reliability & Security [--]. Input Validation & Sanitization [--]. Rate Limiting & Throttling [--]. CORS & CSRF Protection [--]. Error Handling & Logging [--]. OWASP Top [--] Scaling & Performance [--]. Background Jobs /"
X Link 2026-02-15T18:54Z [----] followers, [----] engagements

"cdns are basically caching proxies placed all over the world. edge node nearest to the user gets the request. if the file is already cached from an earlier pull it serves right away super fast. if miss it fetches from your origin once caches it using ttl from cache-control headers then serves to everyone else. quick setup steps upload static files to s3 or your own server point the cdn at that origin bucket or domain change dns cname to point to the cdn hostname add cache-control max-age long with immutable for versioned files like js css with hashes when you update files either purge the url"
X Link 2026-02-16T11:19Z [----] followers, [---] engagements

"Backend engineers in [----] - be honest how many do you regularly touch / understand well [--]. Connection pooling & tuning [--]. Prepared statements vs ORM pitfalls [--]. N+1 query problem & solutions [--]. Database transaction isolation levels [--]. Message queue dead-letter & poison-pill handling [--]. Circuit breaker + fallback in code [--]. Prometheus metrics + useful histograms [--]. Structured logging (and why println is a liability) [--]. JWT vs session cookies in SPA + API [--]. Lazy vs eager loading (and when it goes wrong) Top [--] Frontend / Web Development Concepts Every Developer Should Know Foundations [--]. DOM"
X Link 2026-02-16T16:18Z [----] followers, [----] engagements

"Databases and what they are good for: [--]. PostgreSQL: serious relational work constraints complex queries. [--]. MySQL: simple web apps widespread hosting predictable. [--]. SQLite: local storage embedded apps zero setup. [--]. MongoDB: flexible schema JSON-style documents. [--]. Redis: caching sessions rate limiting fast lookups. [--]. Cassandra: massive scale write-heavy workloads. [--]. DynamoDB: serverless scale managed by AWS. [--]. CockroachDB: distributed SQL horizontal scaling. [--]. Supabase: Postgres + auth + storage quick backend layer. [--]. Firebase Firestore: real-time apps frontend-heavy builds. 11."
X Link 2026-02-16T16:28Z [----] followers, [----] engagements

"Ever wonder why youtube video caps at 10k views but the same clip blows up to 1M on Insta Reels 🤯 YouTube's secret: approx 30s watch time MINIMUM to count a 'view' IG Reels Plays for approx 3s +1 view. Loops it 5x Jackpot. Easy mode. As a dev building my portfolio site: Id skip the 30s logic for sure. Unique visitor triggers add +1 view. Honest reach no artificial filters. How will you implement view logic be for a personal portfolio (Both at high level and low level)"
X Link 2026-02-16T17:08Z [----] followers, [---] engagements

"The only AI/ML concepts you need to know (practical 2026) LLM basics Tokens Context window Temperature / Top-p Prompt engineering Chain-of-thought Few-shot Role prompting RAG Embeddings Vector DBs (Pinecone / PGVector) Retrieval + generation Fine-tuning LoRA / QLoRA PEFT methods Agents Tools ReAct loop Memory Workflows vs Chains Evaluation BLEU/ROUGE vs LLM-as-judge Human eval basics Inference optimization Quantization (4-bit/8-bit) vLLM / TensorRT-LLM Hallucination fixes Grounding Self-consistency Retrieval checks Deployment API endpoints Auto-scaling Monitoring (drift latency) SLM vs LLM"
X Link 2026-02-08T19:00Z [----] followers, 82.1K engagements

"Interviewed an Al engineer candidate last week with [--] years in ML for my friend's startup. Couldn't explain transformer architecture properly. Didn't know about RAG pipelines. Never worked with vector databases. But gave him a prompt engineering problem - his systematic approach to context optimisation and error handling was on point. Hired him. You can learn tools and frameworks. You can't easily teach logical thinking and problem-solving methodology. https://twitter.com/i/web/status/2020578242185638087 https://twitter.com/i/web/status/2020578242185638087"
X Link 2026-02-08T19:19Z [----] followers, 147.4K engagements

"Infosys fresher / early level still gets around 4-10 lakhs depending on band the [---] lpa looks like an entry package from couple years back but not far off for support kind of role. Amazon SDE [--] usually gets 23-30 lakhs total (closer to [--] like mentioned) with oncall and design work matching. Razorpay backend at [--] lpa fits mid level fintech pay there. Uber engineer [--] around [--] to 80+ lpa with rsus is normal for that level scaling apis and p99 stuff is standard. US remote startup at 85k usd converts roughly to same as uber or bit more after tax but full ownership & hiring involvement pushes"
X Link 2026-02-12T13:05Z [----] followers, 34.3K engagements

"As an AI/ML engineer. Please learn: - Math & theory foundations (linear algebra probability & statistics optimization information theory) - Deep learning architectures (Transformers diffusion models CNNs / ViTs RNNs/LSTMs/GRUs mixture-of-experts) - Training & scaling laws (pre-training fine-tuning PEFT / LoRA / QLoRA RLHF / DPO / PPO distributed training: DDP / FSDP / DeepSpeed / Megatron) - Data handling at scale (data pipelines cleaning & deduplication tokenization strategies synthetic data multimodal datasets) - Evaluation & benchmarking (automatic metrics: BLEU/ROUGE/BERTScore/MMLU human"
X Link 2026-02-14T13:24Z [----] followers, 135.6K engagements

"Kafka catches every comment and emoji at the edge split by match and user country so load spreads out. Flink runs fast spam checks and rate limits before stuff even hits the main database. For sending feeds out: Redis pub sub per region plus write time fan out to each user sorted set. That way every viewer pulls their stream super quick. Sentiment part runs a small distilled model something like MobileBERT size right on edge nodes near the big broadcast zones. Gets inference done really fast then pushes the score back through the same Redis channel. Main tradeoff: edge speed is great but the"
X Link 2026-02-14T13:30Z [----] followers, [---] engagements

"Cart data remains in server memory. Next request goes to another server cart gone. Real fix is simple. Make servers stateless. Put cart in Redis (or DB if needed). Cookie holds only session ID. Every server pulls the same cart using that ID. Sticky sessions look easy but create single points of failure and uneven load. Avoid them in production. This is how scalable e-commerce actually runs. https://twitter.com/i/web/status/2022690562449764743 https://twitter.com/i/web/status/2022690562449764743"
X Link 2026-02-14T15:13Z [----] followers, [---] engagements

"25 frameworks and what they are good for: [--]. React: dynamic UIs component thinking frontend default choice. [--]. Next.js: React with structure SSR SEO production-ready apps. [--]. Vue: simple mental model progressive adoption clean templates. [--]. Nuxt: Vue with SSR and routing handled properly. [--]. Angular: opinionated frontend enterprise teams everything included. [--]. Svelte: minimal runtime small bundles surprisingly smooth DX. [--]. SvelteKit: fullstack Svelte lightweight but capable. [--]. Express: minimal Node backend you wire everything yourself. [--]. Fastify: Express mindset but faster and stricter."
X Link 2026-02-14T16:12Z [----] followers, [----] engagements

"DevOps tools and what they are good for: [--]. Docker: containerizing apps consistent environments. [--]. Kubernetes: container orchestration scaling clusters. [--]. Terraform: infrastructure as code cloud provisioning. [--]. Ansible: configuration management agentless automation. [--]. GitHub Actions: CI/CD directly inside your repo. [--]. GitLab CI: integrated pipelines with repo control. [--]. Jenkins: customizable CI older setups still rely on it. [--]. Prometheus: metrics collection system monitoring. [--]. Grafana: dashboards visualizing metrics. [--]. Nginx: reverse proxy load balancing. [--]. Apache: traditional"
X Link 2026-02-14T16:21Z [----] followers, [----] engagements

"This approach works really well at scale. Storing blocks in something durable like Cassandra or DynamoDB & Redis cache for fast checks is standard. Kafka for async propagation to other systems prevents blocking the write path. For new posts skipping fanout to blocked/blocking users saves a ton of useless work on storage and compute. For older posts the runtime check during render/filter is the only accurate way since you can't rewrite history feeds retroactively. Many big platforms do exactly this combo. https://twitter.com/i/web/status/2022713080569040916"
X Link 2026-02-14T16:42Z [----] followers, [--] engagements

"Cloud platforms and what they are good for: [--]. AWS: everything you can think of deep ecosystem. [--]. Google Cloud: data ML strong infra. [--]. Microsoft Azure: enterprise integration Microsoft stack. [--]. DigitalOcean: simple droplets developer-friendly. [--]. Linode: affordable VPS straightforward setup. [--]. Render: easy app hosting less DevOps overhead. [--]. Railway: quick backend deployment simple configs. [--]. deploy close to users edge-friendly. [--]. Heroku: easy PaaS less control but fast start. [--]. Oracle Cloud: cost-effective compute options. http://Fly.io http://Fly.io"
X Link 2026-02-14T19:45Z [----] followers, [----] engagements

"AI / ML Development Project Ideas - Simple Linear Regression House Price Predictor - MNIST Handwritten Digit Classifier - Sentiment Analysis on Movie Reviews or Tweets - Spam Ham Email or Message Classifier - Image Classifier Cats vs Dogs or Flowers - Customer Churn Prediction Telco or Bank dataset - Movie Product Recommendation System Collaborative Filtering - Time Series Forecasting Stock price Weather Sales - Face Detection plus Landmark Detection pipeline - Text Summarization Extractive or Abstractive with transformers - RAG-based QandA over your own PDFs or documents - Fine-tune small"
X Link 2026-02-15T07:01Z [----] followers, 23.3K engagements

"AI / LLM-origin heavy hitters (publicly known base models 2025) - GPT series: United States - Llama series: United States - Claude: United States - Gemini: United States - Mistral: France - Grok: United States - DeepSeek: China - Qwen: China - Gemma: United States France and China are the clearest non-US challengers right now. Feel free to add more to the list. Programming Languages and their Country of Origin C - United States C++ - Denmark Java - Canada Python - Netherlands JavaScript - United States Go - Switzerland / Canada / United States Rust - Canada TypeScript - Denmark Programming"
X Link 2026-02-15T07:39Z [----] followers, [----] engagements

"Frontend rendering & asset loading usually takes way more time than the API call. Backend [---] ms seems good but browser still waits on JS parse style calc layout paint. Users feel the full chain not only server response. Measure with devtools network and performance tab or lighthouse instead of trusting API logs alone. That shows the real story. https://twitter.com/i/web/status/2022941258444902888 https://twitter.com/i/web/status/2022941258444902888"
X Link 2026-02-15T07:49Z [----] followers, [---] engagements

"Have you ever noticed lag during live-streamed matches even when your internet connection is stable and fast As an engineer can you explain the possible reasons behind this lag"
X Link 2026-02-15T14:01Z [----] followers, [----] engagements

"API Gateway with BFF pattern works best here. Client hits one endpoint only. Server side the gateway calls those [--] services in parallel combines everything and sends back single response. This removes the mess from frontend code. Latency improves because parallel work happens closer to services. Bandwidth usage also comes down a lot especially on mobile. If the page data shape changes often then GraphQL over the BFF gives more control without new endpoints every time. Main idea remains same; move the complexity away from client. Keep frontend simple and quick"
X Link 2026-02-15T14:07Z [----] followers, [----] engagements

"@avrldotdev yes bandwidth congestion is the issue during peak matches plus the encoding step itself adds those 5-15 seconds delay. hard to remove completely without sacrificing quality. annoying but thats the tradeoff right now"
X Link 2026-02-15T15:39Z [----] followers, [---] engagements

"Big live streams buffer constantly and honestly your internet is probably fine. CDN propagation delays Live streams go through CDNs with edge servers worldwide. Your stream comes from the nearest edge. If that edge is slow to get updates from origin you lag behind. Some viewers closer to origin are ahead of you. Buffering for stability Streaming apps buffer [--] to [--] seconds of video to handle network jitter. Your connection might drop packets for half a second. Buffer covers that gap so playback remains smooth. But this buffer adds delay compared to actual live. Encoding and transcoding time"
X Link 2026-02-15T20:28Z [----] followers, [---] engagements

"How many of these are you actually using / could teach to a junior in [----] [--]. gRPC vs REST vs GraphQL trade-offs [--]. OpenTelemetry (full end-to-end tracing) [--]. AsyncAPI / Schema Registry [--]. Database-per-service vs shared DB in microservices [--]. Rate Limiting (token bucket vs leaky bucket) [--]. Webhook retry & dead-letter queue design [--]. Feature Flags at scale [--]. Polyglot Persistence (when & why) [--]. GRPC deadlines + cancellation propagation [--]. Request coalescing / hedging As a Backend dev how many concepts can you explain from below : [--]. Event-Driven Architecture [--]. Saga Pattern [--]. CQRS (Command"
X Link 2026-02-16T07:37Z [----] followers, [----] engagements

"We didn't build Google Docs scale but we did real-time collab editing for a smaller product and honestly CRDTs won for us. Operational Transform is theoretically correct but painful OT works great in papers but implementing it correctly is really hard. You need a central server to order operations. Every operation transforms against concurrent ones. If you miss one edge case then you get document corruption. CRDTs let you go serverless on conflict resolution With CRDTs like Yjs or Automerge each client can apply changes locally and they converge automatically. No central authority needed to"
X Link 2026-02-16T17:16Z [----] followers, [---] engagements

Limited data mode. Full metrics available with subscription: lunarcrush.com/pricing