2-bit Gemma 4 12B GGUF, only 4.66 GB on disk, managed to cite 15 sites from a single prompt.
Try this locally on >6GB RAM via Unsloth Studio.
GitHub: https://t.co/aZWYAtakBP
We love seeing what you build with Gemma! ๐
Like this incredible community project that helps you fine-tune Gemma 4 with audio, text, and images on Apple silicon. ๐งต๐
Everyone is sleeping on this new OCR model!
- 85.9% (sota) on olmocr bench
- 90+ language support w/benchmarks
- 4B model (down from 9B)
- Full layout information
- Extracts + captions images and diagrams
- Strong handwriting, math, form, table support
100% open-source.
๐จ BREAKING: Someone just made 70B parameter models run on a single 4GB GPU.
It's called AirLLM. No quantization. No distillation. No pruning. Just raw 70B inference on hardware that costs less than a dinner.
You can even run Llama 3.1 405B on 8GB VRAM.
Here's how it works:
โ Decomposes the model layer-by-layer
โ Loads only one layer into GPU memory at a time
โ Runs inference, moves to the next layer
โ Prefetches the next layer while computing the current one
โ Supports 4-bit and 8-bit compression for 3x speed boost
No cloud API. No $10K GPU. Just pip install airllm and go.
Here's the wildest part:
It supports almost every major model โ Llama, Qwen, Mistral, ChatGLM, Baichuan, InternLM โ and it auto-detects the model type. One line of code to load. One line to generate.
Works on Linux, macOS (Apple Silicon), and even Google Colab free tier.
Your old gaming laptop can now run the same models that needed an A100.
100% Open Source. Apache 2.0 License.
๐๐๐ถ๐น๐ฑ ๐ง๐ต๐ถ๐ ๐๐ป๐ฑ-๐๐ผ-๐๐ป๐ฑ ๐๐ช๐ฆ ๐๐ฒ๐๐ข๐ฝ๐ ๐ฃ๐ฟ๐ผ๐ท๐ฒ๐ฐ๐ (๐ฅ๐ฒ๐ฎ๐น ๐ฃ๐ฟ๐ผ๐ฑ๐๐ฐ๐๐ถ๐ผ๐ป ๐๐ ๐ฝ๐ผ๐๐๐ฟ๐ฒ)
You will learn more by building one hands-on project from scratch than by watching 10 YouTube tutorials.
Project Description: An OpenTelemetry-based E-commerce microservices app deployed on AWS with full CI/CD + GitOps.
๐ข Project Architecture (Industry Style)
User
โ Domain (GoDaddy)
โ Route53
โ Load Balancer
โ EKS
โ Kubernetes Services
โ 20+ Microservices
If you build this once interviews become easy.
๐ข Step 1: Infrastructure as Code (Terraform)
Use Terraform to provision everything.
What you will implement:
โ VPC (public + private subnets)
โ Internet Gateway
โ Route Tables
โ NAT Gateway
โ Security Groups
โ EKS Cluster using Amazon EKS
โ S3 backend for remote state
โ DynamoDB for state locking
๐ What you will learn:
- Real VPC networking design
- How production EKS clusters are created
- Remote state management best practices
- Terraform backend configuration
- State locking (why it matters in teams)
- This alone gives you real DevOps exposure.
๐ข Step 2: CI/CD with GitHub Actions
Use GitHub Actions
Pipeline Stages You Should Create:
๐น Build
- Checkout code
- Setup Go
- Install dependencies
- Run unit tests
๐น Code Quality
- Integrate golangci-lint
- Perform static analysis
๐น Docker
- Build images
- Push to Docker Hub
๐น Update Kubernetes Manifests
- Auto-update image tag
- Commit back to repo
๐ What you will learn:
- Automated CI pipelines
- Docker image tagging strategy
- Version control in pipelines
- Secure secret handling
- Production-grade workflow design
This is exactly what companies expect.
๐ข Step 3: Containerization
Use Docker
What you will implement:
- Containerize 20+ microservices
- Multi-stage Docker builds
- Lightweight production images
- docker-compose for local testing
๐ What you will learn:
- Microservice packaging
- Build optimization
- Local vs production environment differences
- Dependency management
๐ข Step 4: Kubernetes on AWS
Deploy everything on Kubernetes using Amazon EKS
What you will implement:
โ Deployments
โ Services (ClusterIP, LoadBalancer)
โ Ingress
โ Service Accounts (IAM roles for service accounts โ IRSA)
โ Resource limits & requests
๐ What you will learn:
- Pod scheduling
- Service-to-service communication
- Ingress + ALB integration
- Secure workload identity
- Real cluster debugging
- This is real production experience.
๐ข Step 5: GitOps with ArgoCD
Use Argo CD
What you will implement:
- Connect GitHub repo to EKS
- Enable auto-sync
- Maintain desired state = actual state
๐ What you will learn:
- GitOps workflow
- Declarative deployments
- Drift detection
- Production-grade release strategy
- Modern companies are moving toward GitOps.
๐ขStep 6: Domain + Traffic Routing
Use:
- Amazon Route 53
- GoDaddy domain
Flow:
User
โ Route53
โ AWS Load Balancer
โ Ingress
โ Service
โ Pod
๐ What you will learn:
- DNS configuration
- Hosted zones
- A records / CNAME
- Real internet traffic routing
Now your project becomes public and production-like.
๐ฏFinal Outcome
If you build this project fully: You will understand:
โ Networking
โ CI/CD
โ GitOps
โ Kubernetes
โ IAM & Security
โ Terraform Backend
โ Production troubleshooting
โ Real DevOps workflow
I have documented everything in my GitHub repository.
You can follow it step by step, and if you get stuck, feel free to take help from ChatGPT but make sure you truly understand the concepts.
๐ ๐ฎ๐ถ๐ป ๐ฃ๐ฟ๐ผ๐ท๐ฒ๐ฐ๐ ๐ฅ๐ฒ๐ฝ๐ผ: https://t.co/HoGVLDDXlN
๐ง๐ฒ๐ฟ๐ฟ๐ฎ๐ณ๐ผ๐ฟ๐บ ๐ฅ๐ฒ๐ฝ๐ผ: https://t.co/VffpUPOyUn
If you found this helpful, feel free to like, retweet, and share it with aspiring DevOps engineers.
Signing off
@devops_nk ๐ซก
Backend Development Project Ideas
Beginner Level
โข Authentication API
โข CRUD API For Users
โข Blog Backend
โข URL Shortener
Intermediate Level
โข Pagination and Search API
โข File Upload API
โข Rate Limiter API
โข Muti User chat Application
Advanced Level
โข Multi role user System
โข O Auth2 Login API
โข Job Queue System
โข Recommendation System
Expert Level
โข Video Steaming Service
โข High Performance API With Caching
โข Distributed File Storage System
The Top AI Papers of the Week (February 2-8)
- A-RAG
- InfMem
- xMemory
- TinyLoRA
- OpenScholar
- Agent Primitives
- Heterogeneous Computing for AI Agent Inference
- Semi-Autonomous Mathematics Discovery with Gemini
Read on for more:
As a backend engineer.
focus on mastering:
- 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..
and go deep.
stop hopping between languages every few months.
Fusion of ๐ฅ๐๐ (Retrieval Augmented Generation) and ๐๐๐ (Cache Augmented Generation). How can you benefit from it as AI Engineer?
Letโs see what it looks like and what additional considerations should be taken into account.
Here are example steps to implement CAG + RAG architecture:
๐๐ข๐ต๐ข ๐๐ณ๐ฆ๐ฑ๐ณ๐ฐ๐ค๐ฆ๐ด๐ด๐ช๐ฏ๐จ:
๐ญ. We use only rarely changing data sources for Cache Augmented Generation. On top of the requirement of data changing rarely we should also think about which of the sources are often hit by relevant queries. Once we have this information, only then we pre-compute all of this selected data into a KV Cache of the LLM. Cache it in memory. This only needs to be done once, the following steps can be run multiple times without recomputing the initial cache.
๐ฎ. For RAG, if necessary, precompute and store vector embeddings in a compatible database to be searched later in step 4. Sometimes simpler data types are enough for RAG, a regular database might suffice.
๐๐ถ๐ฆ๐ณ๐บ ๐๐ข๐ต๐ฉ:
We can now utilise the preprocessed data.
๐ฏ. Compose a prompt including user query and the system prompt with instructions on how cached context and retrieved external context should be used by the LLM.
๐ฐ. Embed a user query to be used for semantic search via vector DBs and query the context store to retrieve relevant data. If semantic search is not required, query other sources, like real time databases or web.
๐ฑ. Enrich the final prompt with external context retrieved in step 4.
๐ฒ. Return the final answer to the user.
๐๐ฐ๐ฎ๐ฆ ๐๐ฐ๐ฏ๐ด๐ช๐ฅ๐ฆ๐ณ๐ข๐ต๐ช๐ฐ๐ฏ๐ด:
โก๏ธ Context window is not infinite and even while some models boast enormous context window sizes, the needle in the haystack problem has not yet been solved so use available context wisely and cache only the data you really need.
โ For some business cases, specific datasets are extremely valuable to be passed to the model as cache. Think about an assistant that has to always comply with a lengthy set of internal rules stored in multiple documents.
โ While CAG has been popularised for Open Source just recently, it is already viable for some time via Prompt Caching features in OpenAI and Anthropic APIs. It is really easy to start prototyping there.
โ You should always separate hot and cold data sources, only use cold (data that changes rarely) in your cache, otherwise the data will go stale and the application will go out of sync.
โ Be very careful about what you cache as the data will be available for all users to query.
โ It is very hard to ensure RBAC for cached data unless you have a separate model with its own cache per role.
Have you used the combination already?
Claude Code now supports the --from-pr flag
Resume any session linked to a GitHub PR by number, URL, or pick interactively. Sessions auto-link when a PR is created!
5 AI projects that will get you hired in 2026:
save & retweet it.โค๏ธ
1. RAG from Scratch
GitHub: https://t.co/HaJrX0COwN
2. Al Social Media Agent
GitHub: https://t.co/1BXYaxZTN2
3. Medical Image Analysis
GitHub: https://t.co/MqYgVxHisZ
4. MCP Tool-Calling Agents
Notebook: https://t.co/pA3bMHABjH
5. Al Assistant with Memory
GitHub: https://t.co/LoC4mtW5M0