Liminal✨ (@quitvoid0) header
Liminal✨ (@quitvoid0) profile picture

Somewhere between stardust and the unknown. ✨

Joined July 2024
Photo by Liminal✨ (@quitvoid0)Photo by Liminal✨ (@quitvoid0)Photo by Liminal✨ (@quitvoid0)Photo by Liminal✨ (@quitvoid0)Photo by Liminal✨ (@quitvoid0)Photo by Liminal✨ (@quitvoid0)Photo by Liminal✨ (@quitvoid0)Photo by Liminal✨ (@quitvoid0)
Liminal✨ retweeted
Two founders in Gujarat building websites, apps and AI automation. And two free products: 🧾 CrizaVoise, offline billing: voise.criza.dev 🛠️ CrizaTools, 27 browser tools: criza.web.id More: criza.dev
4
2
2
23
Liminal✨ retweeted
Something new is brewing 👀 Check it out 👉 criza.dev
1
3
58
Liminal✨ retweeted
100 Wallpapers for your Home Screen setups 🫵🏼 Repost for good karma 😇 1-4: Best
29
89
2
650
41,278
Liminal✨ retweeted
Replying to @OwaisBatti
Curiosity is the constant. Keep building and exploring! 🚀
1
4
53
Liminal✨ retweeted
Starlink vs the Indian telecom landscape. Musk questions Ambani, Rahul Gandhi hints at “the other guy,” and Jio’s mega IPO is approaching. Coincidence or just business? What do you think connects these dots?
1
2
29
Liminal✨ retweeted
Every app looks simple until you see the system hiding behind the screen.
1
3
42
Liminal✨ retweeted
Starlink India: My price prediction 🇮🇳 ₹2,500–₹3,500/month + hardware. Reports suggest this range, but official pricing remains unconfirmed. JioFiber starts at ₹399/month + GST. Will Starlink prioritise affordability or remote connectivity? #starlink #elonmusk #jio #india
1
2
36
Liminal✨ retweeted
Replying to @malagojr
Yep it always works but not a good idea.
1
5
9,601
Liminal✨ retweeted
AI is evolving from answering questions to executing entire workflows. The next breakthrough? Agents that build, test, and improve other agents. We're not just automating tasks anymore. We're automating intelligence. #AI #AIAgents #MachineLearning
1
2
29
Liminal✨ retweeted
Replying to @SinghAILabs
AI, CLAUDE
1
2
19
Liminal✨ retweeted
Replying to @elonmusk
Funny to see now who's controlling what
1
2
43
Liminal✨ retweeted
Don't even think about going for a Backend Interview if you are not clear about these 5 concepts: 1. Event-Driven Architecture - Services talk via events. 2. Observability - Logs + metrics + traces 3. Circuit Breaker - Fail fast, protect your system. 4. Sharding - Split large datasets across nodes. 5. Rate Limiting (Token Bucket) - Protect APIs under load.
11
64
1
713
39,151
From my college experience, these are the topics commonly asked to freshers during campus placements: Software Developer Engineer Role : *3-6LPA >DSA (Easy - Medium)-(Basic Array and Strings) >SQL Queries (Basic Where, Having Clause) >Project (Basics - In depth) >Cloud Computing (Basics) >Networking(Basics) >OOPs (Mandatory) >Resume based >Mostly 1 Technical round. *7-10LPA >DSA (Medium-Hard) >SQL Queries (Joins) >Project (In depth) >Cloud Computing (Situational Questions) >Networking(Some times In depth) >OOPs (Mandatory) >Resume Based >Mostly 1 but sometimes 2 Technical rounds. *11-15LPA >DSA (Hard) >Problem Solving >SQL Queries (Joins, Sub Queries) >Project (In depth, Situational Questions) >Cloud Computing (Situational Questions) >Networking(Some times In depth) >OOPs (Mandatory) >Resume Based >More than 1 technical round.
16
48
1
577
47,188
Liminal✨ retweeted
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.
99
466
32
3,284
258,146
Liminal✨ retweeted
gemini 3 for frontend opus 4.5 for backend there you go, a fullstack engineer
233
614
54
11,298
434,117
Liminal✨ retweeted
I DON’T UNDERSTAND WHY PEOPLE DON’T USE CHATGPT FOR JOB SEARCHES. I got 5 interview calls in 7 days, all with ChatGPT as my recruiter. Here are 6 prompts that turn your job hunt into a strategy. [Save this thread]
82
1,627
33
19,249
3,848,715
100 wallpapers for your home screen setups 👇🏽 Follow this thread 🧵 : 1-4
13
46
2
460
119,361