Tomas Cormons

I always tell devs: if you're stuck on what to build with AI, reverse-engineer real tools. Try this: - Look at GitHub Copilot—what does it automate? - Use Grammarly—how does it rewrite? - Play with Notion AI—what prompts power it? Then, recreate a tiny version of one. That’s the best way to learn.

3

Software engineers fear the AI that will take their job while the real danger I see should be in companies and solution owners themselves. Products that you spent years and tons of dollars for buildng selling it for whatever the number of subscriptions is can now be easily cloned and it costs nothing but the Gen AI subscription and some small resources. I am really curious of how the scene will look like after maybe Q2 of 2026. The development that business owners needs to follow “not to fail in the common nokia example” is now talking days not years like all used before!! #ArtificialIntelligence #GenerativeAI #SaaS #StartupLife #ProductManagement  #SoftwareEngineering #TechTrends #DigitalTransformation  #Innovation #FutureOfWork #Entrepreneurship  

5

2 Comments

Handling 401 Errors Like a Pro in React + Redux 🔐 Security isn’t just about strong passwords — it's also about smart error handling. A 401 Unauthorized error can create confusion for users if not managed properly. Here's how to handle it the right way: ✅ Intercept 401 responses using Axios interceptors or middleware. ✅ Dispatch Redux actions to log out users or refresh tokens gracefully. ✅ Redirect to Login with context — show a message like "Your session has expired. Please log in again." ✅ Preserve state so users can pick up right where they left off after re-authentication. ✅ Track 401s to monitor suspicious activity or auth-related issues. Pro tip: A seamless 401 experience improves security and user trust. How do you handle authentication errors in your apps? #ReactJS #Redux #Authentication #WebSecurity #JavaScript #FrontendDevelopment #ReactDeveloper #CleanCode #CodingTips #WebDev #UXDesign #TokenAuth #ErrorHandling #SoftwareEngineering #DeveloperExperience

8

1 Comment

This week I shipped two micro-frontends from prototype to production as part of Upwork's platform decomposition into composable smart surfaces. The job search browser went from zero to merged with real pagination, sidebar filtering, accessible scroll-to-top, and reactive search state. The membership manager was the heavier lift: 4 parallel GraphQL queries with graceful degradation, a full API transform layer normalizing raw schema into clean store state, reworked modals, alerts, tracking, and i18n — roughly 1,750 lines across 36 files. Both run as independent SPAs injected into the platform shell, each with its own Pinia store, error boundaries, and analytics instrumentation. What I keep learning at this scale is that the hard part isn't building the feature — it's designing the boundary. Where does the microapp end and the shell begin? Which queries are critical enough to block render, and which degrade silently? How do you instrument analytics without coupling to the host? These are the decisions that determine whether a micro-frontend architecture actually scales or just moves the monolith into smaller boxes.

3

Here’s the uncomfortable truth about why junior developers can’t get hired right now. Many juniors wonder why they can’t land their first role. The reality? You’re often competing with candidates who have 10+ years of experience and advanced degrees. Employers are naturally drawn to these “safer” bets—but that doesn’t mean juniors are out of luck. Understanding this gap helps you strategize smarter, not blame yourself. My take: focus on building projects that solve problems that would mimic real problems you would likely face in the workplace. Connect with senior developers, recruiters and even directors and start a conversation. This will help you figure out what “real problems” would look like and from there you’d be able to see what projects may help you land that next role. Question: Did you have a project that helped you stand out or land a role? #softwaredevelopment #softwareengineering #jobmarket #competition #tech

9

2 Comments

The biggest fear with remote engineers? Trust. You've been burned. I get it. -A dev disappeared. -Code was a mess. -Deadlines were missed. That's not a remote problem. That’s a vetting problem. We don't just find engineers at Kovil AI. We pre-vet them. We build trust first, so you don't have to risk your roadmap on a promise. Stop hiring with hope. Start hiring with trust. #Hiring #Leadership #Startups #Technology

8