This is what happens when you hire based on framework skills. In this case, it was a combination of React and Next.js. I have received an email with the following text: "I want to rebuild the frontend of my existing website from scratch. The purpose of a complete rebuild is to eliminate UI glitches, optimize performance, improve stability and maintainability, and add full multi-language support. I don't want to change the design or backend. I want the frontend code to be clean and easy to maintain." I opened a random component and found a lot of `useState`. Unfortunately, many other components have the same issue. Here is a list of other issues: - Excessive unused code - Most of the code runs on the client side (without a real need) - No lazy-loading for components and 3rd-party scripts - Lack of Static Rendering, Incremental Static Regeneration (ISR), and Server Side Rendering (SSR) - No architectural practices, no adherence to clean code principles, no consistent code styles - No pull requests or code review processes - No strict typing The good news is, they are using ESLint and Prettier. The bad news is, they have disabled most of the rules. Oh man... If you think that it's an exception, unfortunately, no. 💡 Pro Tip: Don't hire based on a particular framework, library, tool, etc. HIre based on the core skills. If you need some help with defining such skills, my DM is always open. P.S. I guess we will skip such a project. #Nextjs #React #Dev #SaaS #Frontend
Hey folks! Thanks a lot for all your activities. I was overwhelmed with all the comments, reposts, and likes. I guess it's my turn to pay to the community) I will prepare a separate post with all my thoughts regarding the approaches and best practices. I expect to post it on the upcoming week (i.e. Mon - Wed). Stay tuned!
Hey folks! ICYMI, here comes the link https://www.linkedin.com/pulse/beyond-framework-knowledge-why-hiring-based-skills-debt-rybka--7ybqe to the article. Enjoy the reading 👋
how do we get here you may ask? Simple. The company don’t care about clean code, don’t care about best practices. Do it quick, all that matters…
this is still fine lol, not everything needs to be cleaned persay, it;s still usable and yet better almost all variables are in use so state will be handled righteously, riding in some fomo dev guide trail is just argh
React is a library. Next.js is a meta framework built on that library. Calling this “hiring based on frameworks” misses the mark. A wall of useState is not an audit. Could be junior code, vibe code, could be rushed, could be a mismatch hire. Doesn’t prove the stack is bad. The checklist at the end with SSR, ISR, lazy loading, typing, and PR flow are not “framework vs core” issues. They are developer fundamentals and team process. The real takeaway isn’t “don’t hire based on frameworks.” It’s “don’t hire the wrong dev.”
Fake
but this has nothing to do with the person being a "framework hire", the person is just not very good - these two things are not mutually exclusive. tho an LLM might see it that way which explains this soulless ai slop of a post.
I can see more states than 🇺🇸
Burn it before it lays eggs.
Built $500K+ SaaS & E-Commerce Solutions. 5★ Clients' Feedback
2moOK, I see that this post is buzzing. Let’s make a deal: 200 likes and 10 reposts, and I will share my thoughts on approaches and best practices. P.S. It will save you 6+ hours of googling and ChatGPT prompting.