JavaScript developers 👀 What will be the output? var obj = { name: "Guest", welcomeFn: function () { return "Hello " + this.name; } }; var obj2 = { welcomeFn: obj.welcomeFn, name: "User" }; console.log(obj2.welcomeFn()); Looks simple… but many get it wrong 👀 Drop your answer 👇 Explanation coming soon #JavaScript #FrontendDeveloper #InterviewPrep #ReactJS
JavaScript Object Prototypes and Function Binding
More Relevant Posts
-
🚨 𝟗𝟓% 𝐨𝐟 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫𝐬 𝐆𝐞𝐭 𝐓𝐡𝐢𝐬 𝐖𝐫𝐨𝐧𝐠 𝐢𝐧 𝐉𝐚𝐯𝐚𝐒𝐜𝐫𝐢𝐩𝐭! Let me ask you something 👇 What does "function.length" actually return in JavaScript? Most developers think it counts the arguments passed ❌ But that’s not the full truth. 👉 It only counts the number of parameters defined 👉 And it completely ignores parameters after default values This small concept can easily become an interview trap if you're not clear about it. I’ve explained it with a simple example in this short video 👇 🎥 Watch here: https://lnkd.in/gtqaybpf If you're serious about improving your JavaScript fundamentals, start focusing on these small but powerful concepts. 💡 Because strong basics = strong developer. Comment “YES” if you already knew this, or "NEW" if you learned something today 👇 #javascript #webdevelopment #coding #frontend #nodejs #learnjavascript #programming #developers #softwaredeveloper #tech
JavaScript function.length 🤯 95% Developers Get This Wrong! #javascript
https://www.youtube.com/
To view or add a comment, sign in
-
JavaScript Interview Question Q: What are the limitations of JavaScript? As frontend developers, we use JavaScript daily—but it’s important to understand its limitations too 👇 Single-threaded nature Dynamic typing Security concerns Floating-point precision issues Browser inconsistencies No true multithreading 💡 Takeaway: JavaScript is powerful, but knowing its limitations helps you write better and more reliable code. What other limitations would you add? #javascript #typescript #React #NextJS #FrontendDevelopment
To view or add a comment, sign in
-
One mistake I made as a React developer 🚫 I used too many states unnecessarily. 👉 Solution: Use a single state object when possible Cleaner code = fewer bugs #reactjs #javascript #codingtips
To view or add a comment, sign in
-
🚀 **JavaScript Interview Question** What will be the output of this code? ```js const obj = { a: { b: 0 } }; const v1 = obj?.a?.b || 42; const v2 = obj?.a?.b ?? 42; console.log(v1, v2); ``` 🤔 **Think before you scroll...** --- #JavaScript #Frontend #WebDevelopment #CodingInterview #ReactJS
To view or add a comment, sign in
-
most React developers don't know why their promises break silently. they wrap everything in .catch() and wonder why errors still slip through. the problem: - .catch() only catches errors up to that point - errors after the chain slip through unhandled - processData() throws but catch doesn't see it the fix : check response status: and one rule: proper error boundaries. check status. validate data. catch at the end. #reactjs #typescript #webdevelopment #buildinpublic #javascript
To view or add a comment, sign in
-
-
Next to PHP/Laravel exceptions, Flare tracks JavaScript errors too. 💪 Super handy for letting AI fix frontend errors (JS/Vue/React) using the Flare CLI/skill.
To view or add a comment, sign in
-
-
Beginner React Developer vs Improving Developer Beginner: • Copies code • Uses useEffect everywhere • Writes big components Improving: • Understands logic • Keeps code simple • Breaks components Difference? Understanding > copying #ReactJS #FrontendDeveloper #WebDevelopment #JavaScript #LearningInPublic
To view or add a comment, sign in
-
I once fixed a performance issue… Didn’t change logic. Didn’t add caching. Just replaced a loop with Promise.all() Speed went 📈 Sometimes the problem isn’t scale… it’s how you write async code. #SoftwareEngineering #NodeJS #JavaScript #Performance #DevTips
To view or add a comment, sign in
-
-
most React developers re-render their entire component when only one value changed. split your state by what changes together. fields that update independently should live independently. the rule: if two pieces of state never update at the same time they shouldn't share an object. one small decision at the start of a component. massive performance difference at scale. #reactjs #typescript #webdevelopment #buildinpublic #javascript
To view or add a comment, sign in
-
-
React Query changed how I think about state — and I have not used Redux since The server state vs client state distinction that React Query makes explicit replaced my need for Redux entirely. Here is the mental model shift. Full breakdown (7 min read) → https://lnkd.in/gcUhHrV2 #ReactJS #Frontend #JavaScript #TypeScript #WebDev #UIEngineering
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development