yoshitha

3 posts

yoshitha

yoshitha

@yoshitha_dev

Katılım Ocak 2026
40 Takip Edilen1 Takipçiler
yoshitha
yoshitha@yoshitha_dev·
@system_monarch Almost 2 years into my career and starting to feel stuck. Most of my work is tool-based, with frequent context switching and limited development exposure. I want to transition into Java backend roles and focus on real engineering work. Would appreciate any advice
English
1
0
0
153
Puneet Patwari
Puneet Patwari@system_monarch·
Need some honest opinions from people who have seen both colleges closely. Which would you choose today for CSE and why? MIT Manipal main campus or VIT Vellore main campus CSE in Category 4? Thanks 🙏
English
7
0
12
3K
Aastha
Aastha@aastha_mhaske·
🚀 𝗝𝗮𝘃𝗮 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 A Practical Guide to Interview Preparation Master the core concepts you need to crack your next backend or microservices interview! ✅ Spring Boot & REST APIs ✅ Service Discovery & Load Balancing ✅ Docker, Kubernetes & CI/CD ✅ Real-world Interview Q&A 📘 FREE for the first 500 people! 1️⃣ Like & Repost 2️⃣ Comment “JAVA” 3️⃣ Follow (so I can DM you the guide) Level up your backend interview prep today! 💻 #Java #Microservices #BackendDevelopment #InterviewPrep #SpringBoot #Giveaway #Developers #Coding
Aastha tweet mediaAastha tweet media
English
172
136
496
27.6K
yoshitha retweetledi
Ishan
Ishan@ishanxtwt·
The biggest lie in coding: "You need to master JavaScript before learning React" If you follow this advice, you will be stuck in "Tutorial Hell" for 6 months You will spend weeks learning about prototypes, var hoisting, and the this keyword context But here is the brutal truth: I run a Web Dev Agency and when I build a SaaS in Next.js, I use maybe 15% of the JavaScript language The rest? It’s legacy bloat from 2010 To be a top-tier React Developer, you don't need to be a "JS Wizard" You need to be a master of ES6+ Syntax These are the 6 Concepts that make up 90% of your codebase: 1. Arrow Functions (=>) - Stop writing function add(a,b) The Code: const Component = () => { return
} The Why: This is the standard for modern React Components. It handles this binding automatically (so you don't have the old headache) 2. Destructuring ({ }) - Stop doing user.name and user.age The Code: const { name, age } = user; The Why: In React, you receive "Props" as an object. Destructuring lets you pull out exactly what you need immediately. It cleans up your code massively 3. Array Methods (.map & .filter) - Stop writing for loops. Seriously The Code: users.map(user => user.name} />) The Why: React is declarative. You don't tell the DOM how to change; you tell data how to transform into UI. Map converts Data → Component 4. Async / Await - Stop using .then() chains and Callbacks The Code: const data = await client.from('users').select('*') The Why: When you connect to a backend (Supabase/Firebase), you need to wait for data. Async/await makes asynchronous code look like clean, synchronous code 5. Ternary Operators (? :) - Stop writing if/else statements inside your JSX The Code: isLoggedIn ? : The Why: You can't write if statements inside React's return block. You must use ternaries for conditional rendering 6. Template Literals (`) - Stop using + to concatenate strings The Code: `bg-blue-${isActive ? '500' : '200'}` The Why: This is critical for dynamic styling in Tailwind Don't aim for "100% JavaScript coverage" Aim → "100% Proficiency in these 6 items" Once you trust that you can ignore the rest (for now), you unlock the speed to actually build what you can try out now is: >Open your console. >Write a function that fetches data from an API using async/await, destructures the result, and maps it to a console log Do that, and you are ready for the next topic if you found this helpful, a repost would mean a lot to me and let me know in the replies if you have any queries, locked in for the next topic
Ishan tweet media
English
20
21
105
6.5K