People think robotics is 90% building cool hardware.
Reality: It’s 90% watching your robot fall over 10,000 times in Isaac Sim over the weekend, praying the Reinforcement Learning policy converges before Monday🤖
Simply put, we will be an American Colony.
US will have tariff of 18% on our goods and we will charge 0% for their goods.
Resign and get lost @narendramodi
#hiring interns
RTX is hiring interns
Role - Software Engineering
Experience - Freshers
Location - India
- Basic Qualifications:
BTech degree in EEE, ECE or CS
- skills in Matlab, Simulink, Python, C/C++
Let us know if you are Interested 👇
#hiring#Remote
Trao is hiring for Software Engineer
Experience - Freshers
Location - Remote India
Requirement
- Build and ship production-grade MERN systems
- skills : MERN stack, AI / Agents
Let us know if you are Interested 👇
For people who keep asking what to build in AI Engineering
> Build your own Reasoner (Chain of Thought implementation)
> Build your own Agent loop (ReAct pattern)
> Build your own Inference Server (in C++/Rust)
> Build your own Transformer from scratch (Attention is all you need)
> Build your own Vector Database (HNSW index)
> Build your own RAG pipeline
> Build your own Flash Attention kernel (CUDA)
> Build your own Quantization library (Int8/FP4 implementation)
> Build your own Mixture of Experts (MoE) routing layer
> Build your own Distributed training loop (FSDP/Tensor Parallelism)
> Build your own KV Cache paging system (like vLLM)
> Build your own Speculative Decoding system
> Build your own State Space Model (Mamba implementation)
> Build your own RLHF pipeline (PPO implementation)
> Build your own Small Language Model (SLM)
> Build your own Matrix Multiplication kernel
> Build your own LoRA (Low-Rank Adaptation) trainer
> Build your own Code interpreter sandbox
> Build your own DPO (Direct Preference Optimization) loss function
> Build your own Graph RAG system
> Build your own Model merger (Model Soups/Spherical Linear Interpolation)
> Build your own Interpretability tool (SAE - Sparse Autoencoders)
> Build your own Synthetic data generator
> Build your own Function Calling router
> Build your own Structured Output parser (Context Free Grammars)
> Build your own Multi-modal projector (CLIP implementation)
> Build your own LLM Eval harness
> Build your own Guardrails system (Input/Output filtering)
> Build your own Prompt caching mechanism
> Build your own Tokenizer (BPE implementation)
> Build your own Autograd engine (like Micrograd)
> Build your own Diffusion model (UNet + Scheduler)
> Build your own Vision Transformer (ViT)
> Build your own Whisper-style ASR model
> Build your own Text-to-Speech pipeline
> Build your own Semantic Router
> Build your own Knowledge Graph builder
> Build your own Data curation pipeline (MinHash/Deduplication)
> Build your own AI Gateway (Load balancing/Failover)
> Build your own Parameter Efficient Fine-Tuning (PEFT) library
> Build your own Text-to-SQL engine
> Build your own Recommendation system (Two-tower architecture)
> Build your own Embedding model
> Build your own Logit Processor
> Build your own Softmax kernel optimization
> Build your own Adversarial attack generator
> Build your own Audio Spectrogram transformer
> Build your own Neural Architecture Search
> Build your own Model Distillation pipeline
> Build your own Feature Store
> Build your own Database driver (for Vectors)
Your biggest career risk isn't learning the wrong framework. It's becoming too comfortable.
Comfort is the enemy of growth in tech.
It's easy to master one stack, one workflow, one way of thinking. But the moment you stop feeling slightly out of your depth, you start stagnating.
Growth happens at the edge of your comfort zone:
- Volunteering for the project that uses a technology you don't know.
- Pairing with the engineer you find most intimidating.
- Presenting your work, even if public speaking terrifies you.
- Spending a weekend building with a completely new paradigm (like Rust after years of Python).
You don't need to master every new trend. But you do need to cultivate a habit of curiosity and intentional discomfort.
The most successful engineers I know aren't the ones who know everything; they're the ones who are best at learning something new.
What's one thing you're doing this month to step outside your comfort zone?
The next evolution of full-stack development won't just be about connecting a frontend to a database. It will be about connecting a frontend to an AI agent that can reason, use tools, and interact with that database on its own. Exciting times ahead. #FullStack#AI
My plans for Sunday:
1. Organize my project backlog.
2. Learn a new technology.
3. Start a new side project.
What I'll actually do:
1. Stare at my project backlog.
2. Open 20 tabs about the new technology.
3. Take a nap.
The pure joy of spending a Saturday afternoon getting your local development environment perfectly configured. Clean aliases, new plugins, everything just right. It's the digital equivalent of tidying your workshop.
That end-of-week feeling when you finally understand a concept you've been struggling with. The brain just feels... bigger. A great way to start the weekend. #AlwaysLearning#Developer
The mental whiplash of switching from a Python backend to a TypeScript frontend to a SQL database query all before lunch is a unique kind of challenge. Context switching is the real final boss. #FullStack#Developer
What's the one programming book that genuinely changed the way you think about code? Mine is "Designing Data-Intensive Applications" by Martin Kleppmann.
Your side projects are more important than your resume.
A resume is a list of claims. A side project is proof.
When I review candidates, a well-documented side project on GitHub tells me more than any bullet point ever could. It shows:
Passion & Initiative: You love this craft enough to build things in your own time. You don't wait for a ticket to be assigned.
End-to-End Thinking: You've handled everything from the initial idea to the database schema, the API design, and the deployment. You've seen the whole picture.
Real-World Problem Solving: You've hit real bugs, made real architectural decisions, and shipped something real. This experience is invaluable.
Your resume says you know React. Your portfolio project shows me you can build, deploy, and maintain a React application.
Don't just tell me what you can do. Show me.
What's the most valuable lesson a side project has ever taught you?
Browser DevTools Tip: Right-click on any network request in the "Network" tab and select "Copy as cURL". You can instantly paste a perfectly formatted cURL command into your terminal to replicate the exact request. Incredibly useful for debugging APIs. #WebDev#DevTools