Andre Gonzales

3 New CSS Features You’ll Love, Keeping up with modern CSS? These three updates simplify how we write responsive and dynamic styles. Let’s break them down: 1️⃣ Simpler Media Queries Forget the clunky min-width and max-width syntax. You can now write it like math (which, for a dumb brain like me, is a blessing): @media (width >= 600px) { } @media (400px <= width <= 800px) { } Way more readable. No more second-guessing where the brackets go. 2️⃣ Nesting Comes to CSS You can now nest pseudo-classes inside selectors — no preprocessor needed: button { color: black; : hover { color: white; } } Cleaner, shorter, and finally native! 3️⃣ Smarter Dark Mode Use color-scheme + light-dark() to adapt themes without extra media queries: : root { color-scheme: light dark; } Modern CSS is becoming more readable and powerful. Update your habits and write cleaner code! 💡 #Mernstackdeveloper #Reactjs #Nextjs #Angularjs #WebDevelopment #FrontendDevelopment #Frontend #WebDesign #CSS #ModernCSS #Programming #Coding #ResponsiveDesign #Tech #SoftwareDevelopment #Developers #UIUX #LearnToCode

2,562

73 Comments

Why the hell are you applying for coding jobs if you can't actually code? We interviewed 10 "coders" last week for a couple of entry level roles we had. SEVEN couldn't explain a single line of their own code submitted as part of the initial assignment. They just copied, pasted, and prayed. My CTO didn't mince words: "We know the f*cking AI is good. The interview was to find out how good YOU are." Let's be brutally honest: relying entirely on vibe coding is like claiming to be a photographer because you can apply Instagram filters You might create something that works momentarily, but you're screwed when reality hits. Don't get me wrong – I'm not against using these tools strategically. I just built a complex pricing calculator in ONE DAY that our team couldn't get around to doing for a year! The harsh truth? Tools amplify capability – they don't replace it. If you have zero fundamental knowledge, your "skills" are an illusion. If you're applying for a coding position: - Know the basics of the language YOU picked - Understand how your code actually works - Be able to debug and modify when things go wrong If you panic at runtime errors, go vibe for the competition. Otherwise, what exactly are we paying you for? roleplay a coder?

581

191 Comments

TypeScript overkill? The bug that changed my mind I used to think TypeScript was just… noise. Extra syntax, more setup, and not worth the hassle for “small” projects. Until one bug slipped through to production. Just one. A simple typo in a prop name, missed in review, missed in testing. And it broke a core flow in production. The kicker? TypeScript would have caught it in seconds. That moment changed my mindset. I stopped seeing TypeScript as “extra work” and started seeing it as future-proofing. Here’s what I’ve noticed since going all in: • I catch 80% of bugs before I ever run the app • Refactors are faster and safer • Collaborating with teams became 10X smoother Now, whether I’m building for web (React, Next.js) or mobile (React Native), TS is non-negotiable.

2,651

154 Comments

Stop hiring "junior devs" for NPR 15,000/month Expecting them to build production-grade apps. If you want a beginner, mentor them. If you want results, pay for experience. It’s not about skill, it’s about respect.

1,499

36 Comments

The reality of today's job market, especially technology is that it is not easy to get in. I would advise you not to sit on the sideline waiting for that perfect tech job to land in your lap. You will either have to network like a madman and work on a lot of projects and grind leetcode or you could try other options such as starting a freelancing business doing automation and websites for local businesses. Another option is entering in through the sidedoor at a desirable company doing something that may not be exactly what you want to do and transitioning into your desired role it becomes available. The last thing you want to do is get down on yourself and sit around being depressed. With faith and effort, you can eventually get into a great role!

45

10 Comments

Building Accessible React Components Isn’t Optional Here’s What I Include By Default Early in my career, accessibility felt like a “nice-to-have.” Something we’d circle back to. Something to "fix later.” ✨ But then I watched: 🔸A blind user navigate the web with a screen reader 🔸A developer share their color blindness struggles 🔸A user fail to submit a form, just because of poor keyboard support That changed how I build components. > Accessibility isn't just about checklists. It’s about building interfaces everyone can use, without barriers. Here’s what I now include by default in every React component I design 👇 ✅ 1. I Always Use Semantic HTML (Not Just Divs) ✨ Instead of: <div onClick​={handleClick}>Click me</div> ✨ I write: <button onClick​={handleClick}>Click me</button> ✅ Built-in keyboard support ✅ Works with screen readers ✅ No need for extra ARIA > HTML is already accessible, use it right. 🏷️ 2. I Connect Labels to Inputs, The Right Way <label htmlFor="email">Email</label> <input id="email" /> Or better, use useId() in React 18+: const id = useId(); <label htmlFor={id}>Email</label> <input id={id} /> ✅ This ensures screen readers announce the label ✅ Especially useful for custom form fields ⌨️ 3. I Support Full Keyboard Navigation ✨ Any interactive component I build (modals, dropdowns, tabs): ⬆️ Supports arrow keys ⏎ Enter selects ⎋ Escape closes 🔄 Tab traps focus when needed I use utilities like focus-trap, roving tabindex, and key handlers. > If it works with a mouse but not a keyboard, it’s not complete. 🔍 4. I Add the Right ARIA Roles, Only When Needed ARIA is powerful, but easy to misuse. ✨ I use it when: 🔸Recreating custom UI patterns 🔸Adding hidden labels 🔸Providing roles like role="alert" or aria-expanded ❌ I don’t use ARIA to fix broken HTML structure. 🌈 5. I Check Color Contrast & Focus States Minimum 4.5:1 contrast for text Strong visible focus indicators (not just a thin outline) Avoid “grey on grey” for disabled elements ✨Use tools like: 🔸 Chrome DevTools → Accessibility tab 🔸WebAIM Contrast Checker > A design that looks great to you may be invisible to others. 🧪 6. I Write Accessibility Tests ✨ With React Testing Library: expect(getByRole('button', { name: /submit/i })).toBeInTheDocument(); Or use axe-core for automated audits. > You test logic. Why not test usability for everyone? TL;DR 🎯 Accessibility isn’t extra, it’s essential. Here’s what I now include by default: ✅ Semantic HTML ✅ Proper label associations ✅ Keyboard-first UX ✅ Thoughtful ARIA roles ✅ Contrast and focus ✅ A11y-aware tests > Your app should work for everyone. Not just for people like you. #ReactJS #Accessibility #FrontendTips #InclusiveDesign #A11Y #FrontendDevelopment #FullstackDevelopment #LinkedIn #WebDevelopment #ReactComponents #CleanCode #LearningInPublic

52

9 Comments

You’re not stuck at the Junior SWE level because of your coding skills. Or because "there's no budget for promotions.” You’re stuck because your thinking hasn’t leveled up yet. When I was a Junior Engineer at Postman, my questions looked like this: "Which API do I need to use?" "How do I implement this feature?" I was always stuck in the WHAT and HOW. I thought my job was just to write good code. But when I joined OYO as a Senior Engineer, my mindset started to shift. My questions changed: "Why are we building this widget?" "How will this feature affect the user experience?" "Will this improve conversion rates or create more confusion?" I was thinking about WHY we were doing things, not just HOW to do them. Junior Engineers ask: WHAT do I need to do? HOW do I code this? Senior Engineers ask: WHY are we building this? WHAT impact will this have on our users? Is this aligned with our business goals? Most engineers stay stuck at junior levels because: They never move beyond just writing code. They don’t focus on the bigger picture or business impact. They keep waiting for instructions instead of taking ownership. Sit in on meetings with senior engineers, product managers, or business leaders. Listen to the questions they ask and the problems they care about. This is exactly how I grew from a junior engineer at Postman to a senior engineer at OYO and eventually landed my dream job as a Senior Software Engineer at Microsoft (L63). Change your questions. Change your thinking. And watch your career grow.

247

11 Comments